Pages

Sunday, March 11, 2007

Task creation for fulfilling user requrirements

At the end of the requirement workshop, first thing the Scrum team would be looking forward to is to create the tasks for the features. For the rest of the iteration, only thing they are worried is how many tasks they have been able to complete. In this process, they forget that they have to deliver the Running Testing Features(popularly known as RTF) to the customer.

One way to avoid this task creation madness could be to divide the features into smaller feature chunks that can be handled like a task. (Right now the discussion is going about this in scrumdevelopment forums)

For Ex: instead of writing a task like "Database creation", if we can rewrite it as "Database creation to fulfill the storyX" Or rewriting it as "Handling Database related work to fulfill FeatureX" could make the team to "NOT" lose their focus on features/requirements.

2 comments:

Michael said...

Excellent posting!

If you are interested in learning more about tasking -- and Scrum in general -- check out www.implementingscrum.com where I post regular cartoons and blogs about what I see on a daily basis when working with Scrum teams.

Please let me know your thoughts.

Thank you!

- mike vizdos
www.michaelvizdos.com
www.implementingscrum.com

Anonymous said...

I found this site using [url=http://google.com]google.com[/url] And i want to thank you for your work. You have done really very good site. Great work, great site! Thank you!

Sorry for offtopic