Joe’s Release PlanningNashville, Feb 5, 2013

Problem: Scrum or not?

Agile release planning is not part of the simple framework of Scrum

Upfront some is ok?

We always know something

We never know everything

Decent plan vs Speed (delay, cost)

Revise every Sprint

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

Who

Product Owner

Implementers

ScrumMaster

Business stakeholders

Steps - 1Vision

Product Backlog

Business value

Priority Poker - BVP

Effort

Planning Poker - SP

Steps - 1

Effort

Risks, depend., learning, MMFS, other

ORDER THE WORK

Steps - 2ORDER THE WORK

Draw the line (Scope-Date trade-off)

Calculate velocity

Figure the cost

‘Communications plan’

Fix-it plan

Why?

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

Rel. Plan Refactoring

Every Sprint

“Everything changes, nothing remains the same.”

Re-do everything that needs re-doing

Includes product backlog grooming...

More informationPlease 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