Comments on: Tips for Tasking Stories during Iteration Planning http://www.agilecoach.ca/2009/10/30/tips-for-tasking-stories-during-iteration-planning/ Changing the World, One Person at a Time Sun, 05 Feb 2012 20:37:49 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Robert Dempsey http://www.agilecoach.ca/2009/10/30/tips-for-tasking-stories-during-iteration-planning/comment-page-1/#comment-27 Robert Dempsey Tue, 03 Nov 2009 01:30:17 +0000 http://www.agilecoach.ca/?p=83#comment-27 Right on, thanks Jason. Right on, thanks Jason.

]]> By: Jason http://www.agilecoach.ca/2009/10/30/tips-for-tasking-stories-during-iteration-planning/comment-page-1/#comment-26 Jason Tue, 03 Nov 2009 00:38:09 +0000 http://www.agilecoach.ca/?p=83#comment-26 Thanks for the comment Robert, in most of the situations I've seen it's more about not really knowing how to go about it. Traditional developers are so used to taking big chunks and working on them for a few days that it's difficult for them to approach work a different way. I find they each want to pick a story because they can't get their head around doing 30 minute to 4 hour tasks but the good thing is that even the most strict developers I've worked with are open to at least trying it because they do understand the benefit. As far as writing the tasks out, some teams I've worked with that use stickies rotate the task writing each iteration and when a developer takes a task he/she would enter it into our tracking system for traceability. As the scrum master for one of the teams I'm working with now, I just enter them in the iteration planning session as we're breaking the stories down which is pretty quick. Thanks for the comment Robert, in most of the situations I’ve seen it’s more about not really knowing how to go about it. Traditional developers are so used to taking big chunks and working on them for a few days that it’s difficult for them to approach work a different way. I find they each want to pick a story because they can’t get their head around doing 30 minute to 4 hour tasks but the good thing is that even the most strict developers I’ve worked with are open to at least trying it because they do understand the benefit.

As far as writing the tasks out, some teams I’ve worked with that use stickies rotate the task writing each iteration and when a developer takes a task he/she would enter it into our tracking system for traceability. As the scrum master for one of the teams I’m working with now, I just enter them in the iteration planning session as we’re breaking the stories down which is pretty quick.

]]> By: Robert Dempsey http://www.agilecoach.ca/2009/10/30/tips-for-tasking-stories-during-iteration-planning/comment-page-1/#comment-25 Robert Dempsey Mon, 02 Nov 2009 22:22:31 +0000 http://www.agilecoach.ca/?p=83#comment-25 Great post Jason. This is a great way for teams to get those tasks laid out. Do you find that teams are hesitant to go to the task level due to the added overhead of writing out all the tasks? If so, what arguments have you found to combat it? Thanks. Great post Jason. This is a great way for teams to get those tasks laid out. Do you find that teams are hesitant to go to the task level due to the added overhead of writing out all the tasks? If so, what arguments have you found to combat it? Thanks.

]]>