I understand the RAID well, however finding there is a requirement when you run Agile Projects to have effective Risk Burndown Charts. Has anyone in the community produce these and could I please be directed/pointed to some effective examples Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Perhaps I did not understand your question but here comes my answer. First, Agile project does not exists then I understand that you are running a project using and Agile based method/frameword. I am saying that because some of the artifact you can select to create depends on the method/framework. For example, if you are using Scrum framework all the artifacts depends on you. Second, all related to risk no matter the approach you use (Lean, Agile, etc) are the same into each approach. My recommendation is taking a look to IEEE standards on risk because it will help you to use things related to risk which are totally independent of the approach, the method/framework, the process you choose. About your question take a look to Mike Cohn´s website where you can find interesting things related to it which no matter are mainly related to software works for other domains.
A risk burndown chart can be created by either showing a simple absolute number of negative risks on the Y-axis with time on the X-axis and showing reduction or increase in risks as they are closed, or more elaborately using expected monetary value to calculate the cost or time impacts of negative risks and showing reduction or increase in that aggregated cost or time.
A risk burndown chart can be created by either showing a simple absolute number of negative risks on the Y-axis with time on the X-axis and showing reduction or increase in risks as they are closed, or more elaborately using expected monetary value to calculate the cost or time impacts of negative risks and showing reduction or increase in that aggregated cost or time.
Perhaps I did not understand your question but here comes my answer. First, Agile project does not exists then I understand that you are running a project using and Agile based method/frameword. I am saying that because some of the artifact you can select to create depends on the method/framework. For example, if you are using Scrum framework all the artifacts depends on you. Second, all related to risk no matter the approach you use (Lean, Agile, etc) are the same into each approach. My recommendation is taking a look to IEEE standards on risk because it will help you to use things related to risk which are totally independent of the approach, the method/framework, the process you choose. About your question take a look to Mike Cohn´s website where you can find interesting things related to it which no matter are mainly related to software works for other domains.
Thank you Sergio. Regards Quinette Saving Changes...
I understand the concept, but where is the requirement coming from? I'm assuming it's a subset of the overall risk list, unless ALL of the risks need to be addressed. But, who is addressing them? Is it a separate backlog? I'm trying to understand the scenario where actions needed to address the risks don't become user stories that are prioritized in the product backlog and addressed during a sprint. If they're treated the same as every other story, why is a separate burndown needed? If they're not the same, who is handling them? Saving Changes...
An RBS is useful for your stakeholders to understand how effective the team has been at early de-risking of a project. Risks wouldn't normally be in a backlog or in a work burndown chart but specific active responses to them might be. The RBS would look at all key negative risks, not just those which we had actively responded to.
Kiron
...
2 replies by Aaron Porter and Daniel King
Jan 14, 2021 8:15 PM
Aaron Porter
...
Thanks. No questions about the RBS. I just haven't had a requirement to incorporate risks into other agile processes. 18 years of waterfall and hybrid approaches. The people I report on risks to don't want burn downs.
Jan 21, 2021 3:45 PM
Daniel King
...
Thanks Kiron, that's was very useful. I was looking for some inspiration on alternative ways to visualize risks for different Agile Release Trains (ARTs) that my hybrid project has dependencies on. e.g., Risk Exposure (Days) vs. iterations
Regards, Daniel
An RBS is useful for your stakeholders to understand how effective the team has been at early de-risking of a project. Risks wouldn't normally be in a backlog or in a work burndown chart but specific active responses to them might be. The RBS would look at all key negative risks, not just those which we had actively responded to.
Kiron
Thanks. No questions about the RBS. I just haven't had a requirement to incorporate risks into other agile processes. 18 years of waterfall and hybrid approaches. The people I report on risks to don't want burn downs. Saving Changes...
Daniel KingSenior Project/Solution Manager| NorlysKøbenhavn, Denmark
Jan 14, 2021 5:00 PM
Replying to Kiron Bondale
...
Aaron -
An RBS is useful for your stakeholders to understand how effective the team has been at early de-risking of a project. Risks wouldn't normally be in a backlog or in a work burndown chart but specific active responses to them might be. The RBS would look at all key negative risks, not just those which we had actively responded to.
Kiron
Thanks Kiron, that's was very useful. I was looking for some inspiration on alternative ways to visualize risks for different Agile Release Trains (ARTs) that my hybrid project has dependencies on. e.g., Risk Exposure (Days) vs. iterations
Regards, Daniel Saving Changes...
Mike GriffithsPresident| Leading AnswersCanmore, Alberta, Canada
Community Champion
