A coordinated grouping of related projects. It provides a context for tracking work that serves a broader objective.
When to use it
Use it when several projects should be managed in a shared program.
Key information
- Completion percentage records reported progress; review it with the actual work and evidence.
- Due date records when the work is expected to be due.
- Scope describes the boundaries of the planned work.
Common relationships
- Program – Project (Structure): Places a Project within a Program’s structure.
- Product – Program (Non-structure): Connects a Product to a Program associated with it.
- Program – Workflow Template (Non-structure): Connects a Program to a Workflow Template associated with its planned process.
Working with this record
Define the broader objective and identify the projects contributing to it. Review scope, dates, and progress together while keeping each project’s responsibilities clear.
Example
Pump Modernization is a Program containing redesign and production-readiness projects.
Choosing the right type
Choose Program to coordinate related projects. Project manages an individual initiative, and Product identifies the offering being developed.
