Sheila's Blog

The Sprint Backlog is separate to the product backlog and contains more detailed requirements that have been broken down into tasks estimated in hours.  The Sprint Backlog allows the team to see where they are and provides a focus on the work remaining.  It’s a team artifact which does not have to be shown to others.  The whole team is responsible for updating it and it is often viewed as a task board.

Tasks should ideally be 4-16 hours of work.  You want to be able to tell in daily meetings if deadlines are likely to slip.  Instead of someone saying they are 50% through a 3 day task, it’s more accurate if they can say a task is fully complete or not.  The team either signs up for tasks or assigns the tasks as a group, taking into account the task priority and the makeup of the team.

Requirement     Task   Owner   Status       Work left (hours)

R1049               T028    JM        Open          12        6          8

Each day the hours remaining is updated so everyone can see how the Sprint is progressing.  This is then used to update the Sprint burndown chart each day.

Tags:   scrumNo Comments