Appearance
2.1c Project and Program Alignment
Individual projects can fail in isolation if their interdependencies aren't managed. Programs provide the connective tissue that ensures 1 + 1 = 3.
🔗 The Synergy Engine
Why group projects into a Program?
Silo Breaking
Prevents duplication of effort. (e.g., Two projects building the same login screen).
Dependency Management
Ensures Project B doesn't start until Project A finishes the prerequisite API.
Resource Optimization
Using one Data Architect across four projects instead of hiring four part-timers.
Benefits Realization
Delivering a "Platform" (Program Benefit) rather than just a collection of apps.
🚦 Managing Dependencies
A dependency is where one project holds the key to another's success.
- Finish-to-Start: The Platform Foundation (Project A) must be complete before the App (Project B) can launch.
- Resource Lock: Both projects need the Lead Security Engineer in Week 40.
- External: Project C is waiting for a government permit.
💡 Integrated Roadmaps
Program Managers use Integrated Master Schedules to visualize these dependencies. If Project A slips by 2 weeks, the software automatically highlights the crash in Project B.
🔄 Delivery Contexts
How alignment works in different methodologies:
| Method | Alignment Mechanism |
|---|---|
| Agile (Scaled) | PI Planning (Program Increment): All teams meet every 10 weeks to map dependencies on a physical board (String board). |
| Predictive | Master Schedule: A rigid Gantt chart linking critical paths across projects. |
| Hybrid | Guardrails: Fixed milestones (Launch Date) with flexible execution (Sprints) inside. |
📝 Exam Insight: If you discover a dependency on another project that you do not control: 1. **Contact Peer PM**: Try to resolve it directly. 2. **Escalate to Program Manager**: If you cannot resolve it peer-to-peer.