Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 1 00:00:01,400 --> 00:00:03,723 How does gathering project requirements work? 2 2 00:00:04,640 --> 00:00:08,020 Business analysts are the professional requirements experts, 3 3 00:00:08,020 --> 00:00:10,670 and should be relied on to lead requirements gathering 4 4 00:00:10,670 --> 00:00:12,143 whenever they are available. 5 5 00:00:13,590 --> 00:00:16,040 They sometimes work for the customer and give the 6 6 00:00:16,040 --> 00:00:17,840 requirements to the project manager. 7 7 00:00:18,800 --> 00:00:22,570 However, whenever possible best practice recommends 8 8 00:00:22,570 --> 00:00:25,107 the business analyst work under the supervision of 9 9 00:00:25,107 --> 00:00:27,900 the project manager, who can help them avoid the common 10 10 00:00:27,900 --> 00:00:30,780 mistake of making the customer happy 11 11 00:00:30,780 --> 00:00:32,710 by including much more than required 12 12 00:00:32,710 --> 00:00:34,300 by the project objective, 13 13 00:00:34,300 --> 00:00:37,093 thereby avoiding scope creep before it even starts. 14 14 00:00:38,900 --> 00:00:40,520 Whether you have business analysts 15 15 00:00:40,520 --> 00:00:42,600 or do requirements gathering yourself, 16 16 00:00:42,600 --> 00:00:46,200 the key is to interview all the stakeholders. 17 17 00:00:46,200 --> 00:00:49,750 Don't miss anyone, especially support groups like 18 18 00:00:49,750 --> 00:00:52,340 operations, privacy, legal, contracts, 19 19 00:00:52,340 --> 00:00:54,410 regulatory agencies, etc., 20 20 00:00:54,410 --> 00:00:57,910 as they might know really important time and cost drivers 21 21 00:00:57,910 --> 00:00:59,113 no one else does. 22 22 00:01:00,900 --> 00:01:03,700 The classic starting interview question is simply, 23 23 00:01:03,700 --> 00:01:07,403 what is needed to meed the objective? 24 24 00:01:09,290 --> 00:01:11,760 Ask a list of questions you prepared before hand, 25 25 00:01:11,760 --> 00:01:13,410 depending on the type of project. 26 26 00:01:15,240 --> 00:01:18,600 Ask the �why� question as often as required 27 27 00:01:18,600 --> 00:01:21,163 to drill down and find the real need. 28 28 00:01:22,690 --> 00:01:26,460 And then a great final question is open ended query. 29 29 00:01:26,460 --> 00:01:28,620 What else do I need to know? 30 30 00:01:28,620 --> 00:01:31,500 You often get really useful information with this question 31 31 00:01:31,500 --> 00:01:33,580 that you hadn't thought of. 32 32 00:01:33,580 --> 00:01:37,680 And keep asking it until they say, almost always with the same 33 33 00:01:37,680 --> 00:01:40,617 language, "I guess that's everything". 34 34 00:01:41,910 --> 00:01:44,393 Then you know you got everything you can. 35 35 00:01:45,870 --> 00:01:49,410 And, if appropriate, document any key scenarios, workflows, 36 36 00:01:49,410 --> 00:01:52,250 or use cases needed to understand the amount of work 37 37 00:01:52,250 --> 00:01:53,350 that will be required. 38 38 00:01:55,330 --> 00:01:58,720 Business analysts are the professionals in this process, 39 39 00:01:58,720 --> 00:02:01,600 but it is so important, if there are none available, then 40 40 00:02:01,600 --> 00:02:02,833 just do it yourself. 41 41 00:02:04,650 --> 00:02:08,120 By the way, B.A.'s have their own professional organization, 42 42 00:02:08,120 --> 00:02:10,620 the International Institute of Business Analysis 43 43 00:02:10,620 --> 00:02:12,043 at IIBA.org. 3842