Most Agile practitioners know why we do retrospectives. But do they know why we use post-it’s? A lot of people don’t. This is one example of a hidden layer: the deeper meaning of the Agile techniques. Whenever you consider using or dropping an Agile technique, you have to be sure to know all the consequences, including these hidden layers. For each of the next 7 hidden layers, we'll talk about techniques to find the hidden layer. Even more importantly, I'll explain some Agile games you can use to feel those hidden layers. - Safety for introverts - everybody involved - Team objective & peer pressure - Comfort zone - Communication methods - The physical connection - Self organising (instead of micro management) - Flow

1. 7 hidden layers

2. Why post-its?

3. What if you remove the post-it’s
during a retrospective?

5. Why planning
poker?

6. What if you just shout your estimation?

8. Hidden layer 1
Psychological safety

9. Psychological safety
• Hidden layer
• All participants get the same space: introverts and extraverts
• Everybody is involved (especially important in Scrum)
• How to show to your team?
• Do it
• Explain it thoroughly

10. Importance of hidden layers
• Choose wisely: know the hidden layer
• Focus on ‘why’-> people will be able to choose
themselves
• Don’t choose the techniques, but the reasons
behind the techniques
• Show them by using agile games

11. Want some more hidden layers?

12. Why
commitment?

13. Why a demo?

14. Hidden layer 2
Team objectives &
peer pressure

15. Team objectives & peer pressure…
• Hidden layer
• Peer pressure leads to helping colleagues (for example stand-ups)
• Team objectives works better then personal objectives
• How to show to your team?
• Agile game: step factory

17. Still want some more hidden layers?

18. Why do we need
a scrummaster?

19. Hidden layer 3
Comfort zone

20. Fear
Learning
Comfort

21. Comfort zone
• Hidden layer
• Get people out of the comfort zone -> continuous improvement
• How to show to your team?
• Agile game: the ball game

23. Another one?

24. Why move post-
it’s on physical
whiteboard?

25. Hidden layer 4
The physical connection

26. The physical connection
• Hidden layer
• Connection between physical act: making abstract things tangible
• Yes, also an information radiator
• How to show to your team?
• Do it
• Explain it
• I haven’t found a good game about this

27. Almost there…

28. Why pair
programming?

29. Why sit together?

30. Why face-to-face
communication?

31. Hidden layer 5
Communication methods

32. Communication methods
• Hidden layer
• Use shortest communication channel
• Avoiding projection (or silo-thinking)
• How to show to your team?
• Agile game: folding origami

34. The last but one?

35. Why micro
management by
the team?

36. Hidden layer 6
Self-organising vs
micro-management

37. Self-organising vs micro-management
• Hidden layer
• ‘How’ best decided by people who do the work
• Self organising is also: the best solution (see the game)
• CAS
• How to show to your team?
• Agile game: step factory

38. The last hidden layer?

39. Why small
increments of
work?

40. Why WIP
limits?

41. Hidden layer 7
Flow

42. Flow
• Hidden layer
• Satisfaction of delivery (not only flow)
• Decrease the risk (but raise the cost?)
• How to show to your team?
• Agile game: the dot-game

44. Thanks
Come and see me afterwards!

45. All hidden layers
1. Psychological safety
2. Team objective and peer pressure
3. Comfort zone
4. The physical connection
5. Communication methods
6. Self organising vs micro management
7. Flow

46. Possible questions
• Do you know any other hidden layers in Agile techniques and
practices, beyond the just presented?
• See any games to let your team feel these layers?