Presentation about differences and flow of using DoR and Refinement Process to improve development process of team's work. Sorry for 4:3/needed by organizer.

1. Definition
of Ready
vs.
Refinement
Buzzwords or bigwords?

2. When you think,
PBI is ready

4. Troy Magennis:
’When we asked someone to estimate how long it will
take to develop a feature or project they think about how
long it would take hands-on, with PERFECT hand-off
between teams and other staff with the specialist skillset.
This never happens.’
One step back…

5. What does it
mean that PBI is
ready?

6. PBI is ready
when there is
nothing to add to
requirements.

7. Ziv’s law:
’Requirements
never be
completely
understood.’

9. Rule #1:
Don’t forget to
ask another
question

10. Rule #2:
If you have asked
all questions, ask
another

11. Rule 3#:
Put the PBI into
app flow, to
check if you
understand

12. Rule #4:
Ask more
questions about
PBI in the flow

13. Rule #5:
Check on
mockups, if you
didn’t forget
about anything

14. Do you think,
you know
everything?

16. Ziv’s law:
’Requirements
never be
completely
understood.’

17. You have
the BASIS
to start working
on each PBI -
DoR

18. There is a
moment for next
step –
Refinement

19. Any clues?
INVEST

20. I – independant
N – negotiable
V – valuable
E – estimable
S – small
T – tastable

21. Refinement flow

22. Why do we create
PBIs according to
DoR?
Because of a sense of the value team needs.

23. When there is a sense of the value:
• Team is self-organizing rather than role- or title-based.
• Team is empowered to make decisions.
• Team truly believes that as a team they can solve any problem.
• Team is committed to team success vs. success at any cost.
• Team owns its decisions and commitments.
• Team is consensus-driven , with full divergence and then
convergence.
- Lyssa Adkins

24. https://www.linkedin.com/in/agatasobek/