Skip to main content

What are Best reports to show progress to upper management.?

Last post 04:43 am March 23, 2020 by Sherwin Soriano
8 replies
12:17 pm March 17, 2020

Burn down,velocity and what else ?

 


12:22 pm March 17, 2020

What kind of questions are they trying to answer? 


12:25 pm March 17, 2020

Working software is always a great measure of progress though. 


01:26 pm March 17, 2020

How does your Development Team feel about showing their burn-down and velocity to upper management, and how might this impact those metrics? 

Might they be more interested in understanding the return on investment they are getting? The product's value? Ability to innovate? Customer feedback? Quality? Lead time, from concept to cash?

Here is a better place to start: https://www.scrum.org/resources/evidence-based-management

 


01:45 pm March 17, 2020

What are Best reports to show progress to upper management.?

A list of the organizational impediments to agile practice which only they are currently in a position to resolve.


05:03 pm March 17, 2020

+1 @Ian Mitchell!!!!!

As @Tony Divel pointed out you need to know what questions they are asking in order to determine what to show. But always lean towards showing what working software increments have been delivered or are ready to be delivered to the stakeholders.  How those increments are built isn't relevant to upper management. The value is what is important.  Burn down charts of estimated work is meaningless to anyone other than the people actually doing the work. 


12:03 am March 20, 2020

If this is a non-negotiable situation where management does not care about Scrum and just wants status, I would say that tracking story points completed would be a good measure. I have seen PMOs use this data to predict how long it will take to get work done for a customer.


02:47 pm March 21, 2020

Thanks you all for your expert advise. what I learnt In a nutshell : 

1) Velocity as it will help in forecasting 

2) Any report that help them understand impediment where they can help. 

3) working software

 

 


04:43 am March 23, 2020

agree with Tony, ask them what they are trying to answer.

Some management think that when they switch to agile, outcome or output is faster but it is not. I usually here that when they are using waterfall and project is about to fail, they switch to agile. It will still fail, agile or scrum is not a magic wand.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.