Sprint planning and story work breakdown
I've done quite a bit of homework on this, but am still confused and would really like advisement.
We have a bunch of user stories sitting in our release backlog. During a sprint planning session, we move select user stories from the release backlog into a sprint backlog (using the Iterations view of our Release Backlog plan).
At that point, we create a bunch of child tasks for accomplishing the user story, those tasks are then assigned to individuals and we get a feel for the load across the team.
Does this sound like intended workflow so far?
During daily scrums, we rely on the taskboard view and update progress on various tasks. The problem is, the subtasks for the user stories appear on the board twice. They appear in the section of the board that groups all of the tasks assigned to an individual (which makes sense), but they also appear (grayed out) next to the user story.
This seems awkward. What happens is we have a scrumboard that is much larger than necessary. I don't see why the child tasks are reiterated. I understand why the story would appear in the far left column (so that tasks are grouped in horizontal swimlanes), but I don't understand why the sub-tasks are reiterated.
Is there a setting I can alter? If needed, I can annotate a picture and post.
We have a bunch of user stories sitting in our release backlog. During a sprint planning session, we move select user stories from the release backlog into a sprint backlog (using the Iterations view of our Release Backlog plan).
At that point, we create a bunch of child tasks for accomplishing the user story, those tasks are then assigned to individuals and we get a feel for the load across the team.
Does this sound like intended workflow so far?
During daily scrums, we rely on the taskboard view and update progress on various tasks. The problem is, the subtasks for the user stories appear on the board twice. They appear in the section of the board that groups all of the tasks assigned to an individual (which makes sense), but they also appear (grayed out) next to the user story.
This seems awkward. What happens is we have a scrumboard that is much larger than necessary. I don't see why the child tasks are reiterated. I understand why the story would appear in the far left column (so that tasks are grouped in horizontal swimlanes), but I don't understand why the sub-tasks are reiterated.
Is there a setting I can alter? If needed, I can annotate a picture and post.
One answer
I agree that this shouldn't happen.
I've submitted work item 124871, and added you as a subscriber.
Cheers,
Geoff
On 8/7/2010 12:38 PM, jleone wrote:
I've submitted work item 124871, and added you as a subscriber.
Cheers,
Geoff
On 8/7/2010 12:38 PM, jleone wrote:
I've done quite a bit of homework on this, but am still confused and
would really like advisement.
We have a bunch of user stories sitting in our release backlog.
During a sprint planning session, we move select user stories from
the release backlog into a sprint backlog (using the Iterations view
of our Release Backlog plan).
At that point, we create a bunch of child tasks for accomplishing the
user story, those tasks are then assigned to individuals and we get a
feel for the load across the team.
Does this sound like intended workflow so far?
During daily scrums, we rely on the taskboard view and update progress
on various tasks. The problem is, the subtasks for the user stories
appear on the board twice. They appear in the section of the board
that groups all of the tasks assigned to an individual (which makes
sense), but they also appear (grayed out) next to the user story.
This seems awkward. What happens is we have a scrumboard that is much
larger than necessary. I don't see why the child tasks are
reiterated. I understand why the story would appear in the far left
column (so that tasks are grouped in horizontal swimlanes), but I
don't understand why the sub-tasks are reiterated.
Is there a setting I can alter? If needed, I can annotate a picture
and post.