Scrum Master Lessons from My 4 Year Old Son

If you like this presentation – show it...

Slide 0

Scrum Master Lessons from My 4 Year Old Son

Slide 1


Slide 2


Slide 3

Slide 4


Slide 5

“Regardless of what we 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

Slide 6

What is Scrum?

Slide 7

SCRUM IN ONE SLIDE Development Sprint Planning Sprint Review Sprint Retrospective Sprint ROLES: Scrum Master, Product Owner, Developer ARTIFACTS: Product Backlog, Sprint Backlog, Product Increment

Slide 8

What is a Scrum Master?

Slide 9

“The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.” --The Scrum Guide

Slide 10

Slide 11

Slide 12

The Scrum Values: Commitment Respect Focus Openness Courage LINK: http://agileanswerman.com/scrum-values-can-make-or-break-your-agile-project/

Slide 13

What is an impediment?

Slide 14

“Anything that prevents the scrum team from being productive.”

Slide 15

Every scrum master can be more successful at serving their team by understanding these 10 lessons.

Slide 16

“A dead scrum master is a useless scrum master.” --Ken Schwaber

Slide 17

It’s Important to Try New Things 1

Slide 18

Slide 19

“At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” --Agile Manifesto

Slide 20

“Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.” --The Scrum Guide

Slide 21

“Experimentation is at the heart of Agile”

Slide 22

Is it safe to fail?

Slide 23

Are experiments safe?

Slide 24

“Your teams velocity is worse than the other scrums teams. Find a way to get your velocity up, or we may have to reassign resources.”

Slide 25

“I don’t care if you want to use software to track user stories, we’re going to start with 3x5 cards and masking tape!”

Slide 26

O’RLY ???

Slide 27

Embrace Learning Opportunities (Failure) 2

Slide 28

“DAD! Stop helping me!” --My son, tired of me inflicting help

Slide 29

Happy Accidents Thomas Edison “failed” thousands of times until he found the correct filament for the light bulb. Post-It notes were invented to replace bookmarks. Kleenex tissues were originally made to remove make-up. WD40 is named after the number of attempts to get the water displacement formula correct. These ideas were at one point failures…

Slide 30

Not every experiment is a winner…and not every failure is a loser.

Slide 31

SCRUM IN ONE SLIDE Development Sprint Planning Sprint Review Sprint Retrospective Sprint ROLES: Scrum Master, Product Owner, Developer ARTIFACTS: Product Backlog, Sprint Backlog, Product Increment

Slide 32

Is it safe to fail?

Slide 33

“That developer is slacking. When is the scrum master going to take care of the poor performer?”

Slide 34

Why? Why? Why? Why? Why? Why? 3

Slide 35

Slide 36

What is the 5 Why’s technique?

Slide 37

Often we push past the surface issues and find more complex system and relationship issues at the 5th “why”

Slide 38

People do not fail, systems do

Slide 39

Learn Gradually 4

Slide 40

Slide 41

“I don’t think that design will work. You should code the story like this…”

Slide 42

THINGS TO LOOK FOR: Is design/architecture emergent? Are the developers disengaged? How does the team decide the best way to do their work? Is pair programming, #mobprogramming, or swarming happening?

Slide 43

ADJUSTMENTS: Leave the developers alone Step down as scrum master and resume a coding role Focus on guiding rather than directing Ask for permission to help

Slide 44

“What does it matter how many times I reassign team members, isn’t that what self-organization is for?”

Slide 45

Words Matter 5

Slide 46

Slide 47

Your words are winning hearts and changing minds.

Slide 48

Be consistent.

Slide 49

Following through isn’t optional.

Slide 50

Following through isn’t optional.

Slide 51

“Teams ship working software at the end of each sprint. That’s why we implemented scrum. Work the weekends if you’re behind. The team needs to deliver on their commitments.”

Slide 52

What about the word “Agile”?

Slide 53

Communication is your greatest tool. How you frame discussions WILL make or break your agile transformations and projects.

Slide 54

Sustainable Pace Is Important 6

Slide 55

Slide 56

“Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.” --Agile Manifesto

Slide 57

Sustainable pace is a quality play Burned out developers deliver bad code They also find better jobs

Slide 58

Sustainable pace is a productivity play Continuous integration, automated testing, skill building, and whole team understanding become important when long hours are not an option

Slide 59

Sustainable pace is predictable Over a period of time, the amount of work that a scrum team - working at a sustainable pace - can accomplish will become consistent

Slide 60

Sustainable pace is humane

Slide 61

“Your team leaves at 5:00pm and refuse to work weekends. Why don’t they have a sense of urgency?”

Slide 62

Watch value, not the clock…

Slide 63

Play Well With Others 7

Slide 64

Slide 65

“How inclusive is your team?”

Slide 66

“That’s not how it’s done! Here, let me show you the “right way” to be agile…at 2am.”

Slide 67

Slide 68

ARE YOU A HERO?: Team seeks your approval before acting Team asks about the “right way” to do Agile Are you insisting on “correct” solutions?

Slide 69

THINGS TO CONSIDER: Resist the urge to solve the teams problems Get comfortable with awkward silence Focus on relationships

Slide 70

BEWARE LEARNED HELPLESSNESS Helplessness can lead to overlooking opportunities to improve

Slide 71

Time Box Events 8

Slide 72

Slide 73

A time box is a fixed period of time to perform an action or to achieve a goal.

Slide 74

SCRUM IN ONE SLIDE Development Sprint Planning Sprint Review Sprint Retrospective Sprint ROLES: Scrum Master, Product Owner, Developer ARTIFACTS: Product Backlog, Sprint Backlog, Product Increment

Slide 75

Prevents over-investment in activities

Slide 76

Promotes a focus on value

Slide 77

Minimizes cost and impact of errors

Slide 78

Be Kind 9

Slide 79

Slide 80

?????? AGILE IMPACTS EVERYONE Organizational Change Leadership Change Team Change Status Change Job Description Change Role Change Culture Change

Slide 81

WARNING SIGNS: Arguments – “What has to be true…?” Emotional outbursts Am I talking to the team or at the team? Your feelings – “Am I enjoying my role?”

Slide 82

ARE YOU BEING KIND? Take time to reflect on difficult exchanges What is motivating you? Anxiety, fear, or frustration Address the “friction” in the retrospective Ask the team for feedback and support

Slide 83

It’s hurts to grow…literally 10

Slide 84

Slide 85

“A project manager could maybe become a tester...maybe.” --Ken Schwaber

Slide 86

“500 YARDS OF FOUL-SMELLING MUCK” --Red “The Shawshank Redemption” The PMP® to CSM® pipeline…

Slide 87

We are telling people to give up the tools, methods, processes, and behaviors that have made them successful.

Slide 88

INSPECT: How the team manages their work Focus of Daily Scrum meeting Unsolicited advice Interrupting progress to pontificate

Slide 89

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

Slide 90

Learn to be introspective

Slide 91

http://agileanswerman.com ryan@agileanswerman.com @ryanripley Podcast available on iTunes, Stitcher, and AgileAnswerMan.Com

Slide 92

IMAGE ATTRIBUTION “Broccoli” - ©Julia Frost – Flickr.com – Creative Commons License “Singleton Bank Rail Crash” – Public Domain “Soap” - ©Frankleleon – Flickr.com – Creative Commons License