Some slides I used to discuss my typical approach to Release Planning in a Scrum context. Discussion at the Nashville PMI Agile COP Meeting, Feb 2013

1. Joe’s Release Planning
Nashville, Feb 5, 2013

2. Problem: Scrum or not?
Agile release planning is not part of the
simple framework of Scrum

3. Upfront some is ok?
We always know something
We never know everything
Decent plan vs Speed (delay, cost)
Revise every Sprint

4. Why?
To plan (when? how much $?)
To identify what we know
To share
To learn (knowledge creation)
To motivate
To get everyone on the same page

5. Who
Product Owner
Implementers
ScrumMaster
Business stakeholders

6. Steps - 1
Vision
Product Backlog
Business value
Priority Poker - BVP
Effort
Planning Poker - SP

7. Steps - 1
Effort
Risks, depend., learning, MMFS, other
ORDER THE WORK

8. Steps - 2
ORDER THE WORK
Draw the line (Scope-Date trade-off)
Calculate velocity
Figure the cost
‘Communications plan’
Fix-it plan

9. Why?
So, if we did it that way...
...what would be the biggest outcome?

10. Rel. Plan Refactoring
Every Sprint
“Everything changes, nothing remains
the same.”
Re-do everything that needs re-doing
Includes product backlog grooming...

11. More information
Please contact me here:
Joseph Little
jhlittle@kittyhawkconsulting.com
LeanAgileTraining.com
LeanAgileTraining.com/blog
h"p://agileconsor0um.pbworks.com/w/page/57940361/Joe%27s
%20Release%20Planning