14
votes
Accepted
Should a burndown chart be based on stories or tasks completed?
In order to make the burndown chart useful to the Product Owner (or the customer or the user or another stakeholder), then burning down based on stories is going to be the better option. Since a story ...
- 18.8k
9
votes
Should a burndown chart be based on stories or tasks completed?
Based on previous experience with lots of different approaches, I would agree with your last paragraph - showing anything except true value delivered (tracking tasks, hours, points etc.) often leads ...
- 957
9
votes
What can the team do to prevent stories from completing until the last day of the sprint?
Do stories generally get done by the end of the sprint? If so then leave things alone. Tracking the sprint burndown always feels to me like micro-management. The team are responsible for meeting the ...
- 6,101
9
votes
Accepted
Using burndown chart to estimate the completion date of a Scrum project
Theoretically, yes, you could use a burndown chart to estimate when all of the work in the Product Backlog would be completed. However, in practice and as you are seeing, it doesn't always work out.
...
- 18.8k
7
votes
How do I create an accurate burndown chart when my backlog keeps on being updated with new items during sprints?
With more items being added/split and re-estimated with more knowledge seems like your burndown is becoming more accurate rather than not.
Issue you are facing is that it looks like it is not ...
- 209
6
votes
Should a burndown chart be based on stories or tasks completed?
The answer depends on who your audience is.
If it is for the feature crew (i.e. product owner / developers):
The main purpose of the burn down chart is to show how the team is trending towards ...
- 190
6
votes
Sprint Burndown chart and tasks estimation in time
If we were to display the chart by Remaining Story Points, it would've been a flat line until almost the end of the sprint.
This is its own problem. It sounds like you are making insufficient use of ...
- 14.8k
6
votes
Why does the burndown chart include weekends and nights?
This question is worth hitting from a few angles:
The Direct Answer
First, to your question, I've never been in a team that found value in showing days on the burndown chart they weren't working. ...
- 16.8k
5
votes
Sprint Burndown chart and tasks estimation in time
"If we were to display the chart by Remaining Story Points, it would've been a flat line until almost the end of the sprint."
Not really a problem with story points burn-down. You just have a work in ...
- 1,255
5
votes
Should a burndown chart be based on stories or tasks completed?
Why not base the burndown chart on both?
It has the benefits to show you some insights about what's happening concerning your tasks (so it clearly shows the actual effort) without putting it out of ...
- 151
5
votes
Accepted
Optimistic vs. Pessimistic Burndown Lines - just a Project smell?
They are genuinely useful, but there are a few factors that can really skew them to be wary of.
For those not familiar, when we use a burn-up chart to track work toward some scope marker, like a ...
- 16.8k
5
votes
Accepted
Burn Down Chart : What is the definition of work done in Scrum
What is the definition of work done in Scrum
Work that satisfies the Definition of Done, which is defined by the Team.
The problem with this is that work being closed on a daily basis is not shown ...
- 14.8k
5
votes
What can the team do to prevent stories from completing until the last day of the sprint?
You need to look at that is happening inside of your sprint. A few things that might provide insight include:
How quickly are items moving into your sprint?
If everything is moving into progress on ...
- 16.8k
5
votes
Using burndown chart to estimate the completion date of a Scrum project
If you already have the three points you mentioned above, you don't need a burndown chart to estimate the completion date of the project. When you divide total story points by the velocity, what you ...
- 14.5k
4
votes
Accepted
Opaque burndown charts and story validation
Honestly, I'm not sure I'm seeing the problem. The primary purpose of a Scrum burndown chart is to measure and predict velocity, is it not? In which case, while the chart might not be pretty if most ...
- 14.8k
4
votes
Sprint Burndown chart and tasks estimation in time
TL;DR
Changing your method of reporting will not actually address the underlying process issues implied by your original problem statement. Your old reporting process was actually the better one. You ...
- 49.5k
4
votes
Do we need to update time estimates when we estimate based on story points?
Do we need to update original/remaining time estimates when we estimate based on the story points?
I'd say no. Filling time information will result in people looking at different metrics. It will ...
- 140
4
votes
What can I constructively say when looking at the Sprint Burndown
TL;DR
First of all, never "walk the board" or huddle around a chart for your daily stand-up. The meeting is for dependency coordination, not reporting or trend analysis. Staring at a burn-down doesn'...
- 49.5k
4
votes
Tips for achieving ideal burn chart
The first thing to acknowledge is that the ideal line is ideal in the mathematical sense, not in the qualitative sense. In fact, if I ever saw a burndown that matched the ideal line, that would be a ...
- 16.8k
4
votes
What can the team do to prevent stories from completing until the last day of the sprint?
Seeing things like "Ready for UAT" and "UAT" in a workflow always raises a concern for me. UAT is almost always outside of the control of the development team, and often even ...
- 18.8k
3
votes
Tracking Time Remaining with GitHub (ZenHub)
TL;DR
A story point based burndown chart doesn't measure time remaining. It measures work-effort remaining, and you must use additional metrics to forecast your schedule based on current scope.
...
- 49.5k
3
votes
How to handle tasks from previous Sprint on current Sprint Burn down chart
TL:DR: Use the original estimate. It keeps your data consistent, holds the team accountable and reflects the actual nature of work in a Scrum setting.
This answer is based on making a living as a ...
- 12.4k
3
votes
Do we need to update time estimates when we estimate based on story points?
Do we need to update original/remaining time estimates when we estimate based on the story points?
In case if you don't use time estimates, why do you need to update these fields? Just don't use them....
- 5,291
3
votes
Should the ideal line in a burndown chart be changed when story scope changes during the Sprint?
The Development Team has completed all the stories that were planned for a particular Sprint.
In this case, the team usually decides to speak with the Product Owner to select other stories from the ...
- 916
3
votes
Should the ideal line in a burndown chart be changed when story scope changes during the Sprint?
Never Rebase the Starting Values of a Burn-Down Chart
Burn-down measures work remaining in the iteration. For example, if you start a Sprint containing 100 points, complete 50 points worth of work in ...
- 49.5k
3
votes
What can I constructively say when looking at the Sprint Burndown
All graphs of this type are, in my opinion, designed to assist you to plan and prioritize. These are not the kinds of activities that I think should occur during a normal daily standup; these are ...
- 8,738
3
votes
How can I measure the effective team work per iteration?
But you are measuring the effective work per sprint just fine. If the team delivers development work but not QA for a few stories, along with some analysis, but nothing else, then the effective work ...
- 1,289
3
votes
Need help for sprint planning when tasks are not done in previous sprint
There are two answers to this: the scrum answer and the deeper answer to the questions under the surface.
First, the scrum answer on carry-over work. At the end of a sprint, all items go back to the ...
- 16.8k
2
votes
What problems can be diagnosed from a Scrum Cumulative Flow Burnup?
I am wondering what patterns stand out on a Scrum cumulative flow burnup?
Too much work in progress in development,
slow testing (automate?)
a very long lead time, and
a not changing backlog, which ...
- 11.9k
2
votes
Should the ideal line in a burndown chart be changed when story scope changes during the Sprint?
I will rather use a Burn up Chart using points to Measure progress with two metrics:Work accepted and Project scope
- 21
Only top scored, non community-wiki answers of a minimum length are eligible