Search...
Practice what you just read
10 free practice questions. No credit card.
| Aspect | Description |
|---|---|
| Definition | A long-lived team of Agile teams that develops and delivers solutions |
| Size | Typically 50-125 people (5-12 Agile teams) |
| Purpose | Deliver a continuous flow of value to customers |
| Alignment | Common vision, program backlog, and roadmap |
| Cadence | Operates on fixed PI cadence (8-12 weeks) |
Practice what you just read
10 free practice questions. No credit card.
| Role | Responsibility |
|---|---|
| Release Train Engineer (RTE) | Servant leader who facilitates ART events and processes |
| Product Management | Owns the Program Backlog and drives PI content |
| System Architect | Defines overall technical and architectural vision |
| Business Owners | Key stakeholders who evaluate PI Objectives and accept value |
| Event | Frequency | Purpose |
|---|---|---|
| PI Planning | Start of each PI | Align all teams on PI Objectives and plan iterations |
| Scrum of Scrums | 2-3 times/week | Coordinate across teams, surface dependencies and impediments |
| PO Sync | Weekly | Sync Product Owners on backlog, priorities, and scope |
| ART Sync | Weekly | Review progress toward PI Objectives, address blockers |
| System Demo | End of each iteration | Demonstrate integrated increment to stakeholders |
| Inspect & Adapt | End of each PI | Reflect on PI, identify improvements, solve problems |