What can possibly go wrong with scrum?

Slides for a talk I did for the NNUG Stavanger meetup.

Transcript

1. WHAT CAN POSSIBLY GO WRONG WITH SCRUM? Created by Aurelien Beraud
4. SO WHAT CAN GO WRONG? Purpose of Scrum Planning meeting Product Owner role Team Empowerment Tribal culture Retrospective Scrum Master role <Insert your own> And much more ...
5. PURPOSE OF SCRUM
6. Any process that people use is wasteful, and that includes Scrum. (Jeff Sutherland, co-creator of Scrum - 2014)
7. So, what is the purpose of Scrum then? To help us learn this:
8. While we learn we should: Follow the rules. Experiment and make mistakes. Not get discouraged when we fail.
9. And once we have learned "Agility", then we don't need Scrum anymore.
10. PLANNING MEETING
12. If we really wanted to plan and estimate every details, we would do it like that:
13. Human being are lousy at estimating, so stop doing it! Use an abstraction: Story Points Compare stories
14. Wall estimates
15. Did you know the planning meeting has two parts? First part - What? Second part - How? If you forget part 2, you then have a goal but you have no plan at all.
16. GROOMING MEETING Sounds funny right? Well that is what you do when you do a grooming meeting!
17. PRODUCT OWNER ROLE
19. However he often becomes a bottleneck ... so what to do? Share the vision not the solution. Open communication channels. Delegate to the team.
20. TEAM EMPOWERMENT
21. DAILY SCRUM
22. meeting! The Daily Scrum is a PLANNING
23. Only the team is supposed to attend that meeting. However they might need a facilitator help with the self- organization.
24. SCRUM BOARD Simple and efficient.
25. But what about ...
26. or ...
27. TRIBAL CULTURE
28. Scrum is asking you to be on stage 4.
29. So what technique could we use to have people working more closely together? PAIR PROGRAMMING
30. Some people go even further: Mob Programming
31. Level 4 tribe does not stop when you step outside of the office. So do thing as a team outside of work.
32. RETROSPECTIVE
33. Common problems: Not engaging Repetitive Broad non actionable goals No follow up on actions Disappear when firefighting
35. Structure your retrospective: Set the stage Gather data Generate Insights Decide what to do Close the retrospective And have a specialist to faciliate it.
36. Force yourself to keep doing it, especially when under pressure. The problem you are facing are probably caused by something you haven't identified yet. So take the time for self reflection.
37. SCRUM MASTER ROLE
38. Scrum ask for much complex things than what is described in the Scrum guide. It asks the whole organization to change it's culture and behavior. And that is one of the reason you have a dedicated role to help with the transition.
39. However: A two days course does not make a good Scrum Master.
40. All these problems I have listed are IMPEDIMENTS that the Scrum Master needs to solve. Do you really think someone can do that as a part time job?
41. Scrum is about change, however humans don't like change. So you will need the courage to challenge the status-quo and start doing things differently.
42. <INSERT YOUR OWN>