“How much is this going to cost?” - “As much as you're willing to spend.”
“How long is this going to take?” - “As long as it necessary.”
“What am I going to get?” - “Whatever you tell us you want.”
These are the common questions that get asked at the beginning of any project. “Pure” agile has minimal constraints beyond the customers imagination. The high-level scope that is defined at the beginning of a project can be changed out of all recognition as the customer evolves the product backlog between iterations.
A burndown chart is an excellent mechanism to visualise the progress of a project, and can provide early feedback on the progress of a project or sprint. Below are 6 potential issues, and how to identify them using burndown charts.
Evan Leybourn is a leader, coach and (soon to be published) author in the developing fields of Agile Corporate Governance and Lean Business Management; applying the successful concepts and practices from the Lean and Agile movements to corporate management. Evan has a passion for building effective and productive organisations filled with actively engaged and committed staff while ensuring high-levels of customer satisfaction. He has held executive, board and advisory positions in private industry and government
Evan currently calls Melbourne, Australia, home, but works with clients across Australia, South East Asia and America to develop institutional capability and is a regular speaker at a variety of international conferences.