Microsoft® Project expert Sam Huffman gives us the do’s and don’ts of Project. Each of these 9 videos shows a different problem that Project users may face and demonstrates how to solve that problem. From organizing your outline to leveling resources, Sam Huffman shares his techniques for getting the job done right. Join MPUG to access full-length, live webinar training sessions and hundreds more on-demand.
Including summary tasks in project sequencing can cause a lot of problems if you are not familiar with Projects scheduling process. By the end of this video, you will know what to look for in order to avoid any problems and even find ways to reduce your project schedule.
Want more Do’s and Don’ts? Check out MPUG’s new book: Microsoft® Project Do’s and Don’ts!
Click the links below to see more videos in Sam Huffman‘s Microsoft® Project Do’s and Don’ts series:
Using Elapsed Durations for Team Schedules
Constraining Activities
Organizing Project Tasks Incorrectly
Inadequate Baselining
Scheduling Projects as Late as Possible
Leveling Resources Without Analysis
Incorrect Calendar Association
Assigning Resources to Summary Tasks
Karim Harb
Hi Sam.
I am wondering what is the best practice to link a task with a whole summary. I mean, the start of one task depends on the finish of all the tasks contained in a summary.
Let’s say we have Summary1 that contains Task1 and Task2; these are linked by a FS dependency. Then we have Summary2 with Task3 and Task4 linked the same way as the previous.
If Task3 depends on the finish of both Task1 and Task2, should I link Task 3 with those? Should I create a milestone named End of Summary1 that will finish once Task1 and Task2 have finished, and then link Task3 with this milestone?
Thanks in advance Sam.
Sam Huffman
Using the milestone would be best. I’m not saying that you must not use summaries in sequencing – it’s just not something I recommend due to potential scheduling issues such as the one I pointed out.