Wednesday, January 30, 2013

Scrum tales - Part 13 - Remaining work estimate

Sprints and Tasks are ownership of Scrum team members and as such you are directly responsible for maintaining their integrity. Product Owner is only concerned with specific Product Backlog Items (goals), to get final deliverables as expected, and won't interfere with the Sprint Tasks

As each Task is owned by a single Scrum team member, if the task is not done at the end of the day, that team member must update the estimate in hours on how much work remains. The estimate should be as real as possible and should answer a simple question "How many more hours do I need in order to complete this task?"

Q: Can the work hours estimate be unchanged or even go up after working on a task?
A: Yes, but in such cases if your daily burndown Actual line also goes up you need to provide an explanation

Q: Where do I track how many hours I spent on a specific Task?
A: You don't. We only need to know how much work remains and to have as objective estimate as possible

Q: What if my Task takes several days to complete?
A: Refactor the Task to create several smaller ones so you can complete at least one Task each day; don't end a workday without finishing at least one Task

Q: What if our Tasks are too complex and cannot be split into smaller Tasks?
A: Unless your Task is an elementary particle, it can be split

A good sprint is a sprint that has concise Tasks so that each Scrum team member can complete at least one Task each day and provide a Daily deliverable

No comments:

Post a Comment