Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 1 00:00:01,260 --> 00:00:03,230 Now let's look at the practical essentials 2 2 00:00:03,230 --> 00:00:05,470 of preparation of the most detailed description of the 3 3 00:00:05,470 --> 00:00:08,083 project scope, the requirements. 4 4 00:00:09,540 --> 00:00:11,870 The first work product you produce during planning 5 5 00:00:11,870 --> 00:00:13,343 are the requirements. 6 6 00:00:14,240 --> 00:00:16,680 Sometimes these are documented as the last step 7 7 00:00:16,680 --> 00:00:19,670 of initiation, however gathering requirements 8 8 00:00:19,670 --> 00:00:22,350 can be a fair amount of effort, so it's better 9 9 00:00:22,350 --> 00:00:24,370 if initiating is kept to the minimum, 10 10 00:00:24,370 --> 00:00:27,310 then a planning budget allocated, then the first step of 11 11 00:00:27,310 --> 00:00:30,093 planning being preparation of the requirements. 12 12 00:00:31,610 --> 00:00:35,480 The requirements are simply the detail behind the objective. 13 13 00:00:35,480 --> 00:00:39,440 All the functions, features, quantities, standards 14 14 00:00:39,440 --> 00:00:42,090 and other information the project result needs to meet 15 15 00:00:42,090 --> 00:00:45,180 the objective and the planning team needs to know 16 16 00:00:45,180 --> 00:00:47,453 to put together a full and accurate plan. 17 17 00:00:49,050 --> 00:00:52,070 Missing requirements is one of the most frequent causes 18 18 00:00:52,070 --> 00:00:55,000 of project problems so you want to make sure 19 19 00:00:55,000 --> 00:00:56,503 you do a complete job. 20 20 00:00:57,420 --> 00:01:00,410 For example, here's a quote from a report on a failed 21 21 00:01:00,410 --> 00:01:03,373 project that captures a very common situation, 22 22 00:01:04,407 --> 00:01:07,040 "It was a classic case of not getting the requirements 23 23 00:01:07,040 --> 00:01:09,250 sufficiently defined from the beginning. 24 24 00:01:09,250 --> 00:01:14,250 And so it required a continuous redefinition of requirements 25 25 00:01:14,560 --> 00:01:17,520 that had a cascading effect on what had already 26 26 00:01:17,520 --> 00:01:19,277 been designed and produced." 27 27 00:01:20,500 --> 00:01:22,183 170 million dollar blowup. 28 28 00:01:23,390 --> 00:01:25,400 This will sound familiar to many people 29 29 00:01:25,400 --> 00:01:27,620 that have worked on projects. 30 30 00:01:27,620 --> 00:01:30,550 Doing a good job on requirements gathering up front 31 31 00:01:30,550 --> 00:01:31,523 is the solution. 32 32 00:01:32,849 --> 00:01:37,310 At the same time, it is also possible to go too far. 33 33 00:01:37,310 --> 00:01:40,180 Sometime a project is seen as an opportunity to address 34 34 00:01:40,180 --> 00:01:43,810 all the problems an organization has, so it is loaded up 35 35 00:01:43,810 --> 00:01:46,853 far beyond the ability of one effort to solve. 36 36 00:01:48,000 --> 00:01:49,420 Here's a quote on a failed project 37 37 00:01:49,420 --> 00:01:51,313 that captures this common mistake. 38 38 00:01:52,237 --> 00:01:55,610 "We started with a big bang approach and put every 39 39 00:01:55,610 --> 00:01:58,060 possible requirement into the program, 40 40 00:01:58,060 --> 00:02:01,307 which made it very large and very complex." 41 41 00:02:02,330 --> 00:02:03,813 A one billion dollar blowup. 42 42 00:02:05,490 --> 00:02:06,520 This is one of the reasons 43 43 00:02:06,520 --> 00:02:08,850 the initiation stage is so helpful. 44 44 00:02:08,850 --> 00:02:12,310 If you define a specific need, agree a one sentence 45 45 00:02:12,310 --> 00:02:15,820 objective to meet that need and then keep requirements 46 46 00:02:15,820 --> 00:02:18,950 gathering to respond just to that objective, 47 47 00:02:18,950 --> 00:02:20,450 there is a much greater chance of defining 48 48 00:02:20,450 --> 00:02:23,200 a manageable size, efficient project 49 49 00:02:23,200 --> 00:02:24,950 that will do just what it needs to. 50 50 00:02:26,430 --> 00:02:29,840 So strike the right balance. 51 51 00:02:29,840 --> 00:02:33,810 Interview everyone and make sure you identify all the 52 52 00:02:33,810 --> 00:02:36,740 requirements required to meet the objective and will drive 53 53 00:02:36,740 --> 00:02:38,343 schedule and cost. 54 54 00:02:39,400 --> 00:02:42,030 But don't go beyond the objective and add requirements 55 55 00:02:42,030 --> 00:02:45,793 that should really be addressed by separate projects. 4947