|
Critical Path 2.0
|
Eric Uyttewaal , ProjectPro Corp
|
|
Product Session
|
|
PC333
|
|
MVP
|
|
300
|
|
Consultants ,Executives ,Portfolio Program and Project Managers
|
|
Project
|
|
Scheduling
|
|
Critical Path, version 1.0, was invented in the late 1950’s. It is a beautiful product of the human brain; it focuses project managers on activities that impact the project duration. However, some people say they hardly ever see a complete Critical Path in their schedule; there are often gaps in the Critical Path. Others say that the Critical Path does not work after you have leveled the workloads; as soon as you start delaying tasks to address over-allocations, the Critical Path becomes fragmented. These are real issues that an international working group led by Eric Uyttewaal has addressed. Eric will share the findings of this working group in his presentation and present to you the second version of the Critical Path theory: Critical Path 2.0. The document produced by the working group is meant to become a standard for scheduling software that vendors can aspire to.
After 60 years, it is time for Critical Path 2.0!
|
• Understand why the Critical Path 1.0 appears fragmented:
- When you use calendars, constraint dates, elapsed durations or lags, etc.
- When MS Project levels the workloads (resource-constrained project)
• Become aware of the new Critical Path 2.0 Method and Standard for scheduling software
• Know which scheduling software is Critical Path 2.0 compliant and which is not
• Understand how to find the new Critical Path 2.0 in your Microsoft Project schedule
• Become aware of automated tools that can display the Critical Path 2.0 in Microsoft Project
|
1. How advanced scheduling features in Microsoft Project break a Critical Path 1.0
2. The new Critical Path 2.0 Method and Standard
3. Some tools that make Microsoft Project Critical Path 2.0 compliant
|
|
|