This document discusses prioritization and the Kent Scrum UG. It values individuals and interactions, working software, customer collaboration, and responding to change over processes, documentation, negotiation, and plans. Scrum Education Units can be earned through Scrum Alliance events. Prioritization should be based on an economic framework considering the cost of delay, value, development expense, risk, and the interaction among variables. The cost of delay includes user/business value decay over time, revenue impact, potential penalties, customer satisfaction, risk reduction, opportunity enablement, and information value. An example is given to prioritize items in a SAFe city using cost of delay and job size estimates.

1. Welcome!
How do you prioritise?
Kent Scrum UG

2. 2
Our Vision
Individuals and interactions
Working software
Customer collaboration
Responding to change
While there is value in the items on the right, we value the
items on the left more.
Over
Over
Over
Over
We are uncovering better ways of developing software by
doing it and helping others do it.
Processes and tools
Comprehensive documentation
Contract negotiation
Following a plan

3. 3
Scrum Education Units (SEU)
Category A: Scrum Alliance Scrum Gatherings
Up to 45 SEUs can be earned at a rate of one credit
per hour of participation in:
• Scrum Alliance Global Gatherings
• Scrum Alliance Regional Gatherings
• Scrum Coaching Retreats
• Scrum Alliance-Sponsored Events
• Scrum Alliance-Endorsed User Group events and
activities.
2 SEUs

4. 4
Thank You

5. 5
Create some noise!
@KentScrumUG
@dazzawilmshurst

6. 6
How do you prioritise?
Does it sound a little like
this?

7. 7

8. 8
Priority Choice – Equal Duration

9. 9
Priority Choice – Equal Value

10. 10
Priority Choice – Mixed Duration, Mixed Value

11. Base Decisions on Economics
Develop an economic framework for decision making
 Empower local decision making
 Do not consider money
already spent
 Sequence jobs for
maximum benefit
 If you only quantify one thing,
quantify the cost of delay
Cycle time Cost
Value
Development
expense
Risk
—Don Reinertsen, Principles of Product Development Flow
“Understanding economics requires understanding of
the interaction amongst multiple variables.”

12. 12
Why Quantifying the Cost of Delay Matters

13. 13
Weighted Shortest Job First (WSJF)
• In order to calculate WSJF we need to estimate Cost
of Delay and Duration
• Relative estimating is a quick technique to estimate
job size and relative value
• For duration, we will use job size as a quick proxy
WSJF = =
User-Business Value + Time Criticality + RROE Value
Job Size
CoD
Job Size

14. 14
Components of Cost of Delay
Relative value to the customer or business
• They prefer this over that
• Revenue impact?
• Potential penalty or other negative impact?
How User Business Value decays over time
• Is there a fixed deadline?
• Will they wait for us or move to another solution?
• What is the current effect on customer satisfaction?
What else does this do for our business
• Reduce the risk of this or future delivery?
• Is there value in the information we will receive?
• Enable new business opportunities?
User and
Business Value
Time
Criticality
Risk Reduction &
Opportunity
Enablement
(RR & OE)

15. 15
Prioritise SAFe City,
based on cost of delay
and job size
Instructions:
 Prioritise your development items
using CD3
 Estimate each backlog item one
column (not row) at a time
 You don’t have to estimate job
size at this time
Source: Mark Richard - http://www.agilenotanarchy.com/2014/08/getting-from-theory-to-practice-with.html
Exercise

16. Questions?
How do we prioritise?
Kent Scrum UG