Downloaded 42 times
Uploaded byRyan Ripley
Help the Scrum Master IS the Impediment
The document discusses the role of the Scrum Master and the potential for them to become impediments to their team's productivity. It emphasizes the importance of self-reflection, adapting behaviors, and fostering open communication within teams to avoid becoming obstructive. Key Scrum values such as commitment, respect, focus, openness, and courage are highlighted as essential for successful Agile projects.
Help the Scrum Master IS the Impediment
- 1. HELP!!! THE SCRUM MASTERIS THE IMPEDIMENT!
- 2.
- 3.
- 4. What is ascrum master?
- 6. “The Scrum Masteris responsible for ensuring Scrum is understood and enacted.” --The Scrum Guide
- 7. What is animpediment?
- 8. “Anything that preventsthe scrum team from being productive.”
- 9. Every scrum mastercan avoid becoming an impediment to their team by frequently inspecting and adapting their behaviors.
- 10. “A dead scrummaster is a useless scrum master.” --Ken Schwaber
- 11. “Regardless of whatwe discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.” --Norm Kerth, Project Retrospectives: A Handbook for Team Reviews
- 13.
- 14. “I don’t careif you want to use software to track user stories, we’re going to start with 3x5 cards and masking tape!”
- 15.
- 16. INSPECT: •Arguments – “Whathas to be true…?” •Emotional outbursts •Am I talking to the team or at the team? •Your feelings – “Am I enjoying my role?”
- 17. ADAPT: •Take time toreflect on difficult exchanges •What is motivating you? •Anxiety, fear, or frustration •Address the “friction” in the retrospective •Ask the team for feedback and support
- 18.
- 19. “A project managercould maybe become a tester...maybe.” --Ken Schwaber
- 20. “Alright, this storyis pretty simple… Bob can knock it out in a few days... This next one…”
- 21. “500 YARDS OFFOUL-SMELLING MUCK” --Red “The Shawshank Redemption” The PMP® to CSM® pipeline…
- 22. INSPECT: •How the teammanages their work •Focus of Daily Scrum meeting •Unsolicited advice •Interrupting progress to pontificate
- 23. ADAPT: •Questions over statements(2:1 ratio) •Make failure an option – and then fail •The team owns tasks and solutions •Ask for permission to help
- 24. “DAD! Stop helpingme!” --My son, tired of me inflicting help
- 25.
- 27. “I don’t thinkthat design will work. You should code the story like this…”
- 28. INSPECT: •Is design/architecture emergent? •Arethe developers disengaged? •How does the team decide the best way to do their work? •Is pair programming, #mobprogramming, or swarming happening?
- 29. ADAPT: •Leave the developersalone •Step down as scrum master and resume a coding role •Focus on guiding rather than directing •Ask for permission to help
- 30.
- 31. “That’s not howit’s done! Here, let me show you the “right way” to be agile…at 2am.”
- 33. INSPECT: •Team seeks yourapproval before acting •Team asks about the “right way” to do Agile •Are you insisting on “correct” solutions?
- 34. ADAPT: •Resist the urgeto solve the teams problems •Get comfortable with awkward silence •Focus on relationships
- 35. Learn to beintrospective
- 36. The Scrum Values: •Commitment •Respect •Focus •Openness •Courage LINK:http://agileanswerman.com/scrum-values-can- make-or-break-your-agile-project/
- 37. Take time toreflect on your day
- 39. Own your mistakes,apologize, learn, and grow.
- 40.