DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

How does AI transform chaos engineering from an experiment into a critical capability? Learn how to effectively operationalize the chaos.

Data quality isn't just a technical issue: It impacts an organization's compliance, operational efficiency, and customer satisfaction.

Are you a front-end or full-stack developer frustrated by front-end distractions? Learn to move forward with tooling and clear boundaries.

Developer Experience: Demand to support engineering teams has risen, and there is a shift from traditional DevOps to workflow improvements.

Related

  • Scrum Smarter, Not Louder: AI Prompts Every Developer Should Steal
  • Misunderstanding Agile: Bridging The Gap With A Kaizen Mindset
  • How to Create a Custom React Component in Vaadin Flow
  • Rebalancing Agile: Bringing People Back into Focus

Trending

  • The Missing Infrastructure Layer: Why AI's Next Evolution Requires Distributed Systems Thinking
  • Defining Effective Microservice Boundaries - A Practical Approach To Avoiding The Most Common Mistakes
  • Operationalizing Data Quality in Cloud ETL Workflows: Automated Validation and Anomaly Detection
  • From Code to Customer: Building Fault-Tolerant Microservices With Observability in Mind
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. The Ideal Burndown Chart

The Ideal Burndown Chart

A breakdown of how the "Ideal Burndown" chart is not the best indicator of productivity.

By 
Reinout Korbee user avatar
Reinout Korbee
·
Jul. 18, 19 · Opinion
Likes (10)
Comment
Save
Tweet
Share
33.1K Views

Join the DZone community and get the full member experience.

Join For Free

You probably have heard of the 'ideal' Sprint burndown chart. If you search with Google, you'll find graphs like these:

Image title

The ideal line is going down in a straight line from top left to down right. This indicates a healthy project and a well-functioning Scrum team. Value is being delivered constantly in a linear fashion.

If the burndown chart is a flat line, it is plateauing. This indicates that we have too many features, or have a poor estimation. Your team is inexperienced, in desperate need of a skilled Scrum master, and requires lecturing on the proper ways of Scrum, preferably by an experienced Scrum consultant.

I disagree.

The ideal line is a fantasy. A typical Sprint contains stories of various sizes, some small, medium, and large tasks. The team will jump on the large tasks firsthand if anyone has the capacity, some of the medium tasks. The small tasks are saved for last. This will lead to the following burndown chart.

Image title

Have you ever read how dysfunctional you are as a Scrum team if you have such a burndown chart? Have you ever had it and wondered why? Have you ever wondered where the hidden problems lie? Theory dictates that you are, in fact, a dysfunctional Scrum team, even if development seems to be going fine. Well, the theory is a fantasy based on some ideological belief that value is delivered incrementally in equally sized chunks of work.

A healthy team covers the long, difficult tasks first, and then the medium-sized tasks, and finally the smaller ones. Someone may even have started working on this one critical bug first.

This explains every single drop off in the 'dysfunctional' burn down chart.

Must have, should have, could have, would have (MoSCoW) is at work here. When dealing with uncertainty, and risk, you can't have a perfect estimation, and you manage scope according to priorities. That's business as usual in DSDM and unless you're doing something that you have already done several times before, with the same team and same technology, the ideal burndown chart will not be achieved. Those projects are boring and of low added value anyway, so why even bother?

The ideal burndown chart is an indication that you're doing something of low added value.

It is not you, the theory is wrong.

Chart scrum

Opinions expressed by DZone contributors are their own.

Related

  • Scrum Smarter, Not Louder: AI Prompts Every Developer Should Steal
  • Misunderstanding Agile: Bridging The Gap With A Kaizen Mindset
  • How to Create a Custom React Component in Vaadin Flow
  • Rebalancing Agile: Bringing People Back into Focus

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • [email protected]

Let's be friends: