Skip to main content

burndown chart

Last post 08:44 pm July 5, 2020 by Thomas Owens
3 replies
11:54 am July 4, 2020

Hello Every one

I'm a junior scrum master of a young team, we are on the 12th day of our 2-week sprint and the burndown chart is a straight line with steps!

could you please guide me on how this chart can be moderated?

team members estimate and add new tasks continuously.



Thanks


02:49 pm July 5, 2020

could you please guide me on how this chart can be moderated?

Before you go ahead and do that, consider how that action might affect transparency. Also, who should be responsible for updating it?

team members estimate and add new tasks continuously.

This shouldn't be a problem as long as the Sprint Goal is not endangered and they are able to build a Done Increment. However, if they don't complete this additional work, then it might have an impact on how the burn-down might appear. Out of curiosity, why are they adding new work continuously? Are they actually intending to complete it and make it part of the Increment for that Sprint?


02:54 pm July 5, 2020

Can the team explain the burndown, and correlate it to things that have happened? If so, how are they using that information during the Sprint?


08:44 pm July 5, 2020

A few questions to consider:

  • Can the team explain the flat portions, where no work is being burned down?
  • Why is the team estimating at the task level instead of at the Product Backlog Item level?
  • Is the team discovering new work that was not considered during refinement and estimation of the Product Backlog Items?
  • Is sufficient planning, including decomposition of Product Backlog Items into more granular units of work, being done as part of Sprint Planning?
  • Is the team likely to meet their Sprint Goal?

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.