PI Planning is the heartbeat of an Agile Enterprise. Scaled Agile provide strong materials, and support competency. But it won't stick as a practice without linking them to Meaning. See 3 critical reframes to add
6. Reframe 2:
Mission Planning
Auftragstaktik
An order should contain all, but also only, what
subordinates cannot determine for themselves.
Do not command more than necessary, or plan
beyond the circumstances you foresee.
Field Marshall Helmuth von Moltke (The Elder)
Read Me
Too many orgs focus on the plans and activities to create them in the rush to produce something reviewable in the tight time box. Objectives review is too often overlooked
Objectives are the key output of PI Planning.
They are what we expect to achieve
Deliverables are transitory; impacts are critical
And impacts connect an ART to PURPOSE – just as you’d expect from your Dan Pink
Nelson Trafalgar story.
Leaders:
Brief Mission: What & Why
Provide Context & Constraints
Give Freedom
Doers:
Define How
Adjust in Execution
Result: less delays, more innovation, better motivation
You also tend to get Product Management spending last weeks of the PI too busy panicking about Feature Readiness to pay attention to the demo and think through what it has learned.
So what does ‘better’ look like?