How would you estimate a cross-cutting initiative in PI Planning?
Tests decomposition of cross-cutting work into team enablers with visible dependencies. Good answer: teams estimate own slices in normalized points, map dependencies on the ART board, and reserve IP buffer.
Tests whether you can break cross-cutting technical work into inspectable, team-owned deliverables during PI Planning while keeping decentralized decisions and dependency transparency. Good answer: define enabler features with clear interfaces; let each team estimate its own slice in normalized points; map dependencies on the ART board; negotiate scope to fit capacity; and preserve IP iteration buffer for integration. Red flag: one architect imposes a monolithic top-down estimate that teams accept without questioning assumptions.
Read the original → framework.scaledagile.com
- #safe
- #pi-planning
- #estimation
- #cross-team
- #scaled-agile
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.