In the project browser window (on the left side looks like a folder list), click on the object that looks like a folder, and is called “VBA Project (Name of your current file here)”, and then click on Modules → Module 1. Then, in MS-Project 2016 select View → Macros → Visual Basic (or Alt+F11 if you prefer) to bring up the Visual Basic editor. To use the macro, first make sure you aren’t using the custom field Flag 5 for anything you don’t want to lose (as the macro uses that field and will overwrite all the values in there). It’s not there any more but I’m republishing it here with his permission as I find it souseful (thanks Jack!). The macro to trace predecessors and successors in MS-Project was written by Jack Dahlgren and originally published on his (now defunct) site. It produces a version of the schedule filtered to show all the tasks that are predecessors (or successors if you prefer) of any non-summary task that you select. This approach should get you to the root cause of the delay, but it is repetitive, laborious, involves a lot of working through long lists ticking things off, and is not a particularly rewarding way to spend far too much time.Ī much better approach to trace predecessors and successors in MS-Project is to use a macro that does all this hard work for you in a few seconds.
Work backwards up this chain to see what is the root cause of the delay.If you didn’t find it, start with the first predecessor (say TaskID 111) of the main milestone, and filter the schedule by setting the successors field to show only those that have 111 as a successor.it took longer than expected), work backwards up this chain applying steps 1 & 2 but focusing on TaskID 222 to see what is the root cause of the delay. If you can’t see why this one was delayed (e.g. If you found it – great! Let’s say it was TaskID 222.Review all these tasks to see which one has moved and is causing the delay.Filter the schedule by setting the successors field to show only those that have 333 as a successor.Say the main delivery milestone is TaskID 333. So how do you find the cause of the delay? You’ve checked the edits you made, and they’re OK. You’ve made a bunch of edits based on conversations with PMs, and now your main delivery is showing significantly overdue. So you’ve created a useful programme schedule, and you are now using it to keep delivery on the right track.
0 kommentar(er)
