Comments on: Temptations of an Agile Project: Let’s Make the Sprint Longer http://www.adeptechllc.com/2009/12/14/temptations-of-an-agile-project-lets-make-the-sprint-longer/ Software, Agile Process and Security Wed, 07 Jul 2010 21:25:24 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Santhosh Sreedharan http://www.adeptechllc.com/2009/12/14/temptations-of-an-agile-project-lets-make-the-sprint-longer/comment-page-1/#comment-4625 Santhosh Sreedharan Thu, 24 Dec 2009 16:16:00 +0000 http://www.adeptechllc.com/?p=262#comment-4625 <blockquote cite="making the sprint longer is such a temptation "> Been there, tried that. I think this temptation is more from trying to comeup with a working app or prototype for the product owner, within the crunched timeline. More or less inexperience in Agile stems this temptation. Incorrectly breaking down a story adds on to this. As a caution, this temptation can be avoided even by development teams if "DONE" is clearly defined and understood by teams and accepted by the product owner. My two cents.

Been there, tried that. I think this temptation is more from trying to comeup with a working app or prototype for the product owner, within the crunched timeline. More or less inexperience in Agile stems this temptation. Incorrectly breaking down a story adds on to this. As a caution, this temptation can be avoided even by development teams if “DONE” is clearly defined and understood by teams and accepted by the product owner. My two cents.

]]> By: Manoj Vadakkan http://www.adeptechllc.com/2009/12/14/temptations-of-an-agile-project-lets-make-the-sprint-longer/comment-page-1/#comment-4624 Manoj Vadakkan Thu, 17 Dec 2009 21:57:04 +0000 http://www.adeptechllc.com/?p=262#comment-4624 Keith, Great piece of advice and nicely put “I encourage teams to put as many people as make sense on the same story, and only when we’re getting in each others way start working on other stories. I tell them it’s better to have one story completely done than two mostly done.” Thank you! Other way around, when team members start working on independent stories the amount of collaboration goes down and eventually start looking like a mini waterfall. Think about the testing person in the team; tester will end up real busy at the end of the sprint and most of the time we will run out of time in the sprint before completing many of the stories. Manoj Keith,
Great piece of advice and nicely put “I encourage teams to put as many people as make sense on the same story, and only when we’re getting in each others way start working on other stories. I tell them it’s better to have one story completely done than two mostly done.” Thank you!

Other way around, when team members start working on independent stories the amount of collaboration goes down and eventually start looking like a mini waterfall. Think about the testing person in the team; tester will end up real busy at the end of the sprint and most of the time we will run out of time in the sprint before completing many of the stories.

Manoj

]]>