Comments on: When Agile Goes Wrong http://www.onesandthrees.com/2008/08/when-agile-goes-wrong/ ... blogging about coding, music and who knows what else ... Mon, 18 May 2026 09:55:52 +0000 http://wordpress.org/?v=2.6 By: Tim http://www.onesandthrees.com/2008/08/when-agile-goes-wrong/#comment-732 Tim Tue, 13 Apr 2010 09:56:32 +0000 http://onesandthrees.com/blog/?p=16#comment-732 I'd make a couple of comments. The fact that you needed to do load testing, should have come out of the acceptance criteria for your stories e.g "the system needs to support x users doing y at the same time" - if this isn't a requirment it doesn't need doing, if it is a requirement it needs to be stated. If you're fixing resource, time and features - its bound to fail. Whatever methodology. Scrum fixes resource and time, meaining that features are flexible - thats why they need prioritising - they aren't all going to get done. I’d make a couple of comments.

The fact that you needed to do load testing, should have come out of the acceptance criteria for your stories e.g “the system needs to support x users doing y at the same time” - if this isn’t a requirment it doesn’t need doing, if it is a requirement it needs to be stated.

If you’re fixing resource, time and features - its bound to fail. Whatever methodology. Scrum fixes resource and time, meaining that features are flexible - thats why they need prioritising - they aren’t all going to get done.

]]>