Skip to main content

How to overcome from project challenges? - 9) Inadequate risk management

Poor risk management has the ability to severely impact your project.

Impacts of poor risk management leads to:

  1. Poor User Adoption
  2. Unrealized Benefits
  3. Late-running Projects
  4. Overspent Budgets
  5. Unhappy Clients
  6. Reputational Damage
  7. Project Failure
When we are failed to identify risk, Your project will failure because you failed to predict the risks of changing conditions.
You could lose enormous investment dollars if you fail to anticipate the risks the project.
You could suffer irreparable damage to your company's reputation by failing to prepare to manage difficulties.

It is the job of every project manager to come up with alternate plans that the team may adopt if the project begins to spiral out of control.
Having a project risk management system helps in identifying the types of risks and mitigating them. Having a contingency plan in place is critical.
This plan should identify all risks that the course of action to be taken if they materialize it.

The risk will be any one below category:



Follow below Risk Management Process:

Strategies for managing risk:
Avoid
When you avoid the risk it means you change your plan to completely eliminate the probability of the risk occurring or the effect of the risk if it does occur.

Transfer
Risk transference occurs when the negative impact is shifted to a third party, such as through an insurance policy or penalty clause in a contract. The risk may still occur however the financial impact will be somewhat displaced.

Risk transference usually involves some type of contractual agreement.

Mitigate
Risk mitigation occurs when you proactively change the plan to minimize the impact or probability of the risk occurring. Risk mitigation does not eliminate the risk and as such there will be some residual risk remaining.

A mitigation plan is proactive and aims to prevent or minimize the impact of a risk, while a contingency plan is reactive and addresses risks that have already occurred.

A mitigation plan is a risk response strategy that reduces the likelihood or impact of a risk occurring. For example, wearing a helmet or seatbelt is a mitigation plan. 

A contingency plan is a risk response strategy that outlines specific actions to be taken if a potential risk becomes a reality. For example, applying for accident insurance is a contingency plan.

There are three proactive approaches to handling a negative risk, also called a threat:

Avoid – eliminate the risk
Transfer – shift the impact to a 3rd party
Mitigate – decrease the probability or impact

Comments

Popular posts from this blog

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

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .