In this article we will demonstrate a simple solution that answers the question of “how to compare different MPP files side-by-side”. The temptation to just link off the summary task is high, and I wonder if in this case that might just be the best thing to do.Project and Program Managers often have to open two different Microsoft Project files and compare different versions of MPP project plan between each other.Ī common use case would be when a Project Manager wants to compare a project plan created by the planner with a project plan that a team member “updated”.
It's a bit vulnerable to me making a mistake, although it is at least easy to pick out on the gantt when the milestone isn't right at the end of the summary task, as it should be. If I want a milestone to capture "all migrations complete", I need to work down the list of 30 tasks picking out the end of each chain and adding it in to the predecessors. Most are manually scheduled, as the constraints dictating when we can Total of about thirty tasks, most of which have no dependencies between them, although some do. The question - I've got a bunch of user migrations taking place over the next two months. Definitely agree on only linking the last task in each chain - the question was intended to be whether there was a quicker way of doing that than working out by eye which those tasks are. For example, if you type in all of the successors of the start milestone, that list is almost the same list as the predecessorsįor the finish milestone, so you just type it and then copy and paste the part of the string that you need for the predecessors of the finish milestone.ĭale: that ctrl tip is a new one thanks. OK, to make it happen means typing in those long strings of ID numbers, but there are ways to make it faster and less tedious. The FS0 predecessor for the finish milestone is each of, and all of, the tasks in the section, including the start milestone. In the section, including the finish milestone. The FS0 successor for each start milestone is each of the tasks Each task is like a project within a section.As a matter of good housekeeping and WBS organisation, and because it alsoīecomes very useful later on, I like to have overall start and finish milestones for the project, as well as intermediate start and finish milestones at top and bottom of each nested section. Each section is like a project within the project.
Nested within those, and so on and so on, down to whatever outline levels you arrive at.
The overall project has sections nested within it and there are sub-sections Let's call the summary and whatever is under it a section. You will not find this in any text books or youtube videos. I will contradict Dale's advice and make a different recommendation.
0 kommentar(er)
