Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Risk Management
How do you manage risks in an agile environment?
Network:587



Some practitioners consider that agile manage risks implicitly through a variety of practices (Continuous Delivery, Automated Testing, short iterations).

Other practitioners consider necessary to manage risks explicitly using practices as Spikes, ROAM and Risk Breakdown Chart.

Your insights would be much appreciated.
Sort By:
Page: 1 2 next>
Network:504



The advantage with Agile is that since you meet your team more frequently , you are able to identify more risks and find updates to them more frequently .
Nothing stops you from following a standard risk management process

Identify the Risks
Prioritize them
Identify mitigating actions
Assign ownership
Actively manage them

Once you have setup a "Shared" risk register , (and there are very good EXCEL templates that auto calculate the severity and priority of risks )just encourage team members to keep adding to the risks and as a Project Manager, you need to keep an eye and make sure the register is updated at least every week.

I strongly believe that Risks need to be managed continuously and explicitly throughout the project and there is no such thing as "implicit" management
...
1 reply by Mario Coquillat
Jan 09, 2019 4:59 AM
Mario Coquillat
...
Thanks Deepesh

You suggest to use a risk register, which is a more predictive approach. What about manage riks in a Kanban Board together with user stories?
Network:1313



Mario -

Risks can be managed similar to how they are in a predictive project but the main difference is that revisiting the risk management processes will happen more frequently.

It is important to surface critical solution or operational risks early and explore those early through options such as spikes, multiple candidate architectures and so on.

Kiron
...
1 reply by Mario Coquillat
Jan 09, 2019 5:00 AM
Mario Coquillat
...
Thanks Kiron

Spikes are one of the practices I suggested.
Network:201



Managing risk in agile environment is also important in my view. Although processes like continuous delivery, automated testing, short iterations help to eliminate certain types of challenges quickly, however there still are many categories of risks that needs continuous monitoring and a proactive action if it occurs. Keeping an eye on all risks is beneficial and recommended in agile delivery model as well.
...
1 reply by Mario Coquillat
Jan 09, 2019 5:09 AM
Mario Coquillat
...
I totally agree with your point of view.

Continuous Delivery, Automated Testing and short iterations will manage some categories of risks (tasks complexity, tasks size, processes, people) but not all of them.

So we need explicit risk management to manage them.
Network:110782



Mario,

I think risk must be managed the same way in all projects. In an Agile context, it should be more frequent, making it more efficient.

Vincent
...
1 reply by Mario Coquillat
Jan 09, 2019 5:10 AM
Mario Coquillat
...
Thanks Vincent
Network:1749



Traying to add something to comments above, few people know that to implement Agile mainly in the software field Barry Bohem´s Spiral model was the life cycle process selected as basement or foundation to create iterative-incremental process that help Agile based metods to create software. Then, my first recommendation is reading that process. When you read it, you will find that is based on risk management then Agile based method inherit that. Agile is based on risk management. Then, you can find implementations that can vary regarding frameworks (Scrum) or methods (DSDM for example) where you can find risk management implicit or explicit. At the end, the way to implement risk management is exactly the same than in other approaches. Remember: what could vary is tools and techniques according your organizational reality and initiative.
...
1 reply by Mario Coquillat
Jan 09, 2019 5:12 AM
Mario Coquillat
...
Thanks Sergio. I´ll read about Barry Bohem´s Spiral model.
Network:587



Jan 08, 2019 12:24 AM
Replying to Deepesh Rammoorthy, PMP®AgilePM®
...
The advantage with Agile is that since you meet your team more frequently , you are able to identify more risks and find updates to them more frequently .
Nothing stops you from following a standard risk management process

Identify the Risks
Prioritize them
Identify mitigating actions
Assign ownership
Actively manage them

Once you have setup a "Shared" risk register , (and there are very good EXCEL templates that auto calculate the severity and priority of risks )just encourage team members to keep adding to the risks and as a Project Manager, you need to keep an eye and make sure the register is updated at least every week.

I strongly believe that Risks need to be managed continuously and explicitly throughout the project and there is no such thing as "implicit" management
Thanks Deepesh

You suggest to use a risk register, which is a more predictive approach. What about manage riks in a Kanban Board together with user stories?
Network:587



Jan 08, 2019 6:58 AM
Replying to Kiron Bondale
...
Mario -

Risks can be managed similar to how they are in a predictive project but the main difference is that revisiting the risk management processes will happen more frequently.

It is important to surface critical solution or operational risks early and explore those early through options such as spikes, multiple candidate architectures and so on.

Kiron
Thanks Kiron

Spikes are one of the practices I suggested.
Network:587



Jan 08, 2019 7:01 AM
Replying to Vishakha Sharma
...
Managing risk in agile environment is also important in my view. Although processes like continuous delivery, automated testing, short iterations help to eliminate certain types of challenges quickly, however there still are many categories of risks that needs continuous monitoring and a proactive action if it occurs. Keeping an eye on all risks is beneficial and recommended in agile delivery model as well.
I totally agree with your point of view.

Continuous Delivery, Automated Testing and short iterations will manage some categories of risks (tasks complexity, tasks size, processes, people) but not all of them.

So we need explicit risk management to manage them.
Network:587



Jan 08, 2019 4:39 PM
Replying to Vincent Guerard
...
Mario,

I think risk must be managed the same way in all projects. In an Agile context, it should be more frequent, making it more efficient.

Vincent
Thanks Vincent
Network:587



Jan 08, 2019 4:47 PM
Replying to Sergio Luis Conte
...
Traying to add something to comments above, few people know that to implement Agile mainly in the software field Barry Bohem´s Spiral model was the life cycle process selected as basement or foundation to create iterative-incremental process that help Agile based metods to create software. Then, my first recommendation is reading that process. When you read it, you will find that is based on risk management then Agile based method inherit that. Agile is based on risk management. Then, you can find implementations that can vary regarding frameworks (Scrum) or methods (DSDM for example) where you can find risk management implicit or explicit. At the end, the way to implement risk management is exactly the same than in other approaches. Remember: what could vary is tools and techniques according your organizational reality and initiative.
Thanks Sergio. I´ll read about Barry Bohem´s Spiral model.
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"There is one way to find out if a man is honest: Ask him! If he says yes, you know he's crooked."

- Groucho Marx

ADVERTISEMENT

Sponsors