Showing posts with label Project Management. Show all posts
Showing posts with label Project Management. Show all posts

Wednesday, March 28, 2018

Risk Management in Projects

In projects, things often pan out differently than expected. Sometimes the unexpected works in favor of the project team but often the opposite is the case. To anticipate these events or keep them in check a proactive stance is needed. Risk management refers to the universe of activities and measures aimed at dealing with risks in order to keep a project under control.



What is Risk? 
Risk is defined as "The possibility of suffering harm or loss; danger." Even if we're not familiar with the formal definition, most of us have an innate sense of risk. We are aware of the potential dangers that permeate even simple daily activities, from getting injured when crossing the street to having a heart attack because our cholesterol level is too high. Although we prefer not to dwell on the myriad of hazards that surround us, these risks shape many of our behaviors. Experience (or a parent) has taught us to look both ways before stepping off the curb and most of us at least think twice before ordering a steak. Indeed, we manage personal risks every day.

Significance
Risk management helps the uninterrupted flow of activities in a project by hedging against undesirable events. This in turn creates confidence in the project, in third parties affected by the project and in the project team itself. Risk management activities require information; therefore they promote communication within the project and improve effectiveness of team efforts. Finally, risk management improves decision making in the project.

Types

There are two types of unexpected events in the course of a project

  • Known risks: these are identified potential problems such as the possibility of a strike when labor contracts expire. The exact consequences are unknown but the potential to harm project outcomes is evident.
  • Unknown risks: these are problems arising unexpectedly but seasoned project managers do expect them.

Risk Management Techniques
  • Identify Weaknesses: Risk analysis begins with identifying all potential weaknesses. Weaknesses are internal. One example is a product or service that does not meet the needs of the customer. Other examples include staffing shortages, unreliable employees and ineffective leadership. After an organization examines these and other areas for potential weaknesses, it can examine more closely different parts of the organization such as systems, finances, and human resources . Communication with other people may also bring to light some potential weaknesses within the organization.

  • Identify Threats : Threats are external factors that can negatively affect an organization. Identify all potential threats by looking into the parent company, the organization itself and the industry. Determine how threatening each could be to the organization and how vulnerable the organization is to an attack from competitors. Other examples of external threats include natural disasters, war, disclosure, hackers, theft, errors in data entry and changes in the economy.
  • Estimate Risks : After each threat and weakness has been identified, the next step is to determine how damaging they are or could be. These threats and weaknesses may or may not negatively impact the organization. To calculate the value of one of these risks, take the probability of the threat taking place and multiply it by the cost of fixing the damage caused by the threat.
  • Manage Risks:  An organization must manage the risks once it knows the value of each risk. To be cost-effective, spend less money eliminating a risk than the amount it would cost to resolve the aftermath if the event occurs. If the event occurs, and it will not cost much to resolve, it may not even be worth the time and money spent eliminating it. Managing risks can be done by using existing assets to improve methods, transfer responsibilities or improve internal controls. In addition, a contingency plan can manage risks by creating a plan that will reduce the effect of the risk, should it occur. Investing in new resources is another way to manage risks.
  • Critical Path : The critical path refers to specific tasks in a project that are necessary for the successful completion of the project. The tasks are displayed in flow chart or diagram along with the amount of time it should take to complete each one. The tasks must be completed in the correct order; if one task does not get complete, it could hold up the entire project and risk missing the completion date. Manage the risk by ensuring the tasks get completed in order and on time, and prepare a contingency plan.
  •  


Steps


The risk management framework comprises four processes:

  1. Identify risks: Risk management starts with identifying potential problems in the course of the project. Since "all possible problems" can be a large number, it is necessary to prioritize and focus on the most disruptive ones.
  2. Develop response plans: Every risk response attempts to reduce the probability and/or the impact of risks. The outcome of this phase is a risk log. A risk log is the full list of risks the project team will actively manage and the tasks associated with managing each risk.
  3. Establish reserves: Usually a project budget contains some reserves for dealing with risks. With detailed risk planning done, a much more accurate assessment of how much money to allocate for known risks and unknown risks can be done.
  4. Continuous risk management: Continuous risk management is the conscious repetition of risk identification, response development and risk planning. At regular intervals known risks are reassessed and the team searches for new risks

Role
Risk management is not a separate function in the project management process; it complements all management functions: definition, planning and control. The first risks surface in the project definition phase. Tackling risks requires reserves, hence risk management has an important feed into the planning function. The control function tries to keep the project on track, therefore risks that can disrupt the flow of activities are of prime concern.

Considerations
Despite the benefits of risk management, it is not used in every project. First, the project team may not be familiar with risk management and its associated benefits. Second, some people do not relish acknowledging the existence of risks because of the ostrich mentality. Also some mangers think if risks turn up in their project, it would be considered a sign of their poor management. Third, risk management is costly and its yield is not easy to determine. Fourth, some companies claim they do not have the time and capacity to indulge in risk management.

Ensuring Customer Satisfaction

There are four main questions that your CEO could ask you about a very visible or critical project you may be managing. You better be ready to answer these questions and back them up with proof.

The questions are:

  • Is the project on Budget?
  • Is the project on time?
  • Is the customer satisfied?
  • Is the project going to deliver a usable solution?

Let us discuss the ‘Customer Satisfaction’ issue.

Always Keep the Customer in the communication Loop.

Sometimes we feel that we have to solve problems before we discuss them with the customer. If the solution is easy and quick, that may be the case. But in general, the customer is much happier if they are made aware of issues by you in a timely manner rather than hear about them after the fact (when they are fixed) or through some other channel or when they become critical emergencies.

That does not mean that we should keep the customer informed on each issue, but at least on the issues, they may be sensitive. Always contact the customer with your alternate solutions with merits & de-merits as you perceived. Try to sell the solution you feel the best. But be open to listen to what the customer says. Give him opportunity to suggest an innovative solution.



Be Consistent

The customer sees you as the delivery person and the individual who is responsible for making sure that their million dollars is well spent on the project. You wouldn’t want an erratic or inconsistent individual as your financial planner and I’m certain that the customer doesn’t want that for their project manager either.

Deliver status reports when you say you will. Conduct status meetings regularly, deliver error-free documents, provide accurate project schedules, and always do your best to ensure your team hits the big deadlines. Consistency shows leadership and breeds confidence.

Keep the Project Moving Forward

Make sure everyone knows what they’re responsible for at any given time. They won’t be looking at down time due to uncertainty and your resources will

remain engaged and working on your tasks. Let them know, exactly what is expected from them, when & how (e.g. templates of deliverables).

Likewise, keep on top of the schedule and the resource forecasts so you know when you need to engage new resources to keep the new tasks on target as well. The goal is to not let the project stall. If it stalls for customer funding, you can’t do much about that. But don’t let it stall because of you or your team or lack of resources. Customer satisfaction can drop like a rock in those cases and all momentum can be lost quickly. SAP resources are difficult to get in the market. Plan for the resources in advance.

Monitor Scope Closely

Creeping of scope is the most dangerous factor working against customer satisfaction, timeline as well as budget. Do not allow to creep the scope out of your control. Raise signal whenever you feel that you are loosing control on the scope. In terms of customer satisfaction, it will ensure that the right tasks are getting done in the right timeframe.

Delivering a usable solution

There are four main questions that your CEO could ask you about a very visible or critical project you may be managing. You better be ready to answer these questions and back them up with proof.

The questions are:


  • Is the project on Budget?
  • Is the project on time?
  • Is the customer satisfied?
  • Is the project going to deliver a usable solution?
  • Let us discuss how to deliver a usable solution.


Never Assume the Customer Knows What They Want

We need to satisfy customer, and all we have to do is build to their requirements, right? Wrong! Be sure to ask the right questions up front and don’t be afraid to ask the customer to go back to their end users and SMEs and make sure that they understand what the final solution really needs to be.

The best way to implement ERP is ‘One organization – One way of working’. But over the years, different departments of the customer organization have developed in different directions. They might be using different stand-alone softwares. With introduction of an ERP (e.g. SAP), they need to change their style of working. They may not be ready for the same & the trouble starts. You must be firm on the strategy you decided before starting the project.

Many times though don’t truly know that when the engagement starts. If that is the case, one of two things happens:

It becomes apparent part way through the engagement and then the customer is faced with change orders, a stretched out timeline, budget overruns due to rework, and a lot of frustration for both teams.
It doesn’t become apparent until deployment when the end user finally gets their hands on it and it’s not what everyone dreamed it would be. Sure, you built to the customer specs, but the lasting legacy is that the customer has an unusable solution and the finger often gets pointed at you and the delivery team.
Assemble a Skilled Delivery Team

As with any engagement, the more applicable skills your team has for delivering on the engagement, the better chance you have for success. In case of SAP, it is difficult to get exactly matched skill sets. Try to get external help, if the skills not available with your organization.

Track Requirements

During requirement analysis and Design, map out the customer requirements well and manage those requirements closely. Keep track of where those requirements are implemented in the final solution. Missed requirements mean a solution that doesn’t match your customers documented needs.

Test and Re-Test

Have the customer build their own test cases and also use those during your own system tests prior to UAT along with your own test cases. Make sure the customer has solid, knowledgeable resources engaged for the User Acceptance Testing. Ensure that the end-client gets enough time to complete the UAT.

(UAT) sessions and definitely get their signoff on UAT once it’s completed.

A well-tested system goes along way in ensuring that the delivered system will work for the customer.

Get All Signoffs

Sign-off requirements, prototype design, UAT and all other documents. Do not rush to start next phase of the project unless previous phase is signed off by the customer. Ensure that the signing customer is authorized by their management.

Keeping budget under control

There are four main questions that your CEO could ask you about a very visible or critical project you may be managing. You better be ready to answer these questions and back them up with proof.

The questions are:

  • Is the project on Budget?
  • Is the project on time?
  • Is the customer satisfied?
  • Is the project going to deliver a usable solution?

Keep watch on Scope
Scope of the project is the foundation document of your project. Understand thoroughly the meaning of the scope defined & make it clear before starting the project. Spilling of the scope is the first enemy of your budget.

Forecast resources carefully
Resources are expensive. Decide the skill-set required. Choose the resources carefully. Communicate the deliverables clearly.

Perform Project Budget Analysis on weekly basis
Identifying issues early can help in correcting the issues before they become ‘Problem’.
Inform customer, if necessary.

Project Management : Managing Time