Summary
In this chapter, we learned that scope is the set of requirements, and the impact is the group of people affected by the scope. We learned how to drive clarity at the program level by discerning the scope and impact of the requirements.
We then discussed how to use the scope and impact to define boundaries around the requirements. The boundaries can make up both the boundaries of a project and the deliverables within that project. This brings shape to the program.
After that, we learned that a program should be created when sufficient impact and scope dictate that multiple projects are needed to complete the goals. We also discussed how seeing patterns and goals across existing projects may align and warrant the creation of a program to track them as a whole.
Lastly, we discussed various aspects of tracking a program through program planning, risk management, and stakeholder management. Each of these key management areas builds on the management styles used at the...
