Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 1 00:00:01,015 --> 00:00:02,852 How much detail should go 2 2 00:00:02,852 --> 00:00:05,207 into the requirements document? 3 3 00:00:05,207 --> 00:00:07,536 When should you add more? 4 4 00:00:07,536 --> 00:00:10,757 If you're in any doubt you've got all the cost drivers, 5 5 00:00:10,757 --> 00:00:13,216 then preform additional investigation, 6 6 00:00:13,216 --> 00:00:14,847 since the most common project problem 7 7 00:00:14,847 --> 00:00:18,699 is missing essential requirements during planning. 8 8 00:00:18,699 --> 00:00:20,782 When should you add less? 9 9 00:00:21,643 --> 00:00:25,565 Don't include anything not essential to the objective. 10 10 00:00:25,565 --> 00:00:28,046 No �nice to haves� and �while we're at its� 11 11 00:00:28,046 --> 00:00:30,721 that will complicate the main goal. 12 12 00:00:30,721 --> 00:00:34,113 And stop above the level of how. 13 13 00:00:34,113 --> 00:00:38,040 Design is too costly for planning, too much information, 14 14 00:00:38,040 --> 00:00:42,373 and too restrictive on work once the project starts. 15 15 00:00:44,268 --> 00:00:46,761 Then put all the requirements in a formal document 16 16 00:00:46,761 --> 00:00:49,551 and circulate to the stakeholders. 17 17 00:00:49,551 --> 00:00:51,844 There are lots of different names that can be used 18 18 00:00:51,844 --> 00:00:54,130 depending on the organization and their methodology. 19 19 00:00:54,130 --> 00:00:55,632 But a common name that works fine, 20 20 00:00:55,632 --> 00:01:00,419 is simply, the Project Requirements Document or PRD. 21 21 00:01:00,419 --> 00:01:04,279 And then, it is essential to have the customer review 22 22 00:01:04,279 --> 00:01:07,861 and prove the requirements in writing. 23 23 00:01:07,861 --> 00:01:10,272 Hold review meetings with relevant users 24 24 00:01:10,272 --> 00:01:11,967 from customer organization, 25 25 00:01:11,967 --> 00:01:14,579 walk through every requirement to obtain any changes 26 26 00:01:14,579 --> 00:01:17,704 or agreement, and keep holding these meetings 27 27 00:01:17,704 --> 00:01:20,454 until the requirements stabilize. 28 28 00:01:21,349 --> 00:01:23,052 State more than once: 29 29 00:01:23,052 --> 00:01:25,630 �Experience shows that any missed requirement 30 30 00:01:25,630 --> 00:01:28,436 will be five to ten times more disruptive and costly 31 31 00:01:28,436 --> 00:01:31,190 if it needs to added once the project is under way, 32 32 00:01:31,190 --> 00:01:34,190 so let's make sure we have them all.� 33 33 00:01:35,305 --> 00:01:37,448 And it's very helpful if you can say: 34 34 00:01:37,448 --> 00:01:40,057 �And the costs for any additions made later will come 35 35 00:01:40,057 --> 00:01:41,640 out of your budget.� 36 36 00:01:42,666 --> 00:01:44,197 At the end of this process, 37 37 00:01:44,197 --> 00:01:47,611 you have an agreed, baselined set of requirements 38 38 00:01:47,611 --> 00:01:52,073 that capture what needs to be done to meet the objective, 39 39 00:01:52,073 --> 00:01:54,323 and put you in the best position possible 40 40 00:01:54,323 --> 00:01:57,527 to plan the rest of the project. 41 41 00:01:57,527 --> 00:01:59,194 Well worth the time. 3599