This document discusses value-driven planning for agile software methodologies. It outlines 10 steps for implementing value-driven planning: 1) Choose a methodology; 2) Determine epics; 3) Analyze and score epics; 4) Determine if a business value model is needed; 5) Plan releases; 6) Prioritize stories; 7) Map business velocity; 8) Stop on time; 9) Experiment with value; 10) Learn from experience. Various techniques are mentioned for each step, such as epic valuation, business value modeling, requirements prioritization models, tracking business velocity, and using the business model canvas. The overall goal is to ensure software delivers value to customers.

1. 03-23-05Agile software methodologies February 2014
page 1
VALUE DRIVEN PLANNING

2. Feb. 2014Agile Software Methodologies – Value Driven Planning
Katalict Kick-off Quotes
“Software zal worden voorzien met die
functionaliteit die de klant nodig heeft. Er moet
een added value zijn voor iedere gebruiker”
(Pieter Casneuf, CEO Adam Software)
“Je moet de markt constant in het oog houden.”
(Inge Geerdens, CEO CVWarehouse)
Oktober 2013
page 2

3. Feb. 2014Agile Software Methodologies – Value Driven Planning
1. Kies een methode
• Assessing Value
• Epic Valuation (SAFE)
• Business Value Modeling
• Planning Value
• Prioritisation
• Value & Agile Contracting
• Delivering Value
• Business Velocity
• Tracking & Reporting Value
• Agile Earned Value
• Confirming Value
• Disruptive innovation
page 3
© Plethon Consulting 2014

4. Feb. 2014Agile Software Methodologies – Value Driven Planning
2. Bepaal de epics
page 4
© Dean Leffingwell 2014
Assessing

5. Feb. 2014Agile Software Methodologies – Value Driven Planning
3. Analyseer & score epics
Epic Value
Statement
Effort ?
Econ. Impact ?
WSJF Prior.
Light BusCase
Split the epic
Integrate in Release Train
User/Business Value + Time + RR&OE Value
WSJF = ------------------------------------------------------------
. Job Size (length)
page 5
© Dean Leffingwell 2014
Assessing

6. Feb. 2014Agile Software Methodologies – Value Driven Planning page 6
4. Biz Value Model nodig ?
© Gartner 2014
Assessing

7. Feb. 2014Agile Software Methodologies – Value Driven Planning page 7
5. Plan de Releases
© Mike Griffiths 2014
Planning

8. Feb. 2014Agile Software Methodologies – Value Driven Planning page 8
• Simple
• MoSCow
• Monopoly Money
• Kano Analysis
• 100-Point method
• Requirements prioritisation model
Planning
6. Prioritiseer de stories

9. Feb. 2014Agile Software Methodologies – Value Driven Planning page 9
7. Map de Business Velocity
Business Velocity: How much business value
(in points) is delivered in each Sprint.
Delivering
© Pascal Van Cauwenberghe 2014

10. Feb. 2014Agile Software Methodologies – Value Driven Planning page 11
8. Stop op tijd
Business Value
Achieved*
Missing profit
* Make sure to follow up closely on this indicator internally
© Peter Stevens 2014
Planning

11. Feb. 2014Agile Software Methodologies – Value Driven Planning page 12
© Eric Ries 2014
Confirming
Disruptive Innovation
9. Experimenteer met Value

12. Feb. 2014Agile Software Methodologies – Value Driven Planning
BMC & Value Proposition
page 13
© Alexander Osterwalder 2014
Confirming

13. Feb. 2014Agile Software Methodologies – Value Driven Planning
Benefits management
Business
Value
Model
Epic
Valuation
Business
Velocity
Value
Proposition
Testing
Business Model
Canvas
Agile
Earned
Value
Agile
Contracting
Story
Prioritisation
Experimenting
Planning
Delivering & Tracking
The
Program Risk
environment
Value
Mgmt
Office
Assessing
10. Leer uit de ervaring
page 14
© Plethon Consulting 2014

14. Feb. 2014Agile Software Methodologies – Value Driven Planning
Thanks !
Contact info:
carl.danneels@plethon.be
http://www.plethon.eu
page 15