This document discusses the concept of "Scrum Shu Ha Ri" which refers to the three stages of learning an agile framework like Scrum: follow (Shu), detach/break limits (Ha), and create/innovate (Ri). It encourages moving from strictly following Scrum processes to adapting and strengthening Scrum with techniques like acceptance test-driven development, visual management, and integrating ideas from Kanban and lean startup. The ultimate goal is to understand Scrum's teachings and invent your own unique approach to agility.

1. Scrum Shu Ha Ri
Christophe Addinquy

2. Thank to our sponsors

3. Thanks to
our support sponsors & partners
Partner Partner Partner
Support Sponsor Support Sponsor Media Partners

4. Who Am I ?
✤ Playing with computers for a long time !
✤ Formerly : developer, consultant, trainer, project manager,
business analyst, project director
✤ Agile addict since 2001
✤ Now agile coach @ Zenika
✤ Founding member of the French SUG until 2013

5. Agile, what it’s all about ?
Be agile ≠ Doing agile
Being agile = Becoming agile
Agility is a journey

6. Agility : a breakthrough
✤ Do = process
✤ Be = culture, mind set
Cynefin model
This is a radical change ! It
takes more than one step
to embrace it
3 steps

7. Shu Ha Ri
✤ Shu : Follow the example (learn)
✤ Ha : detach (break the limits)
✤ Ri : Be fluent (create, innovate)
✤ Refer to the Aïkido learning stages
✤ Introduced in the agile community by Alistair Cockburn

8. Scrum and the agile journey
✤ Not a process, but a «framework»
✤ Our companion during our journey : the
Scrum unknown vertu !
✤ Discover the true nature of Scrum !

9. Scrum Shu

10. Scrum : Follow the guide !
✤ A simple framework
✤ 3 roles
✤ 2 mandatory artifacts
✤ 4 meetings
✤ 2 cycles

11. Scrum « by the book »

12. Scrum : the roles
The Scrum Master
✤Take care of the right
Scrum implementation
✤Protect the team
✤Act as a facilitator
The Product Owner
✤Is the master of the
backlog
✤Take the decisions
about the product
✤Validate the
implemented features
The Team
✤Is responsible for the
outcome
✤Self organize to make the
Sprint items « done »
✤Own all the skills
required to achieve its
mission

13. The Sprint recipes
✤ A Planning Meeting at the beginning to organize, set
the objectives and the Sprint content
✤ A Scrum Meeting each morning to synchronize
everybody and adapt the plan
✤ A Sprint Review at the end of the Sprint to
demonstrate the work done
✤ A retrospective to learn and adapt about
the process based on what happened

14. What could go wrong...

15. The «mini V»
✤ « A Sprint, is like waterfall, but reduced to 2 or 3 weeks. »

16. Only the tests remain to be
performed...
✤ « A sprint outcome must be shippable in production »

17. Scrum, but...
✤ « We have adapted
Scrum to our specific
needs »

18. The rush mode
✤ The team must keep a sustainable pace from the beginning to
the end of the Sprint. And keep this pace from Sprint to Sprint.

19. Way too long stories !
✤ Cut in thin slices ... but keep a business meaning !
✤ A story isn’t a requirements document

20. Scrum Ha

21. The basic package

22. Scrum « and »
Reinforce inside
Reinforce from the
outside

23. Reinforce Scrum inside

24. Acceptance Tests driven
development
Specifications
Acceptance tests
✤ Write acceptance tests BEFORE the
development !
✤ The test cases (examples) are part and strengthen
the specification
✤ Write collaboratively to share understanding

25. Cognitive Bias
Creativity
workshop
23
Causal analysis
Service-Oriented
requirements
neuro-linguistique
programmation
Design Thinking
Story maps
Analyse système
Structured Analysis
CRC Card
Kano Model BPM
PLeffingwell Pyramid
Brainstorming
Personas
Mind maps
Contextual
analysis
Use Cases
Story boards
Archeology
documentation
Gap analysis
Non-fonctionnal
requirements
Constrains
Questioning
Attributes List
Mesures
Vision
Risks Analysis
Liespotting
Glossary
Prototyping
Stakeholders
assessment
Elevator statement
Product features
Decision tree
Traçability
Model
Business case
Usability engineering
Quantitative Analysis
Goal modeling
Integrated requirements
engineering
Agent-oriented
requirements
Use Cases maps
UML
Collaborative reqt. gathering
Screenwriting
Card sort
Formal Specifications
Cognitive Analysis
EARS
Social modeling
Event-oriented reqt.
Contextual inquiry
Reqt. driven design
Problem frames
Domain Driven Design
HCI analysis
Stakeholders taxonomy

26. The power of games !
Games to do
the job
Games to
learn

27. Visual Management
See everything that
matters
A forum to interact
in front of facts
Where the work
happens

28. Reinforce Scrum from the outside

29. From Scrum to Kanban
✤ Work on the product following a flow
✤ Keep the iterations cadence for the team
✤ Focus on the value and delay rather than estimates

30. An agile definition of the product
✤ Take into account all the
dimensions
✤ The Product Owner is not
superman
Start from the goal (the « why »)
Subordinate the perimeter to this « why »

31. Lean Startup
✤ Agility extended
to the business
model

32. From the development to the
production with devops
✤ 2 very different visions of the world
✤ Complementary but hard to put together
✤ A question of tools...
✤ But first a question of people
and collaboration

33. Scrum Ri

34. Invent your own agility
✤ Understand what Scrum can teach us
✤ The rules are no longer required
✤ Create your own way to be agile

35. My own agile indicators
Feedback Focus
Pleasure

36. Scrum outside development
Extreme Manufacturing : A customized car for each client in 7 days !

37. Agile Transformation with Scrum
© Laurent Sarrazin /
Rupture 21

38. Thank you !
✤ @addinquy
✤ http://freethinker.addinq.uy
✤ christophe.addinquy@zenika.com
✤ addinquy
✤ addinquy
✤ addinquy
✤ addinquy
✤ addinquy