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

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

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 - ar...

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims: Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)

High-Tech Yuga

Search This Blog