2023-01-31
1370
#agile and scrum#collaboration and communication
Ian Khor
157526
Jan 31, 2023 â‹… 4 min read

What is a burndown chart?

Ian Khor Senior Product Manager @ Octopus Deploy | Ex-lawyer | Enthusiast of all things Agile, LEAN, JTBD, and RICE

Recent posts:

5 ways product managers can steward cross-pollination

Learn practical strategies PMs can use to spread ideas, improve collaboration, and shape stronger, more connected product outcomes.

Kayode Adeniyi
Sep 11, 2025 â‹… 4 min read
Steal My Startup Approved Growth Workshop Agenda

Steal my startup approved growth workshop agenda

Discover how to run a growth workshop that equips your product team to map key drivers, identify levers, and plan experiments that matter.

Kimberly Shyu
Sep 9, 2025 â‹… 6 min read
How To Consolidate Your Product Management Tools

How to consolidate your product management tools

Streamline your product stack with a six step guide to tool consolidation. Cut costs, reduce silos, and boost team efficiency.

Sara Nguyen
Sep 2, 2025 â‹… 4 min read
How To Define Customer Segments That Actually Matter

How to define customer segments that actually matter

Avoid weak product-market fit and wasted resources. Learn how to narrow broad customer segments into a focused beachhead strategy.

Joel Polanco
Aug 28, 2025 â‹… 8 min read
View all posts

One Reply to "What is a burndown chart?"

  1. This is a good article on using the “burn down” chart method to track progress on projects large enough to use them.

    And this approach, along with sprints, works well in many mass manufacturing scenarios.

    Speaking from decades of experience both managing software projects and being a hands-on developer/team lead/architect, this is a problematic way to manage software projects.

    Software engineering is quite different than manufacturing, though there are some useful commonalities.

    Manufacturing is creating N quantity of a single item, assembling it in a deterministic process of known parts and known, repeated, labor processes. There is little that is not predictable. Those who assemble the items are not engineers, but technicians.

    Software engineering is creating a number of different items, much of which comes from creating new components or altering existing components. This is nondeterministic, requires creativity, and (most importantly to this article’s context) the time to complete any part of the process is too dependent on a number of variables, as to be predictable.

    Software development is best managed by tracking the major milestones (NO SPRINTS), and team leads that know if their team members are being productive or not. Coders are typically not considered creative or professional, but developers, engineers, and architects in software are professionals who are both scientists and artists.

    Many software shops have learned that the principles echoed in the “Agile Manifesto” are useful in software engineering, and work when applied to the unique characteristics of each software shop. But many have learned the hard way that using the various “agile methodologies”, especially when managed by non-engineer project managers, are costly, lead to low quality (at best) and failed projects (at worst).

    I believe what is presented in this article has some useful principles that, when applied properly, will benefit a software project. Those useful principles do not differ much from how successful software projects were managed before the “agile methodologies” entered the software business, pouring molasses in the gears of success.

Leave a Reply