joe's release planning nashville feb 2013
DESCRIPTION
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 2013TRANSCRIPT
![Page 1: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/1.jpg)
Joe’s Release PlanningNashville, Feb 5, 2013
![Page 2: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/2.jpg)
Problem: Scrum or not?
Agile release planning is not part of the simple framework of Scrum
![Page 3: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/3.jpg)
Upfront some is ok?
We always know something
We never know everything
Decent plan vs Speed (delay, cost)
Revise every Sprint
![Page 4: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/4.jpg)
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
![Page 5: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/5.jpg)
Who
Product Owner
Implementers
ScrumMaster
Business stakeholders
![Page 6: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/6.jpg)
Steps - 1Vision
Product Backlog
Business value
Priority Poker - BVP
Effort
Planning Poker - SP
![Page 7: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/7.jpg)
Steps - 1
Effort
Risks, depend., learning, MMFS, other
ORDER THE WORK
![Page 8: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/8.jpg)
Steps - 2ORDER THE WORK
Draw the line (Scope-Date trade-off)
Calculate velocity
Figure the cost
‘Communications plan’
Fix-it plan
![Page 9: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/9.jpg)
Why?
So, if we did it that way......what would be the biggest outcome?
![Page 10: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/10.jpg)
Rel. Plan Refactoring
Every Sprint
“Everything changes, nothing remains the same.”
Re-do everything that needs re-doing
Includes product backlog grooming...
![Page 11: Joe's release planning Nashville Feb 2013](https://reader034.vdocuments.us/reader034/viewer/2022052522/554c4417b4c90530668b5144/html5/thumbnails/11.jpg)
More informationPlease contact me here:
Joseph Little
LeanAgileTraining.com
LeanAgileTraining.com/blog
h"p://agileconsor0um.pbworks.com/w/page/57940361/Joe%27s%20Release%20Planning