Agile Project Management: Status Reporting

A little whileAgile Project Management Status Reporting ago I wrote about agile project management and how agile project management alone is not enough.

One area agile methods don’t really address is project status reporting.

Obviously the daily stand-up (or daily scrum) is a good form of status reporting. It’s great for people with a close interest in the project who can spare the time to get to the scrum.

But it’s really no good for other stakeholders that can’t get to the scrum each day, either because they are interested in less detail, or because they have an interest in many projects and can’t be at all the scrums.

For people like this, a traditional project status report is still important. But traditional project status reports often have their problems too. In my experience, they are often too wordy, sometimes leaving you to find the essence of the report in a sea of useless information.

In my view, the answer is simple:

The burndown chart.

For a regular project status report, calculate the burndown chart using the entire product backlog for the project, not just for the current Sprint. Forecast what future Velocity you think can be achieved based on the team’s past performance. The forecast line will allow you to forecast the project’s likely end date.

The burndown chart gives a really clear indication of status. Particularly if the team is very disciplined about the definition of done. Importantly, the status is obvious at a glance. So it’s really good for stakeholders that can’t get to the scrum, providing the key information without losing the point in lots of words.

If the project is running behind, or facing key issues or risks, they obviously warrant a brief explanation too.

The other key dimension on most projects is cost. Why not create another burndown chart for the project’s costs? If the forecast line reaches zero before the planned line, you’re running over budget and (unless you finish early) you will run out of funds!


3 Responses to “Agile Project Management: Status Reporting”

  1. C Saunders says:

    Question: Why not a burnup chart?

  2. Kelly Waters says:

    Hi Chris

    XP has a burn-up chart; Scrum has a burn-down chart.

    Since the two agile methods complement each other so well, this discrepency is a little irritating :-)


  3. Red River says:

    I haven't used Agile yet, but it sound intersting. Hope that I will have a chance to try it soon.

    About project reporting, I usually write a weekly report to my upper supervisor as below (familar with PMBoK)
    - EVM spreedsheet (excel)
    (with Agile, it will be burn down chart)
    - Short Summary & Analysis:
    + Process Management: Analy EVM
    + Issue:
    + Quality Management:
    + Deployment:

    Dont need to put so many information, I only put the summary status (the fact), processd info (analysis) and my next action.
    I think the way to write report for any kind of PM methodologies are quite similar. They should follow format "Status — Analysis — Action".

    Really want to learn about Agile :)

Leave a Reply

What is 4 + 2 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”