We have the burdown chart to measure the features delivered in a Agile project (in complexity). But I have never seen such a chart displaying the actual business value delivered.
Patrice BlanchardExpert in transferring his expertise| Museum Box srlBraine L'Alleud, Brabant Wallon, Belgium
Burndown chart is the project point of view.What about the customer point of view? Have you ever seen such a chart dispoaying the reals Business Value delivered and focusing on the business instead of focusing on the project team delivery? Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Patrice
Those charts are to display progress through releases. During each release or sprint, there is a sprint review in which the client review what is being delivered and together with the team confirms it adds value or make adjustments to the backlog.
You can always do a roadmap for what is being delivered each release along with the value it adds.
RK
...
1 reply by Patrice Blanchard
May 31, 2023 7:43 AM
Patrice Blanchard
...
Thanks for your answer Rami,
Ths issue I see with review at the end of the sprint is that it is a lag information. I mean the team is receiving infomation AFTER the job has been done. It is too late for backlog refinement and adjusting it.
This goes agains the agile practices trying to get early feedback and information shared to the eam as soon as possible.
At least it is a good start.
I'd suspect a burnup chart would be more useful for such a use case. The target threshold would be the expected benefits and the team could track how much value had been delivered over time.
Such a tool would also help a customer decide if they had received "sufficient" business value such that further project work was not required.
Kiron
...
1 reply by Patrice Blanchard
May 31, 2023 7:44 AM
Patrice Blanchard
...
This sounds like a very good solution. I am just surprised I never saw such a burnup chart in agile practices.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
In my personal experience, in the y axis, you can show what you like. For example, value. But visualization could be better with burn up chart, because if you show a line with up to bottom direction to show value achievement it could be misunderstand.
...
2 replies by Keith Novak and Patrice Blanchard
May 31, 2023 7:49 AM
Patrice Blanchard
...
How come this kind of chart is not discussed / presented in agile documentation. I mean this makes sense and is directly bringing value to the team and the business.
There is no question whether it is feasible. Let's just start using it.
The only issue I see it the optimal measure of business value. For complexity we have planning poker but nothing similar for business value. It is even rarely presented and discussed in the CARD for the user story.
May 31, 2023 9:41 PM
Keith Novak
...
I really like that elegantly simple explanation: in the y axis, you can show what you like.
It is a lot easier to explain the reason for that chart format than math terms. It also goes together well with how we often think "up" on a chart is good (unless you're talking about quality control).
Saving Changes...
Iain FraserAuthor, Speaker, Independent Director| Jacobite ConsultingWellington, New Zealand
Irrespective of what format you use to communicate progress, the key is making sure that 'value' is well defined and understood within your organisation. You could take a singular view eg finance or a more balanced perspective across 4 themes. These themes can then be the basis of a balanced scorecard type of communication that shows value captured against one or more of the themes. Great at the organizational level and useful at a project level. More from 'The Business of Portfolio Management - Boosting Organizational Value' book from PMI.
...
1 reply by Patrice Blanchard
May 31, 2023 7:45 AM
Patrice Blanchard
...
Humm this sounds like a very interesting reading to go through. Thanks a lot for the info Iain.
I have never implemented a BD chart to measure business value. However, every time I notice a slowdown in team velocity or insufficient progress, it triggers our team to undertake an analytical effort to determine why is this situation happening and what is its impact on value delivery/project realization. One thing takes us to the other. Our analysis effort always include previously established KPIs and other metrics that help us assess the circumstances. Thank you everyone for sharing your ideas and knowledge on this topic. It is great to learn new things every time I visit this w page. Saving Changes...
Patrice BlanchardExpert in transferring his expertise| Museum Box srlBraine L'Alleud, Brabant Wallon, Belgium
May 27, 2023 12:47 PM
Replying to Rami Kaibni
...
Patrice
Those charts are to display progress through releases. During each release or sprint, there is a sprint review in which the client review what is being delivered and together with the team confirms it adds value or make adjustments to the backlog.
You can always do a roadmap for what is being delivered each release along with the value it adds.
RK
Thanks for your answer Rami,
Ths issue I see with review at the end of the sprint is that it is a lag information. I mean the team is receiving infomation AFTER the job has been done. It is too late for backlog refinement and adjusting it.
This goes agains the agile practices trying to get early feedback and information shared to the eam as soon as possible.
At least it is a good start. Saving Changes...
Patrice BlanchardExpert in transferring his expertise| Museum Box srlBraine L'Alleud, Brabant Wallon, Belgium
May 27, 2023 12:57 PM
Replying to Kiron Bondale
...
Patrice -
I'd suspect a burnup chart would be more useful for such a use case. The target threshold would be the expected benefits and the team could track how much value had been delivered over time.
Such a tool would also help a customer decide if they had received "sufficient" business value such that further project work was not required.
Kiron
This sounds like a very good solution. I am just surprised I never saw such a burnup chart in agile practices. Saving Changes...
Patrice BlanchardExpert in transferring his expertise| Museum Box srlBraine L'Alleud, Brabant Wallon, Belgium
May 28, 2023 7:04 PM
Replying to Iain Fraser
...
Irrespective of what format you use to communicate progress, the key is making sure that 'value' is well defined and understood within your organisation. You could take a singular view eg finance or a more balanced perspective across 4 themes. These themes can then be the basis of a balanced scorecard type of communication that shows value captured against one or more of the themes. Great at the organizational level and useful at a project level. More from 'The Business of Portfolio Management - Boosting Organizational Value' book from PMI.
Humm this sounds like a very interesting reading to go through. Thanks a lot for the info Iain. Saving Changes...
Patrice BlanchardExpert in transferring his expertise| Museum Box srlBraine L'Alleud, Brabant Wallon, Belgium
May 28, 2023 8:49 AM
Replying to Sergio Luis Conte
...
In my personal experience, in the y axis, you can show what you like. For example, value. But visualization could be better with burn up chart, because if you show a line with up to bottom direction to show value achievement it could be misunderstand.
How come this kind of chart is not discussed / presented in agile documentation. I mean this makes sense and is directly bringing value to the team and the business.
There is no question whether it is feasible. Let's just start using it.
The only issue I see it the optimal measure of business value. For complexity we have planning poker but nothing similar for business value. It is even rarely presented and discussed in the CARD for the user story.
...
1 reply by Sergio Luis Conte
Jun 01, 2023 6:31 AM
Sergio Luis Conte
...
The point is: this chart is not related to agile. Is an "ancient" chart that becomes from long time ago. But, like other things, it could be consider a new "buzzword". As you know, the point is to understand the meaning. Then, you can plot what you like into it. About the meassure of business value it is a matter of other discipline (to pint this in the context of PMI and others) which is business analysis. And it is a lot to write about. You can see other methods/approaches like MoV, ValueIT, etc. In the past I worked a lot as volunteer with the PMI with this type of topics mainly in the framework of benefits realization.
Community Champion
