Comments on: Agile Development At Full Stretch http://www.allaboutagile.com/agile-development-at-full-stretch/ Agile Development Made Easy! Sun, 19 May 2013 08:16:47 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Kelly Waters http://www.allaboutagile.com/agile-development-at-full-stretch/#comment-188 Kelly Waters Sat, 19 Jan 2008 16:51:00 +0000 http://allaboutagile.com/uncategorized/agile-development-at-full-stretch/#comment-188 Keep stretch tasks small to try to avoid this problem.

A stretch task could be to complete something that helps with the next sprint – to get a head start.

Or it could be an important research, training or documentation task.

If it’s new code, and there’s a chance it can’t be completed before the end of the current sprint, I would advise you not to include it in the build until it’s confirmed as correct, so you don’t miss your sprint goal over a stretch task.

Kelly.

]]> By: Scheevel http://www.allaboutagile.com/agile-development-at-full-stretch/#comment-187 Scheevel Fri, 18 Jan 2008 21:41:00 +0000 http://allaboutagile.com/uncategorized/agile-development-at-full-stretch/#comment-187 I’m torn, should “could-have stretch tasks” for this sprint be the “must-have” (or at least “should-have”) stories in the next sprint’s product backlog? I ask because what if the team has time to start the “stretch task” but can’t finish. (To prevent the unfinished task from being muda) the team is commited to completing carried-over unfinished “stretch tasks” first, which could interfere with priorities OR should “stretch tasks” all be tiny and available irregardless of priority?

]]>