O'Reilly logo
  • Giovanni Asproni thinks this is interesting:

In Scrum, burndown charts are considered a critical and daily part of the process where engineers provide up-front task estimates and then give daily updates to those estimates throughout each four-week sprint. The primary value of the burndown chart is to predict when all the work will be completed. It is a way to show “work remaining versus time” and “are we on track.” Although they probably work great for some businesses, we found two problems with burndown charts for us. First, the time spent doing daily updates to each task estimate was time that could have been spent accomplishing more tasks instead of estimating what was remaining. Second, by its very nature, the goal of the burndown chart is to get to z...


Cover of A Practical Approach to Large-Scale Agile Development: How HP Transformed LaserJet FutureSmart Firmware


They created a 'de facto' custom methodology, by choosing which practices to implement, some of them on a per-team basis.