Why is number 10 so hard?
So many years into the agile journey - why is Agile Principle #10 -"Simplicity--the art of maximizing the amount of work not done" still so difficult to get right?
We've been bombarded with prioritization tools and techniques, sent millions of people on Product owner training yet are still more obsessed with velocity, throughput and output than customer value.
What if there were valid reasons why we avoid prioritization and prefer to deal with the consequences?
In this session we'll explore some of the assumptions we have regarding backlog refinement and prioritization, why it's so darn hard, and how we can create the right environment so that it's easier.
Because as Peter Drucker says:
"There is nothing so useless as doing efficiently that which should not be done at all."
Outline/structure of the Session
- Storytelling intro on impacts of lack of inittiative prioritization
- Overview of the myriad of prioritisation techniques - visual representation and videos
- Challenge the audience - How many of them are really focused on delivering the most important customer outcomes vs output. (Polling software if allowed)
- Overview of some of the cognitive biases and neurological causes for that. E.g
- Prioritisation is one of the hardest mentally draining things we ask our brains to do and requires the prefrontal cortex to consume lots of energy.
- So how do you charge your PFC? Your teams? Your Product Owners?
- What time of day is best to run refinement sessions?
- Summarise what they can do to create a better environment for value maximisation to happen.
How to create the right environment for prioritisation and value maximisation to happen
Product Owners, Scrum masters, Anyone who has ever struggled to prioritise and can't understand why.
Basic agile concepts and product ownership fundamentals.