sdec15: help the scrum master *is* the impediment

108
Ryan Ripley Help!!! The ScrumMaster *IS* the Impediment Thank you to our Sponsors

Upload: ryan-ripley

Post on 14-Apr-2017

600 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: SDEC15:  Help the Scrum Master *IS* the Impediment

Ryan RipleyHelp!!! The ScrumMaster *IS* the Impediment

Thank you to our Sponsors

Page 2: SDEC15:  Help the Scrum Master *IS* the Impediment

@ryanripleyPMI-ACP, PSM I, PSM II, PSE, PSPO I, PSD I, CSM, and CSPO

Page 3: SDEC15:  Help the Scrum Master *IS* the Impediment

#SDEC15

Page 4: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 5: SDEC15:  Help the Scrum Master *IS* the Impediment

?

Page 6: SDEC15:  Help the Scrum Master *IS* the Impediment

“500 YARDS OF FOUL-SMELLING MUCK”--Red “The Shawshank Redemption”

The Project Manager to ScrumMaster ® pipeline…

Page 7: SDEC15:  Help the Scrum Master *IS* the Impediment

What is Agile?

Page 8: SDEC15:  Help the Scrum Master *IS* the Impediment

DILBERT © 2007 Scott Adams. Used By permission of UNIVERSAL UCLICK. All rights reserved.

Page 9: SDEC15:  Help the Scrum Master *IS* the Impediment

We are uncovering better ways of developingsoftware by doing it and helping others do it.

Through this work we have come to value:

Individuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

That is, while there is value in the items onthe right, we value the items on the left more.

Page 10: SDEC15:  Help the Scrum Master *IS* the Impediment

THE 12 AGILE PRINCIPLES

www.AgileManifesto.org

Our highest priority is to satisfy the customer

through early and continuous delivery of

valuable software.

Welcome changing requirements, even late in

development. Agile processes harness change

for the customer's competitive advantage.

Deliver working software frequently,

from a couple of weeks to a couple of months, with a preference to the

shorter timescale.

Business people and developers must work

together daily throughout the project.

Build projects around motivated individuals.

Give them the environment and support they need, and trust them to get the

job done.

The most efficient and effective method of

conveying information to and within a development

team is face-to-face conversation.

Working software is the primary measure of

progress.

Agile processes promote sustainable development. The sponsors, developers, and users should be able

to maintain a constant pace indefinitely.

Continuous attention to technical excellence

and good design enhances agility.

Simplicity--the art of maximizing the amount

of work not done--is essential.

The best architectures, requirements, and

designs emerge from self-organizing teams.

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts

its behavior accordingly.

Page 11: SDEC15:  Help the Scrum Master *IS* the Impediment

SCRUM IN ONE SLIDE

Development

Sprint Planning Sprint Review

Sprint Retrospective

Sprint

ROLES: Scrum Master, Product Owner, DeveloperARTIFACTS: Product Backlog, Sprint Backlog, Product Increment

Page 12: SDEC15:  Help the Scrum Master *IS* the Impediment

Where is the Project Manager?

Page 13: SDEC15:  Help the Scrum Master *IS* the Impediment

“A project manager could maybe become a tester...maybe.”

--Ken Schwaber

Page 14: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 15: SDEC15:  Help the Scrum Master *IS* the Impediment

What is a Scrum Master?

Page 16: SDEC15:  Help the Scrum Master *IS* the Impediment

“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

Page 17: SDEC15:  Help the Scrum Master *IS* the Impediment

PRODUCT OWNER

SCRUM MASTER

STAKEHOLDERSDEVELOPMENT TEAM

WHAT?WHY?

IMPEDIMENTSSYSTEM

IMPEDIMENTS

FEEDBACK

(HOW)

Page 18: SDEC15:  Help the Scrum Master *IS* the Impediment

LEADING CAUSES OF FAILED AGILE PROJECTSFrom the 9th Annual VersionOne State of Agile Report

©2015 VersionOne, Inc. - State of Agile is a trademark of VersionOne, Inc. and VersionOne is a registered trademark of VersionOne, Inc.

42%Company philosophy

or culture at odds with core agile values

37%External pressure to

follow traditional waterfall processes

38%Lack of management

support

30%Insufficient training

33%A broader organizational

or communications problem

33%Unwillingness of

team to follow agile

Page 19: SDEC15:  Help the Scrum Master *IS* the Impediment

Copyright © 2015 Scrum Alliance®

Page 20: SDEC15:  Help the Scrum Master *IS* the Impediment

BARRIERS TO FURTHER AGILE ADOPTIONFrom the 9th Annual VersionOne State of Agile Report

©2015 VersionOne, Inc. - State of Agile is a trademark of VersionOne, Inc. and VersionOne is a registered trademark of VersionOne, Inc.

22%Concerns about a

loss of management control

24%Management

concerns about lack of upfront planning

29%Management support

44%Ability to change

organizational culture

34%General organizational resistance to change

35%Not enough personnel with necessary agile

experience

Page 21: SDEC15:  Help the Scrum Master *IS* the Impediment

Copyright © 2015 Scrum Alliance®

Page 22: SDEC15:  Help the Scrum Master *IS* the Impediment

Scrum Masters have their hands full, but not with software development…

Page 23: SDEC15:  Help the Scrum Master *IS* the Impediment

A scrum master can avoid becoming an impediment to their team by frequently inspecting and adapting their behaviors.

Page 24: SDEC15:  Help the Scrum Master *IS* the Impediment

Common Scrum Master Impediments:• Agile Expert – one true way to “be agile”• Project Manager – assigning tasks• Technical Lead – dictating solutions to the dev team

Page 25: SDEC15:  Help the Scrum Master *IS* the Impediment

SUPER HERO(SM != Super Man)

Page 26: SDEC15:  Help the Scrum Master *IS* the Impediment

“I will solve all of your problems.”

Page 27: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 28: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 29: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 30: SDEC15:  Help the Scrum Master *IS* the Impediment

BEWARE LEARNED HELPLESSNESSHelplessness can lead to overlooking opportunities to improve

Page 31: SDEC15:  Help the Scrum Master *IS* the Impediment

“A dead scrum masteris a useless scrum master.”

--Ken Schwaber

Page 32: SDEC15:  Help the Scrum Master *IS* the Impediment

It’s Important to Try New Things

1

Page 33: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 34: SDEC15:  Help the Scrum Master *IS* the Impediment

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

--The Scrum Guide

Page 35: SDEC15:  Help the Scrum Master *IS* the Impediment

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

--Agile Manifesto

Page 36: SDEC15:  Help the Scrum Master *IS* the Impediment

“Experimentation is at the heart of Agile”

Page 37: SDEC15:  Help the Scrum Master *IS* the Impediment

Are experiments safe?

Page 38: SDEC15:  Help the Scrum Master *IS* the Impediment

“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.”

Page 39: SDEC15:  Help the Scrum Master *IS* the Impediment

Embrace Learning Opportunities(Failure)

2

Page 40: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 41: SDEC15:  Help the Scrum Master *IS* the Impediment

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…

Page 42: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 43: SDEC15:  Help the Scrum Master *IS* the Impediment

SCRUM IN ONE SLIDE

Development

Sprint Planning Sprint Review

Sprint Retrospective

Sprint

ROLES: Scrum Master, Product Owner, DeveloperARTIFACTS: Product Backlog, Sprint Backlog, Product Increment

Page 44: SDEC15:  Help the Scrum Master *IS* the Impediment

Is it safe to fail (learn)?

Page 45: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 46: SDEC15:  Help the Scrum Master *IS* the Impediment

Why? Why? Why? Why? Why?

3

Page 47: SDEC15:  Help the Scrum Master *IS* the Impediment

What is the 5 Why’s technique?

Page 48: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 49: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 50: SDEC15:  Help the Scrum Master *IS* the Impediment

People do not fail, systems do

Page 51: SDEC15:  Help the Scrum Master *IS* the Impediment

Learn Gradually

4

Page 52: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 53: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 54: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 55: SDEC15:  Help the Scrum Master *IS* the Impediment

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?

Page 56: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 57: SDEC15:  Help the Scrum Master *IS* the Impediment

Words Matter

5

Page 58: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 59: SDEC15:  Help the Scrum Master *IS* the Impediment

Your words are winning hearts and changing minds.

Page 60: SDEC15:  Help the Scrum Master *IS* the Impediment

Be consistent.

Page 61: SDEC15:  Help the Scrum Master *IS* the Impediment

Following through isn’t optional.

Page 62: SDEC15:  Help the Scrum Master *IS* the Impediment

Following through isn’t optional.

Page 63: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 64: SDEC15:  Help the Scrum Master *IS* the Impediment

“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.”

Page 65: SDEC15:  Help the Scrum Master *IS* the Impediment

Sustainable Pace Is Important

6

Page 66: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 67: SDEC15:  Help the Scrum Master *IS* the Impediment

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

--Agile Manifesto

Page 68: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 69: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 70: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 71: SDEC15:  Help the Scrum Master *IS* the Impediment

Sustainable pace is humane

Page 72: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 73: SDEC15:  Help the Scrum Master *IS* the Impediment

Play Well With Others

7

Page 74: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 75: SDEC15:  Help the Scrum Master *IS* the Impediment

“How inclusive is your team?”

Page 76: SDEC15:  Help the Scrum Master *IS* the Impediment

Temper dominant personalities

Page 77: SDEC15:  Help the Scrum Master *IS* the Impediment

Draw out the introverts

Page 78: SDEC15:  Help the Scrum Master *IS* the Impediment

Time Box Events

8

Page 79: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 80: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 81: SDEC15:  Help the Scrum Master *IS* the Impediment

SCRUM IN ONE SLIDE

Development

Sprint Planning Sprint Review

Sprint Retrospective

Sprint

ROLES: Scrum Master, Product Owner, DeveloperARTIFACTS: Product Backlog, Sprint Backlog, Product Increment

Page 82: SDEC15:  Help the Scrum Master *IS* the Impediment

Prevents over-investment in activities(Risk Mitigation)

Page 83: SDEC15:  Help the Scrum Master *IS* the Impediment

Promotes a focus on value(Risk Mitigation)

Page 84: SDEC15:  Help the Scrum Master *IS* the Impediment

Minimizes cost and impact of errors(Risk Mitigation)

Page 85: SDEC15:  Help the Scrum Master *IS* the Impediment

Limits WIP(Risk Mitigation)

Page 86: SDEC15:  Help the Scrum Master *IS* the Impediment

Be Kind

9

Page 87: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 88: SDEC15:  Help the Scrum Master *IS* the Impediment
Page 89: SDEC15:  Help the Scrum Master *IS* the Impediment

Make sure people are ready to hear what you have to say.

Page 90: SDEC15:  Help the Scrum Master *IS* the Impediment

??????

AGILE IMPACTS EVERYONE

• Organizational Change• Leadership Change• Team Change• Status Change• Job Description Change• Role Change• Culture Change

Page 91: SDEC15:  Help the Scrum Master *IS* the Impediment

“People who ask others to change may not understand what value they are asking people to give up. And in fact, they may not appreciate or even notice what’s valuable to the people they expect to change.”

--Esther Derby

Page 92: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 93: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 94: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 95: SDEC15:  Help the Scrum Master *IS* the Impediment

RESPONSES TO CHANGE ARE INVALUABLEWhat is the source of their resistance?

Do people know how to do what they are being asked to do?

Is there a personal conflict that is causing

resistance?

Is someone a champion of the

old process?

Are there systems in place

that reward disruptive behavior?

Is the path to success unclear

to them?

What does someone lose

due to the change?

Page 96: SDEC15:  Help the Scrum Master *IS* the Impediment

Focus on Management

10

Page 97: SDEC15:  Help the Scrum Master *IS* the Impediment

You are going to face a lot of wrong premises about what makes safety and speed possible.

Page 98: SDEC15:  Help the Scrum Master *IS* the Impediment

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

Page 99: SDEC15:  Help the Scrum Master *IS* the Impediment

Self-organization does not initially feel safe or fast.

Page 100: SDEC15:  Help the Scrum Master *IS* the Impediment

SCRUM MANAGEMENT • Manage the boundaries• Build Stable Teams

• Hire people – Grow skills• Act transparently• Examine systems &

correct faulty ones• Give guidance when

asked/needed• Reach across org charts• Definition of Done• Continuous improvement• Expect working software

every sprint

Vision – Direction – Goals

“I finally have time to do my job.”

Page 101: SDEC15:  Help the Scrum Master *IS* the Impediment

“A scrum teams job is to self-organize around the challenges, and within the boundaries and constraints, put in place by management.”

--Mike Cohn, Succeeding with Agile

Page 102: SDEC15:  Help the Scrum Master *IS* the Impediment

What must be true for a person to ask that question?

Page 103: SDEC15:  Help the Scrum Master *IS* the Impediment

“Agile is for IT. Why are you talking to HR and finance?"

Page 104: SDEC15:  Help the Scrum Master *IS* the Impediment

What must be true for a person to say that?

Page 105: SDEC15:  Help the Scrum Master *IS* the Impediment

“You can’t coach if you’ve never developed software. Pick another scrum master for this team."

Page 106: SDEC15:  Help the Scrum Master *IS* the Impediment

“Managers are still needed. Not so much for their planning and controlling ability, but for that important job of interfacing on the teams behalf with the rest of the organization.”

--Diana Larsen

Page 107: SDEC15:  Help the Scrum Master *IS* the Impediment

FEEDBACK

Page 108: SDEC15:  Help the Scrum Master *IS* the Impediment

http://[email protected]@ryanripleyPodcast available on iTunes, Stitcher, and ryanripley.com