
Key Artifacts: Program/ART Level
Coordinating work across multiple teams
Features
- Larger functional capabilities delivered within a Program Increment (PI)
- Managed in the ART's Program Backlog
- Delivers value to end-users
- In hospitals: "Electronic medication reconciliation across all care transitions"
Program Backlog
- Prioritized list of Features maintained by Product Management
- Source of work for all teams in the ART
- Contains both business and enabler features
- Typically holds 2-3 PIs worth of upcoming features
PI Objectives
- Summary of business goals the ART commits to deliver in the PI
- Created during PI Planning
- Categorized as Committed or Stretch objectives
- In hospitals: "Deploy patient portal with SSO integration to three clinical systems"
Program Board
- Visual management tool showing feature assignments and dependencies
- Created collaboratively during PI Planning
- Highlights cross-team dependencies
- Used throughout the PI to track progress
Program Increment (PI)
- Timeboxed interval (typically 8-12 weeks)
- Contains 4-5 iterations plus Innovation & Planning iteration
- Primary planning, execution, and learning cycle for the ART
- Culminates in a System Demo of integrated functionality
System Demo
- Integrated demonstration of the entire solution
- Occurs at the end of each PI
- Includes all teams' work integrated into a cohesive system
- Key stakeholders (including clinical representatives) attend
- Provides objective evidence of progress