#agile and scrum#collaboration and communication
Ian Khor
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:

Data-Driven Roadmapping- Using Analytics To Prioritize Product Features

Data-driven roadmapping: Using analytics to prioritize product features

Data-driven road mapping refers to the process of using quantitative and qualitative data to create a roadmap for a digital product.

Kayode Adeniyi
Jul 19, 2024 ⋅ 3 min read

A complete guide to sequence diagrams

A sequence diagram is composed of several key components that provide a clear and detailed view of how system elements collaborate over time.

Jean Huang
Jul 18, 2024 ⋅ 4 min read
Jieying Zheng Leader Spotlight

Leader Spotlight: Effectively prompting repeat behavior, with Jieying Zheng

Jieying Zheng, Chief Product and Technology Officer at Bellhop, talks about how she promotes repeat customer behavior in the moving industry.

Jessica Srinivas
Jul 18, 2024 ⋅ 8 min read
Boosting team productivity during growth stages

Boosting team productivity during growth stages

In this post, I share the story of a team that overcame declining productivity through effective specialization, clear missions, and gradual change.

Dr. Marina Stojanovski
Jul 17, 2024 ⋅ 5 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