1 00:00:06,960 --> 00:00:12,030 Now let's talk about some actions that you'll have to take as a project manager. 2 00:00:12,030 --> 00:00:14,230 First off we have corrective action. 3 00:00:14,250 --> 00:00:16,900 This is where you're fixing a problem. 4 00:00:16,980 --> 00:00:23,100 So you're realigning the project performance preventive action is where you don't want to make the mistake 5 00:00:23,100 --> 00:00:23,630 again. 6 00:00:23,630 --> 00:00:27,150 So you are insuring future performance. 7 00:00:27,360 --> 00:00:33,360 Now corrective action and preventive action can go hand-in-hand and then it ties in with our next action 8 00:00:33,360 --> 00:00:35,700 here which is defect repair. 9 00:00:35,700 --> 00:00:37,520 So let me give you an example. 10 00:00:37,620 --> 00:00:45,330 We have a thousand dollars to install in a building and we have four or five different groups of people 11 00:00:45,330 --> 00:00:47,540 that are going out installing these doors. 12 00:00:47,790 --> 00:00:51,370 Well we do some inspections so some quality control. 13 00:00:51,630 --> 00:00:59,760 And we notice that about 50 of the 300 doors we've installed so far are installed incorrectly. 14 00:00:59,760 --> 00:01:06,600 So we need to do corrective action which is also defect repair that we're fixing the problem or modifying 15 00:01:06,600 --> 00:01:10,250 that nonconformists the doors aren't installed properly. 16 00:01:10,310 --> 00:01:15,890 What we also do is we bring everyone together when we do a little bit of training so that we ensure 17 00:01:15,900 --> 00:01:21,870 future performance so that everyone is installing the doors correctly from this point forward. 18 00:01:22,500 --> 00:01:29,180 Now these actions corrective and preventive action and defect repair they require a change request. 19 00:01:29,180 --> 00:01:34,410 Typically you're going to have to do a change request because it's time and money that you're spending 20 00:01:36,010 --> 00:01:41,650 corrective action we're talking about current results who want to realign the project work back to our 21 00:01:41,650 --> 00:01:42,880 project plan. 22 00:01:43,180 --> 00:01:48,880 We want to make certain the work we're doing is in scope then getting rid of items that are not in scope 23 00:01:48,880 --> 00:01:55,270 so scope creep or gold plating those are not acceptable here remember scope creep as our scopes getting 24 00:01:55,270 --> 00:01:58,600 bloated by tiny changes or gold plating. 25 00:01:58,630 --> 00:02:05,520 We're just trying to consume the budget by adding bells and whistles that wasn't really approved preventive 26 00:02:05,520 --> 00:02:06,030 action. 27 00:02:06,030 --> 00:02:12,390 We want things like safety training looking for problems or risk that could happen. 28 00:02:12,390 --> 00:02:22,200 So this ties in to Chapter 11 on risk management the factory pair is we have a non-conforming product 29 00:02:22,200 --> 00:02:24,860 like those doors that weren't installed properly. 30 00:02:24,870 --> 00:02:27,280 So it kind of ties back to corrective action. 31 00:02:27,460 --> 00:02:33,000 So you want to fix the problem and then we have defect repair validation to make sure it was fix that 32 00:02:33,330 --> 00:02:35,360 when you go and fix the problem. 33 00:02:35,370 --> 00:02:40,640 Make certain that it's of quality now that it's conforming to our requirements. 34 00:02:41,540 --> 00:02:43,700 Then you have to do some updates here. 35 00:02:43,720 --> 00:02:50,370 So you may have to look at your project documentation and your plans and what updates are happened. 36 00:02:50,450 --> 00:02:56,780 So that may require a change request so changes to project documentation could be things like activity 37 00:02:56,780 --> 00:03:00,290 less because now you have activities to redo the work. 38 00:03:00,290 --> 00:03:01,780 Are there assumptions. 39 00:03:01,990 --> 00:03:03,530 What about your lessons learned. 40 00:03:03,530 --> 00:03:07,030 So you don't have to do this again and again and again. 41 00:03:07,040 --> 00:03:12,800 We're going to learn from the problems we don't have it year so corrective action and preventive action 42 00:03:12,800 --> 00:03:19,010 tie in together their requirements documentation see if the update your requirements make certain that 43 00:03:19,010 --> 00:03:23,740 everything is conforming to the requirements who want clarity on requirements. 44 00:03:23,750 --> 00:03:28,420 Are there any risk at it or stakeholder register comes into play here. 45 00:03:28,580 --> 00:03:35,560 So these are all changes that could come about because of these actions and that these formally controlled 46 00:03:35,560 --> 00:03:40,850 changes means you likely need a change request and of course you'll have updates to O.P..