Exploring the key management areas
In Chapter 1, I introduced the key management areas: plan, risk, and stakeholder management. Using the Mercury program as an example, we’ll examine each of the key management areas and continue to build on top of our use case study.
Program and project plans
Let’s examine the Windows rollout project plan with a few assumptions so as not to overcomplicate the plan at this point in the book:
- We have as much resourcing as we need (so, every task that does not have a predecessor constraint at the beginning of the project will be scheduled to start).
- No resource timing constraints exist.
- Estimates are uniform across all platforms.
- All predecessors are considered finish-to-start (meaning the predecessor must be finished before the task can start).
- There are no cross-project dependencies.
- In other words, a textbook program example!
Given these assumptions, Table 4.2 lists a simplified...
