Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Hi,
I am looking for tools or recommendations to manage properly the risks on Agile projects, all your lessons learned I'll appreciate them. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jesus - On agile projects, you manage risk as you go by creating a Risk Adjusted Product Backlog, Risk Register and monitoring the same using a Risk Burndown Graph. Refer to Mike Griffith’s book, it is very well explained there with detailed example.
...
1 reply by Jesus Martheyn
Aug 19, 2018 6:04 PM
Jesus Martheyn
...
Thanks Rami, I'm going to research about it.
Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Prioritize them, same as in waterfall, but the application is a little different. Agile uses product backlogs to manage and prioritize features/stories and adjusts them to reflect not only value, but risk. That's why it's called a risk-adjusted backlog when that occurs. We do the highest value, highest risk items first wherever possible.
...
1 reply by Jesus Martheyn
Aug 19, 2018 6:03 PM
Jesus Martheyn
...
Hi Sante, I got it. Thanks for your answer.
Saving Changes...
Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Aug 19, 2018 5:56 PM
Replying to Sante Delle-Vergini, PhD
...
Prioritize them, same as in waterfall, but the application is a little different. Agile uses product backlogs to manage and prioritize features/stories and adjusts them to reflect not only value, but risk. That's why it's called a risk-adjusted backlog when that occurs. We do the highest value, highest risk items first wherever possible.
Hi Sante, I got it. Thanks for your answer. Saving Changes...
Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Aug 19, 2018 4:54 PM
Replying to Rami Kaibni
...
Jesus - On agile projects, you manage risk as you go by creating a Risk Adjusted Product Backlog, Risk Register and monitoring the same using a Risk Burndown Graph. Refer to Mike Griffith’s book, it is very well explained there with detailed example.
Thanks Rami, I'm going to research about it. Saving Changes...
Anita DhirPresident/CEO| Medhira EnterprisesLong Island City, Ny, United States
Jesus: Prior to the adoption of tools, choosing the appropriate agile method is far more important. For example, if the initial risk analysis shows that the requirements are not fully understood then, scrum would work. However, if the approach is clear and the team has worked together on a similar project successfully before then, CAS would a better approach/method to use. Many tools are common among different agile methods while there are few that help implement a specific agile method.
...
1 reply by Jesus Martheyn
Aug 19, 2018 7:13 PM
Jesus Martheyn
...
I agree with you. If on traditional Project Management the risks track was dynamic, now on agile approach is even more dynamic and a little bit hard to follow up the risks that has been identified and some others on the road.
Saving Changes...
Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Aug 19, 2018 6:10 PM
Replying to Anita Dhir
...
Jesus: Prior to the adoption of tools, choosing the appropriate agile method is far more important. For example, if the initial risk analysis shows that the requirements are not fully understood then, scrum would work. However, if the approach is clear and the team has worked together on a similar project successfully before then, CAS would a better approach/method to use. Many tools are common among different agile methods while there are few that help implement a specific agile method.
I agree with you. If on traditional Project Management the risks track was dynamic, now on agile approach is even more dynamic and a little bit hard to follow up the risks that has been identified and some others on the road. Saving Changes...
the only thing I'd add is that agile delivery encourages early exploration of key areas of uncertainty - on technology projects, that would be through development & testing, not just a paper exercise. That is in support of the "fail fast, fail cheap" principle...
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First of all, Agile projects that not exists. What exists are project managed into Agile environments. What does mean? It does mean that you can use an Agile based method or you can use Agile based techniques like iterative-incremental life cycles. Second, Agile based envionments are created to deal with risk. The reason to "invent" Agile based methods was due to deal with risk. Few people know that all Agile based method are baed on Barry Bohem´s Spiral Life Cycle. Search about this life cycle into the internet and you will understand in a simple way how Agile based methods are based on risk management. Thrid, how to manage risk? In the same way you manage risk into any other type of environments. What could defer is the tool and techniques depending on you use an Agile based method (DSDM for example) or you use your own Agile based approach (in this case you can follow tools and techniques you can find into PMBOK. I do that in my actual work place). Saving Changes...
Furthermore, could anyone advice more on the aspect of managing risk in an agile environment. I meant to say that managing risk, could it determine the following:
1. Determine the types of agile practices/framework that should be adopted/applied to a project (software development/mobile, IT)
2. Guide/provide the project team on how to select the best approach to managing a project?
If this can be explained in a pragmatic way using specific examples to enhance my understanding, that will be appreciated. Saving Changes...