RE: [scrumdevelopment] Re: What constitutes a "task" in Scrum
- I've had good luck using XP's idea of "user stories" for my product backlog.
User stories offer the advantage of being written to be much more tangible
to the Product Owner. When stories are moved to the sprint backlog we create
the appropriate tasks for them.
For information on this approach see http://www.userstories.com/download.php
and look at Chapter 15, "Using Stories with Scrum."
From: danube_tech [mailto:danube_tech@...]
Sent: Monday, January 26, 2004 3:16 PM
Subject: [scrumdevelopment] Re: What constitutes a "task" in Scrum
Yes this makes a lot of sense. Section 3.5.3 of the Schwaber and
Beedle book explains this as well. Being new to Scrum, I think we are
still a little tentative and was curious how granular other people
were getting in Sprint task backlogs.
Thanks for the confirmation.
--- In firstname.lastname@example.org, "Michael D. Ivey" <mdi@i...>
> The answer is: it depends.
> For the Product Backlog, the granularity is low. Items on the
> Backlog are usually Features or Abstract Ideas, and are estimatedin #
> of days.Sprint
> For the Sprint Backlog, the granularity is higher. Items on the
> Backlog are task-level, and are usually estimated in # of hours.looks
> The second half of the Sprint planning meeting is where the team
> at the high-level items from the Product Backlog, and creates theSprint
> Backlog items based on them. So 3 or 4 Product Backlog items maybecome
> 15 - 45 Sprint Backlog items, with more cropping up as the Sprintgoes.
>To Post a message, send it to: scrumdevelopment@...
> Does that answer your question?
> Michael D. Ivey, Senior Partner | mdi@i...
> Ivey & Brown, Inc. | http://www.iveyandbrown.com
> Process and Technology Consulting | (866) 235-7764
To Unsubscribe, send a blank message to:
Yahoo! Groups Links
To visit your group on the web, go to:
To unsubscribe from this group, send an email to:
Your use of Yahoo! Groups is subject to: