Scrum Master Lessons from My 4 Year Old Son

Transcription

1 Scrum Master Lessons from My 4 Year Old Son

2 @ryanripley

3 #Path15

4

5

6 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

7 What is Scrum?

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

9 What is a Scrum Master?

10 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

11

12

13 The Scrum Values: Commitment Respect Focus Openness Courage LINK:

14 What is an impediment?

15 Anything that prevents the scrum team from being productive.

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

17 A dead scrum master is a useless scrum master. --Ken Schwaber

18 1 It s Important to Try New Things

19

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

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

22 Experimentation is at the heart of Agile

23 Is it safe to fail?

24 Are experiments safe?

25 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.

26 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!

27 O RLY???

28 2 Embrace Learning Opportunities (Failure)

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

30 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

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

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

33 Is it safe to fail?

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

35 3 Why? Why? Why? Why? Why? Why?

36

37 What is the 5 Why s technique?

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

39 People do not fail, systems do

40 4 Learn Gradually

41

42 I don t think that design will work. You should code the story like this

43 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?

44 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

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

46 5 Words Matter

47

48 Your words are winning hearts and changing minds.

49 Be consistent.

50 Following through isn t optional.

51 Following through isn t optional.

52 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.

53 What about the word Agile?

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

55 6 Sustainable Pace Is Important

56

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

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

59 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

60 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

61 Sustainable pace is humane

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

63 Watch value, not the clock

64 7 Play Well With Others

65

66 How inclusive is your team?

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

68

69 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?

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

71 BEWARE LEARNED HELPLESSNESS Helplessness can lead to overlooking opportunities to improve

72 8 Time Box Events

73

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

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

76 Prevents over-investment in activities

77 Promotes a focus on value

78 Minimizes cost and impact of errors

79 9 Be Kind

80

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

82 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?

83 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

84 10 It s hurts to grow literally

85

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

87 The PMP to CSM pipeline 500 YARDS OF FOUL-SMELLING MUCK --Red The Shawshank Redemption

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

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

90 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

91 Learn to be introspective

92 Podcast available on itunes, Stitcher, and AgileAnswerMan.Com

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