Posted on

WBS – Healthcare Projects

Dick Billows, PMP
Dick Billows, PMP
CEO 4pm.com
Dick’s Books on Amazon

A key part of a good healthcare project plan is the work breakdown structure (WBS). The WBS for Healthcare Projects specifies the work assignment for every person working on the project.  It also specifies the deliverables the customer or sponsor will get. And it provides checkpoints for the organization’s management to track the project’s performance.

WBS – Healthcare Projects: Step One

Creating a good WBS – Healthcare Projects starts with defining the scope and major deliverables of the project with administrators, physicians and other caregivers.  Then you decompose or breakdown each of those deliverables into smaller deliverables until you get to the level of an individual assignment. When you break down the project scope into deliverables, you specify the end result you want from each assignment. That is not a list of what you want the assigned team member to do. As an example, you would not describe everything an ICU nurse on your team must do to create a new procedure. Instead, you would state that the ICU nurse must deliver a set of procedures that pass inspection by the state Department of Health. That is a measurable deliverable with an acceptance criteria that is crystal clear. When you define every assignment in the healthcare project WBS as a measurable deliverable, you clearly define the work assignments for every caregiver, technician, administrator and any outside consultants working on the project. The assignments or tasks in your WBS define exactly what a good job is for each assignment and how you will measure it.  WBS – Work Breakdown Structure – Main Page

 

WBS Work Breakdown Structure

WBS – Healthcare Projects: Step Two

The WBS also shows the methodology you will use on the project to produce the required deliverables. The WBS of a project that uses a waterfall methodology will be very different from a project that uses a design-build methodology. In the waterfall methodology project, you will complete very detailed front end planning before the team starts work. On a project that uses a design-build methodology, the team will begin work on the deliverables before all the plans are finished. If you use an agile methodology for the project, you will complete the deliverables iteratively with a great deal of interaction with the caregivers and administrators at every step. The WBS will include time for them to assess the results and change the specifications. That project’s WBS will look very different from a WBS using one of the other methodologies.Healthcare Project WBS

WBS – Healthcare Projects: Step Three

The healthcare project WBS must specify the testing and quality control procedures you will utilize at various checkpoints in the project. Some of the checkpoints may be the testing of equipment against manufacturer or regulator specifications. Other checkpoints may be a governmental comparison of what you have developed to the approved regulations and requirements.

WBS – Healthcare Projects: Step Four

If you know who will be working on your project, it is a good practice to give the team members an opportunity to talk about the acceptance criteria for the deliverables they will be producing. Allowing team members to take part in defining the healthcare project WBS entries and their acceptance criteria gives you two benefits. First, it sets up the estimating process so your team members become familiar with the tasks they’ll be asked to estimate. Second, their participation also gives you the benefit of the team members’ experience with similar projects. That’s an opportunity for you and the team to identify problems very early in the process.

WBS – Healthcare Projects: Summary

The aim of the WBS is to

  • give team members clear assignments that are deliverables
  • communicate the methodology you’ll use to produce the deliverables
  • specify the acceptance criteria for quality control and testing
  • provide management with checkpoints for tracking progress.

This sample lecture from our Healthcare Project Basics course focuses on developing a healthcare project WBS. The goal of the WBS is to give crystal-clear assignments to people working on the project and give management clear checkpoints on progress. It also provides a good basis for you, the project manager, to track project progress and do variance analysis.

 

To learn more about designing a good WBS for healthcare projects, consider taking one of our online healthcare project management courses. You’ll learn at your pace with an expert healthcare project manager as your coach.

Get free articles and videos like this every week

Posted on

Become a Project Manager

Dick Billows, PMP
Dick Billows, PMP
CEO 4pm.com
Dick’s Books on Amazon

There are many career paths you can use to Become a Project Manager and start a professional career. Project management offers career potential to men and women. The average salary for certified project managers topped $110,000 in the past year. Project management is also a skill demanded worldwide. The demand for project managers has remained strong despite economic ups and downs. In fact, in bad economic times organizations in the private and public sectors need to have projects to improve performance, cut costs or cope with diminished availability of resources. That gives project managers a lot of opportunities to change employers, geographic locations, as well as industries and the type of projects they manage. Project management is now seen as a separate skill from the technical knowledge of information systems or construction or manufacturing.  For many projects, particularly large ones, the project manager does not have to be a technical expert in the actual work of the project. Many organizations are coming to realize that what the project manager needs to be expert in is managing projects, teams, stakeholders, schedules and budgets. Project Management Careers Main Page

Become a Project Manager – Three Paths

Here are career three paths or situations we’ll explore:

  • a recent college graduate
  • a craftsperson who has worked their way up in the trades
  • a professional, like a systems analyst, accountant or operations manager, wanting to move into project management.

Become a Project Manager – Recent College Graduate

These days it’s difficult to find a job after you graduate from college, particularly if you don’t have a degree that is in demand. If you’re a person who pays attention to detail and is good on follow-through, a good option is getting a job as a project coordinator or assistant project manager. Usually no experience is required for these entry-level project management positions. Regardless of the title, the work will involve assisting a project manager on a large effort. Your work could include assisting with scheduling the project work, updating the schedule to show the team’s actual performance, documenting information to support change requests and expediting work on tasks by team members, outside contractors and vendors. Good performance in the entry-level position can earn you an opportunity to manage a small project on your own. That’s the first step up in your project manager career.

Become a Project Manager – Working Your Way Up in the Trades

Many project managers gain their first experience out of high school working in the trades or as a line employee. Good performance lets them move up to the supervisor or foreman level and many make the jump to project management at that point. They have a great deal of practical experience to offer. However, they must learn the basics of planning, scheduling, tracking and reporting so they can apply the best practices in project management to their years of practical experience. Usually their first project management assignment is assisting an experienced project manager and learning the ropes from them. Obviously training in the basics of project management is a big help in making this transition from the trades into the professional project manager ranks.

Become a Project Manager – Moving From Another Profession 

Still other people begin their career in one profession, such as information systems, civil/electrical/mechanical engineering, medicine/nursing or general management. After several years, theyBecome a Project Manager decide that project management is a better fit for their skills and long-term career opportunities. They equip themselves to make the move to project management by getting some basic training in the best practices. Then they market themselves using the combination of their current professional skills and their knowledge of managing projects.

 

Become a Project Manager- Summary

Each of these paths for getting into project management is possible because the demand for project managers is high. Few organizations have enough people who are able to consistently manage projects to produce results on time and within budget. All of the paths require one thing; that you know the best practices and can use the basic skills of project management. You can learn them in our project management basics courses. Take a look at the course in your industry specialty.

[button link=”http://162.144.114.198/~jwkdwgmy/it-project-basics-111/” style=”info” color=”red” window=”yes”]IT Projects[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/project-management-basics/” size=”medium” style=”info” color=”#1e14a8″ border=”#940940″ window=”yes”]Business[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/construction-project-basics-121/” style=”info” color=”red” window=”yes” bg_color=”00000000″]Construction[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/healthcare-project-basics-131-2/” style=”info” color=”#1e14a8″ window=”yes” bg_color=”00000000″]Healthcare[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/client-project-management/consulting-project-basics-online-141/” style=”info” color=”red” window=”yes” bg_color=”00000000″]Client Projects[/button]

 

Get free articles and videos like this every week

Posted on

WBS – Business & Operations Projects – Video

A critical part of your project plan is the work breakdown structure (WBS). The WBS for Business & Operations Projects is a lot more than a long list of tasks. It comes from a definition of the project scope which is the business benefit that the project will deliver. The project scope is stated as a metric, an acceptance criteria, and so is every component of the work breakdown structure. Those components are the deliverables, everything that’s required to deliver the business benefit. The aim of the WBS is to give crystal-clear assignments to people working on projects and give management clear checkpoints on progress. Every successful business and operations project also includes process changes in their organization. The WBS has to include the training that will increase the capability of the users. Finally, the WBS is structured with the particular methodology that the project will employ (waterfall, agile, iterative).  Main WBS – Work Breakdown Structure – Page

WBS Work Breakdown Structure

Dick Billows, PMP
Dick Billows, PMP
CEO 4pm.com
Dick’s Books on Amazon

WBS – Business and Operations Projects: Step One

The WBS is a decomposition of the project scope. You start by breaking down the scope into 4 to 7 major deliverables. Then you break down each of those major deliverables into smaller deliverables. You continue the process all the way down to tasks you will assign to the team members. To do this decomposition, you must define every task in the work breakdown structure with acceptance criteria. Those are the specific measures the customer or user will apply when deciding whether to accept the deliverable. An example of an acceptance criteria in a project for improving efficiency might be, “Project team members can complete their weekly timesheet in less than two minutes 90% of the time.” That defines a specific end result that you, as the project manager, will use in specifying user requirements and measuring team member performance.

WBS – Business and Operations Projects: Step Two

The WBS – Business & Operations Projects will show the methodology you will use on the project to produce the required deliverables. If you and the project sponsor have decided to use an agile methodology, the WBS will include multiple iterations in the creation of each deliverable. It would include time for the user to assess the result and change the specifications after each iteration. On the other hand, the classic waterfall project plan would include very detailed front end planning followed by execution of the plan.

WBS – Business and Operations Projects: Step Three

The WBS needs to specify the acceptance criteria for quality control and testing. Some testing tasks should include the number of transactions or samples that you will test. That ensures adequate time is estimated for the complete testing procedure. That includes any external testing of the deliverables during development or prior to acceptance. They should appear in the work breakdown structure to ensure enough hours of work for adequate testing and quality control are included in the schedule.

WBS – Business and Operations Projects: Step Four

Finally, if you know which team members will be doing the work on your project, it is a good practice to give them an opportunity to talk about the acceptance criteria for the deliverables they will be producing. Allowing team members to take part in defining the WBS entries and their acceptance criteria gives you two benefits. First, it sets up the estimating process so your team members become familiar with the tasks they’ll be asked to estimate. Second, their participation also gives you the benefit of the team members’ experience with similar projects. That’s an opportunity for you and the team members to identify problems very early in the process.

WBS – Business and Operations Projects: Summary

The aim of the WBS is to

  • give team members clear assignments that are deliverables
  • communicate the project methodology you’ll use to produce the deliverables
  • specify the acceptance criteria for quality control and testing
  • provide management with checkpoints on progress.

 

This sample lecture is from our online Project Management Basics course. It focuses on creating the work breakdown structure for small business projects. The focus is on creating a project plan and work breakdown structure that are tools for making clear, measurable assignments and tracking the team’s progress on those deliverables.

To learn more about designing a good WBS for Business & Operations projects, consider taking one of our online project management courses. You’ll learn at your pace with an expert project manager as your coach.

Get free articles and videos like this every week

 

Posted on

WBS – Construction Projects – Video

A key part of a good construction project plan is the work breakdown structure (WBS). The WBS – Construction Projects specifies the work assignment for every crew member, subcontractor, architect, and outside consulting engineer working on the project.  It also specifies the deliverables the customer will get. That definition is in the form of an objective measure like, “maintain 72° degrees temperature during operating hours.”

Dick Billows, PMP
Dick Billows, PMP
CEO 4pm.com
Dick’s Books on Amazon

WBS – Construction Projects: Step One

You begin by defining the scope and major deliverables of the project. Then you breakdown each of those deliverables into smaller deliverables until you get to the level of an individual assignment to a crew member or subcontractor. As you work through this breakdown process, you are specifying the end result you want from each assignment, not what you want them to do.

WBS Work Breakdown Structure

As an example, you wouldn’t describe everything that a framing contractor is supposed to do. Instead, the WBS would specify that the subcontractor is to frame the project according to plan and pass the local municipality’s rough framing inspection. The acceptance criteria of that deliverable is crystal-clear. With every assignment in the construction project WBS specified as a deliverable, you have clearly defined the work assignment for everyone working on the project. The assignments or tasks in the WBS define exactly what a “good job” is for each of those work assignments and how it will be measured.   WBS Work Breakdown Structure Main Page

WBS – Construction Projects: Step Two

Second, the work breakdown structure is also based on the construction methodology that will be used on the project. As an example, the WBS of a waterfall construction project will be very different from a project that uses a design-build methodology. In a waterfall methodology project, all the planning is completed before you start construction work. In a design-build methodology project, you begin construction work before all the plans are finished. And an agile methodology project will look very different from the first two types. Here you complete the components iteratively with a great deal of customer interaction and input at each step.

WBS – Construction Projects: Step ThreeWBS - Construction Projects

Third, the construction project WBS has to specify the testing and quality control procedures and acceptance criteria you will use at various checkpoints in the project. Some of these checkpoints may be the testing of materials, other checkpoints may be the governmental comparison of what you have built to the approved plan.

WBS – Construction Projects: Summary

The aim of the WBS is to

  • give crews and subcontractors clear assignments that are deliverables
  • communicate the construction methodology you’ll use to produce the deliverables
  • specify the acceptance criteria for quality control and testing
  • provide checkpoints on progress.

This sample construction project lecture is from our Construction Project Basics course. It covers how to develop the work breakdown structure (WBS) for smaller commercial and residential construction projects. The focus is on creating a project plan and work breakdown structure that are tools for making clear, measurable assignments and tracking the progress of crews and subcontractors on those deliverables. It also provides a good basis for you, the project manager, to track project progress and do variance analysis.

To learn more about designing a good WBS for construction projects, consider taking one of our online construction project management courses. You’ll learn at your pace with an expert construction project manager as your coach.

[button link=”http://162.144.114.198/~jwkdwgmy/construction-project-management/construction-project-certification/” style=”info” color=”red” window=”yes” bg_color=“00000000″]Construction[/button]


Get free articles and videos like this every week

Posted on

WBS – Information Technology Projects – Video

The work breakdown structure is the heart of a successful WBS – Information Technology project plan. The work breakdown structure (WBS) defines the deliverables in objectively measurable terms, like retrieve 6 months of customer history in 4 seconds. It fits the systems developmental methodology you will use in the project, like Agile, Waterfall, Iterative, etc.  It defines the users’ expectations about exactly what business result(s) they will get.  The WBS must cover the three components of successful implementation. It covers not only 1.)what the analysts and programmers will do but also 2.) the users’ process changes and 3.) the user training.

Dick Billows, PMP
Dick Billows, PMP
CEO 4pm.com
Dick’s Books on Amazon

WBS – Information Technology Projects: Step One

First, the WBS tells everyone what’s expected of them. You and the users start by breaking down the project scope into 4 to 7 major deliverables. Then you break down each of those major deliverables into smaller deliverables. You continue the process all the way down to tasks you will assign to the team members, information system staff and user staff. Yes, it includes assignments for the development staff and the users because both groups will complete tasks to deliver the project scope. To do this decomposition, you define every task in the work breakdown structure with acceptance criteria that is usually a metric. Those are the specific measures the user will apply when deciding whether to accept the deliverable. The WBS allows the sponsor and user management to track the progress of the project because every entry in the WBS is unambiguous; they are measurable.  WBS Work Breakdown Structure Main Page

WBS Work Breakdown Structure

WBS – Information Technology Projects: Step Two

Second, on an IT project the WBS also communicates the systems development methodology you’ll use on the project to produce the required deliverables. If you and the project sponsor have decided to use an Agile methodology, the WBS will include multiple iterations of each deliverable. It will include time for the user to evaluate the result and change the specifications after each iteration. On the other hand, the classic Waterfall project development would include very detailed front end planning followed by execution of the plan. So an IT project WBS done with a Waterfall methodology is very different from a WBS for an Agile systems development effort or any of the other IT methodologies.

WBS – Information Technology Projects: Step Three

Third, regardless of the methodology, a correctly developed WBS is not a list of activities or “to dos.” It is a list of acceptance criteria that define what a good job is on each of the WBS entries. As an example, if one or more programmers will write the code for a payroll data entry screen, you might define the acceptance criteria for that effort with a WBS entry like, “Payroll clerks can create new employee payroll records using the new GUI in less than three minutes 90% of the time.”  That tells both the programmers and the users involved what they’re going to get from this new GUI. When you define your WBS entries this way, you have the discussion and debate about the deliverable’s acceptance criteria before you even start work.

WBS – Information Technology Projects: Step Four

Fourth, the WBS needs to specify the acceptance criteria for quality control and testing. Some testing tasks should include the number of transactions that you will test. That ensures that adequate time is estimated for the complete testing procedure. That includes any external testing of the software during its development or prior to acceptance.  The tasks should also appear in the WBS so enough hours of work are allocated to the process and the resulting schedule for adequate testing and quality control.

WBS – Information Technology Projects: Step FiveWBS - Information Technology Projects

Fifth, if you know which team members will be doing the work on your project, it is a good practice to give them an opportunity to talk about the acceptance criteria for the deliverables they will be producing. Allowing team members to take part in defining the WBS entries and their acceptance criteria gives you two benefits. First, it sets up the estimating process so your team members become familiar with the tasks they’ll be asked to estimate. Second, this participation also gives you, the project manager, the benefit of the team members’ experience with similar projects. That’s an opportunity for you to identify problems very early in the planning process.

WBS – Information Technology Projects: Summary

The aim of the WBS is to

  • give clear assignments to system analysts, programmers and users
  • communicate the systems development methodology you’ll use to produce the deliverables
  • state the acceptance criteria on each of the deliverables and provide checkpoints on progress
  • specify the acceptance criteria for quality control and testing
  • set up the estimating and early problem solving processes

This sample IT project lecture from our IT Project Basics course focuses on developing the work breakdown structure for IT systems development projects. The focus is on creating a project plan and work breakdown structure that are tools for making clear, measurable assignments and tracking the progress of the deliverables.

To learn more about designing a good WBS for IT projects, consider our project management courses. You learn with an expert project manager as your coach.

[button link=”http://162.144.114.198/~jwkdwgmy/it-project-management/it-project-manager-certification-111-113/” style=”info” color=”red” window=”yes”]IT Projects[/button]

 

Get free articles and videos like this every week

 

Posted on

How To Do Risk Analysis

Here is How To Do Risk Analysis for your project. After you have identified the risks your project faces, you need to do a risk analysis to determine which ones call for a risk response and which do not. The purpose of risk analysis is to rank the list of identified risks in order of significance or importance.  Your risk analysis focuses on qualitatively assessing the probability that the risk will occur and the magnitude of its impact if it does. You will use this qualitative risk analysis to decide which risks are important enough to warrant a risk response. Risk Management Main Page

Dick Billows, PMP
Dick Billows, PMP
CEO 4pm.com
Dick’s Books on Amazon

How To Do Risk Analysis: Step 1 – Qualitative Analysis

Qualitative analysis assesses how much the risk could hurt the project but is doesn’t use any numbers. Qualitative analysis has the benefits of being cheap and fast but it lacks precision.  You can easily do qualitative analysis by meeting with three or four team members and stakeholders in the cafeteria for coffee. You list the risks you have identified that can possibly affect the project. For each risk, you ask them to assess whether it is very likely to occur, moderately likely to occur or unlikely to occur. When you have that information from each attendee, you ask them about how much damage the risk will cause if it does occur. Will it cause just a little damage, a medium amount of damage or a lot of damage?

As you can see, this is not a very precise method but it does give you the opinions of your stakeholders and team members. If you have any risks that are very likely to occur and will cause significant damage, you will plan a risk response for those risks. The less significant risks you have identified are things you will watch out for but you won’t plan a formal risk response for them. On smaller projects, you will probably limit the risk analysis to these qualitative techniques and planning risk response(s) for the significant risks.  Small Project Risk Management 

You may also decide that one or two risks are so significant you should preform a quantitative risk analysis.  The cost of the higher-level quantitative risk analysis probably requires the sponsor’s approval. Risk Responses

How To Do Risk Analysis: Step 2 – Quantitative Analysis

Quantitative risk analysis is both expensive and time-consuming. Usually, it is done only on very large projects which face very significant risks. Only in that situation could you justify the cost and weeks or months of effort which can go into a quantitative analysis. Regardless of which quantitative risk technique you utilize, the end result is the expected value of the risk. You calculate that by multiplying the probability of the risk occurring times the magnitude of the impact if it does occur.
Here’s an example. Let’s say your quantitative risk analysis determined there is a 0.001% chance that the company headquarters would be destroyed by a tornado during the coming four months. It also estimated that the magnitude of that risk (the damage that the tornado would cause) could be valued at $800,000. Now that risk probability is pretty small but the magnitude is pretty large. To combine them into a single number that lets you make a good decision, you  would multiply that probability times the magnitude and come up with an expected value of the risk of $800. What that expected value means is that if you did this project 10,000 times with the same tornado risk, the average damage would be $800. So you can’t justify spending more than that amount ($800) to avoid the tornado risk. The quantitative risk analysis says you can have only a very limited risk response program if you must keep the cost under $800, the expected value of the tornado risk.  Presenting Your Risk Plan

 

To learn more about how to manage project risks, consider one of our online project management courses. You work privately with a expert project manager. You control the schedule and pace and have as many phone calls and live video conferences as you wish.  Take a look at the courses in your specialty.

[button link=”http://162.144.114.198/~jwkdwgmy/it-project-management/it-project-manager-certification-111-113/” style=”info” color=”red” window=”yes”]IT Projects[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/business-project-management/business-project-manager-certification-101-103/” size=”medium” style=”download” color=”#1e14a8″ border=”#940940″ window=“yes”]Business[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/construction-project-management/construction-project-certification/” style=”info” color=”red” window=”yes” bg_color=“00000000″]Construction[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/healthcare-project-management-2/healthcare-project-manager-certification-2/” style=”info” color=”#1e14a8″ window=”yes” bg_color=“00000000″]Healthcare[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/client-project-certification-141-143/” style=”info” color=”red” window=”yes” bg_color=”00000000″]Client Projects[/button]

 

Posted on

Managing Project Risks Not Fighting Fires

Managing project risks is a touchy subject with project sponsors. The majority of executives who sponsor projects are hesitant to authorize risk management efforts. This is because in the past many executives have gotten burned by risk management efforts that cost a great deal of time and money and produced little or no results. So it’s hard to get the sponsor’s approval to do risk management. Often executives will say, “Start work and we will put out fires when they occur.” But firefighting is not the way to succeed on projects. Project Risk Management Main Page

Dick Billows, PMP
Dick Billows, PMP
CEO 4pm.com
Dick’s Books on Amazon

There is an unfortunate emphasis in many organizations on firefighting as opposed to careful planning. This includes planning for the risks the project faces. Many project sponsors like the idea of not committing to highly detailed project plans. They think, and rightly so, that this limits their ability to “be flexible” and make changes whenever they want. Project managers who buy into this thinking have happy sponsors in the beginning of the project because they can start work fast. In this situation, the team puts little effort into project planning and there certainly is no project risk management. Unfortunately, the same project managers are routinely surprised by risk events that easily could have been anticipated during the planning phase. Because there was no risk management, the team has to stop work and figure out what to do about the risk(s) that smacked them in the face.

Managing Project Risks The Wrong Way

Let’s think about what happens when a project manager and team rely on firefighting instead of having a well thought out risk response plan. Let’s talk about a specific example. A project manager is relying on an outside contractor to produce a “super tech” deliverable that is required by three major project deliverables. In other words the super tech is an input to three other deliverables. There had been discussion among the project team and the organization’s legal staff about the contract with this vendor. But the team had worked with him before and assumed the super tech deliverable would be exactly what they need.
The project has started fairly quickly because no detail plan is being formulated. Over the first month everything goes well but then the vendor calls and says, “Super tech is going to be delayed because four of my best people have just walked off the job to go to work for a competitor in California. I don’t know where the heck I’m going to find people to do your super tech work. But I’ll get to work on it right now and keep you posted.” The project manager tries to find out how much of a delay they’re facing and the vendor says there’s no way to tell at this point.” The project manager also reminds the vendor that there’s a contract requirement to deliver super tech by the end of June. The vendor says, “That’s a long way away. I’m sure we’ll get it worked out by then.”
The project team is stuck because they gave no thought to the possibility of the vendor being unable to produce the deliverable by the end of June. They had done no risk analysis or planning about this critical project deliverable. There was no contingency plan and no money to pay for hiring another contractor to do the work. They also hadn’t planned for the option of buying a pre-built or “canned” deliverable as a substitute for super tech. So the project team must stop work on other project activities while they and the project manager try to find other options for super tech. Even if they find a substitute, the project will be significantly late because of the delay.
This type of risk event occurs all the time.  People who try to respond to this type of risk with firefighting fail to recognize one thing. All the thinking that they’re going to do in this firefight should have been done as part of the risk management process.  Then they would have had a contingency plan approved by the sponsor which they could implement the moment the contractor called with bad news.

When the project is late and over budget because of a couple of these risk events the sponsor’s not happy. Project managers need to remind executives of these failed projects to “sell” them on the need for rimanaging project riskssk management on future projects. Presenting Your Risk Plan

Managing Project Risks The Right Way

A risk management process can pay big dividends, particularly when it is scaled to fit each project. In fact, the entire risk management effort for a small project can take place during lunch with the sponsor. The sponsor and project manager spend one hour to identify the risks, analyze them and plan ways to avoid or mitigate the significant ones. There are bare-bone risk management techniques that don’t require a lot of paper work. Small Project Risk Management 

To learn more how to manage project risks,  consider our online project management courses. You work privately with a expert project manager. You control the schedule and pace and have as many phone calls and live video conferences as you wish.  Take a look at the courses in your specialty.

[button link=”http://162.144.114.198/~jwkdwgmy/it-project-management/it-project-manager-certification-111-113/” style=”info” color=”red” window=”yes”]IT Projects[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/business-project-management/business-project-manager-certification-101-103/” size=”medium” style=”download” color=”#1e14a8″ border=”#940940″ window=“yes”]Business[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/construction-project-management/construction-project-certification/” style=”info” color=”red” window=”yes” bg_color=“00000000″]Construction[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/healthcare-project-management-2/healthcare-project-manager-certification-2/” style=”info” color=”#1e14a8″ window=”yes” bg_color=“00000000″]Healthcare[/button]

[button link=”http://162.144.114.198/~jwkdwgmy/client-project-certification-141-143/” style=”info” color=”red” window=”yes” bg_color=”00000000″]Consulting[/button]