Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 1 00:00:01,309 --> 00:00:02,638 Now that we have a Gantt chart 2 2 00:00:02,638 --> 00:00:04,307 and critical path, 3 3 00:00:04,307 --> 00:00:07,668 we need to choose the reporting milestones, 4 4 00:00:07,668 --> 00:00:10,119 and it's relatively straightforward, because 5 5 00:00:10,119 --> 00:00:12,124 once you define the deliverables, 6 6 00:00:12,124 --> 00:00:14,575 everything gets easy. 7 7 00:00:14,575 --> 00:00:16,615 Milestones are simply of a subset 8 8 00:00:16,615 --> 00:00:18,426 of the existing deliverables 9 9 00:00:18,426 --> 00:00:20,446 that are important to stakeholders 10 10 00:00:20,446 --> 00:00:22,765 because they show significant achievement 11 11 00:00:22,765 --> 00:00:25,717 towards project completion. 12 12 00:00:25,717 --> 00:00:28,295 What's the purpose of milestones? 13 13 00:00:28,295 --> 00:00:30,756 Basically, to reduce the set of deliverables 14 14 00:00:30,756 --> 00:00:32,276 to a manageable number 15 15 00:00:32,276 --> 00:00:35,145 for reporting each month to the stakeholders. 16 16 00:00:35,145 --> 00:00:37,635 For example usually, you don't include minor deliverables 17 17 00:00:37,635 --> 00:00:41,875 like initial drafts, that would not be significant to them. 18 18 00:00:41,875 --> 00:00:45,025 On the other hand, you want to provide enough milestones 19 19 00:00:45,025 --> 00:00:47,014 to ensure the stakeholders have a good understanding 20 20 00:00:47,014 --> 00:00:49,105 of the project status every month, 21 21 00:00:49,105 --> 00:00:53,116 and can do their job of providing oversight. 22 22 00:00:53,116 --> 00:00:55,405 And if the project is contractual, 23 23 00:00:55,405 --> 00:00:57,626 milestones provide agreed checkpoints 24 24 00:00:57,626 --> 00:00:59,403 for interim payments. 25 25 00:00:59,403 --> 00:01:02,676 Particularly important on long contracts. 26 26 00:01:02,676 --> 00:01:05,711 For example, when all the material has been purchased, 27 27 00:01:05,711 --> 00:01:08,211 a partial payment can be made. 28 28 00:01:09,620 --> 00:01:11,942 How many milestones should there be? 29 29 00:01:11,942 --> 00:01:16,572 A rule of thumb is at least one every two months. 30 30 00:01:16,572 --> 00:01:20,241 This ensures enough granularity for stakeholder oversight. 31 31 00:01:20,241 --> 00:01:21,512 Not too much time goes by 32 32 00:01:21,512 --> 00:01:24,621 without an official reporting milestone. 33 33 00:01:24,621 --> 00:01:26,751 But this rule of thumb is very flexible. 34 34 00:01:26,751 --> 00:01:28,902 Two milestones can be on the same day 35 35 00:01:28,902 --> 00:01:32,929 if they are important enough to the stakeholders. 36 36 00:01:32,929 --> 00:01:34,241 And when you present the project plan 37 37 00:01:34,241 --> 00:01:35,451 at the end of planning, 38 38 00:01:35,451 --> 00:01:37,511 you sometimes receive input from the stakeholders 39 39 00:01:37,511 --> 00:01:40,771 to add more deliverables for milestone reporting. 40 40 00:01:40,771 --> 00:01:42,501 Perhaps a stakeholder says 41 41 00:01:42,501 --> 00:01:45,039 "I'd like to see the first draft of the training material 42 42 00:01:45,039 --> 00:01:47,302 as a milestone too, I really want insight 43 43 00:01:47,302 --> 00:01:49,653 into how that's going every month." 44 44 00:01:49,653 --> 00:01:52,192 Okay, no problem, you can make that deliverable 45 45 00:01:52,192 --> 00:01:54,692 a reporting milestone as well. 3856