Now let's talk about some actions that you'll have to take as a project manager.
First off we have corrective action.
This is where you're fixing a problem.
So you're realigning the project performance preventive action is where you don't want to make the mistake
again.
So you are insuring future performance.
Now corrective action and preventive action can go hand-in-hand and then it ties in with our next action
here which is defect repair.
So let me give you an example.
We have a thousand dollars to install in a building and we have four or five different groups of people
that are going out installing these doors.
Well we do some inspections so some quality control.
And we notice that about 50 of the 300 doors we've installed so far are installed incorrectly.
So we need to do corrective action which is also defect repair that we're fixing the problem or modifying
that nonconformists the doors aren't installed properly.
What we also do is we bring everyone together when we do a little bit of training so that we ensure
future performance so that everyone is installing the doors correctly from this point forward.
Now these actions corrective and preventive action and defect repair they require a change request.
Typically you're going to have to do a change request because it's time and money that you're spending
corrective action we're talking about current results who want to realign the project work back to our
project plan.
We want to make certain the work we're doing is in scope then getting rid of items that are not in scope
so scope creep or gold plating those are not acceptable here remember scope creep as our scopes getting
bloated by tiny changes or gold plating.
We're just trying to consume the budget by adding bells and whistles that wasn't really approved preventive
action.
We want things like safety training looking for problems or risk that could happen.
So this ties in to Chapter 11 on risk management the factory pair is we have a non-conforming product
like those doors that weren't installed properly.
So it kind of ties back to corrective action.
So you want to fix the problem and then we have defect repair validation to make sure it was fix that
when you go and fix the problem.
Make certain that it's of quality now that it's conforming to our requirements.
Then you have to do some updates here.
So you may have to look at your project documentation and your plans and what updates are happened.
So that may require a change request so changes to project documentation could be things like activity
less because now you have activities to redo the work.
Are there assumptions.
What about your lessons learned.
So you don't have to do this again and again and again.
We're going to learn from the problems we don't have it year so corrective action and preventive action
tie in together their requirements documentation see if the update your requirements make certain that
everything is conforming to the requirements who want clarity on requirements.
Are there any risk at it or stakeholder register comes into play here.
So these are all changes that could come about because of these actions and that these formally controlled
changes means you likely need a change request and of course you'll have updates to O.P..