Skip to main content

Risk Contingency Plan Vs Mitigation Plan

 Risk Contingency Plan Vs Mitigation Plan


Contingency plan: (Reactive)

The Project Management Institute defines contingency planning as, “involving defining action steps to be taken if an identified risk event should occur."

A contingency plan in project management is a defined, actionable plan that is to be enacted if an identified risk becomes a reality. 

It is essentially a “Plan B”, to be put in place when things go differently than expected for a "Plan A".

The essential components of an effective risk contingency strategy are:

  • Make a list of risks
  • Weigh risks based on severity and likelihood
  • Identify important risks
  • Conduct a business impact analysis
  • Create contingency plans for the biggest risks
  • Get approval for contingency plans
  • Share your contingency plans
  • Monitor contingency plan
Example for contingency plan:
A brokerage company may have a backup power generator to ensure that trades can be executed in the event of a power failure, preventing possible financial loss.

Synchronise data with a second data centre and switch operations to the second data centre in the event of the first one going down.

Mitigation Plan: (Proactive)

Risk mitigation describes a process by which a project reduces its exposure to risk and works towards minimizing the likelihood of any issues arising during the project.

It involves a process that we’ll explore in a moment but essentially addresses the top risks to fully protect the project.

The essential components of an effective risk mitigation strategy are:

  • Identifying likely risks
  • Prioritizing risk 
  • Preparation and responses
  • Monitoring
  • Updating the risk mitigation plan

The key difference between a contingency plan and a mitigation plan is that a contingency plan is reactive, while a mitigation plan is proactive.

Example for Mitigation Plan:

Airlines create risk mitigation plans to operate flights that are profitable and safe for all parties. They train pilots and check systems to limit internal risks and create guidelines that specify acceptable flying conditions.

Comments

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - archite

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable