Слайд 1Scrum Master Lessons from
My 4 Year Old Son
Слайд 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
Слайд 8
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
Слайд 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
Слайд 13The Scrum Values:
Commitment
Respect
Focus
Openness
Courage
LINK: http://agileanswerman.com/scrum-values-can-make-or-break-your-agile-project/
Слайд 15 “Anything that prevents the scrum team from being productive.”
Слайд 16Every 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
Слайд 18It’s Important to Try New Things
1
Слайд 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”
Слайд 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!”
Слайд 28Embrace Learning Opportunities
(Failure)
2
Слайд 29“DAD! Stop helping me!”
--My son, tired of me inflicting help
Слайд 30Happy 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…
Слайд 31Not every experiment is a winner…and not every failure is a
loser.
Слайд 32
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
Слайд 34“That developer is slacking. When is the scrum master going to
take care of the poor performer?”
Слайд 38Often we push past the surface issues and find more complex
system and relationship issues at the 5th “why”
Слайд 42“I don’t think that design will work. You should code the
story like this…”
Слайд 43THINGS 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?
Слайд 44ADJUSTMENTS:
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?”
Слайд 48Your words are winning hearts and changing minds.
Слайд 50Following through isn’t optional.
Слайд 51Following 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.”
Слайд 54Communication is your greatest tool. How you frame discussions WILL make
or break your agile transformations and projects.
Слайд 57“Agile processes promote sustainable development. The sponsors, developers, and users should
be able to maintain a constant pace indefinitely.”
--Agile Manifesto
Слайд 58Sustainable pace is a quality play
Burned out developers deliver bad code
They
also find better jobs
Слайд 59Sustainable pace is a productivity play
Continuous integration, automated testing, skill building,
and whole team understanding become important when long hours are not an option
Слайд 60Sustainable 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
Слайд 62“Your team leaves at 5:00pm and refuse to work weekends. Why
don’t they have a sense of urgency?”
Слайд 67“That’s not how it’s done! Here, let me show you the
“right way” to be agile…at 2am.”
Слайд 69ARE YOU A HERO?:
Team seeks your approval before acting
Team asks about
the “right way” to do Agile
Are you insisting on “correct” solutions?
Слайд 70THINGS TO CONSIDER:
Resist the urge to solve the teams problems
Get comfortable
with awkward silence
Focus on relationships
Слайд 71BEWARE LEARNED HELPLESSNESS
Helplessness can lead to overlooking opportunities to improve
Слайд 74A time box is a fixed period of time to perform
an action or to achieve a goal.
Слайд 75
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
Слайд 76Prevents over-investment in activities
Слайд 78Minimizes cost and impact of errors
Слайд 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?”
Слайд 83ARE 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
Слайд 86 “A project manager could maybe become a tester...maybe.”
--Ken Schwaber
Слайд 87“500 YARDS OF FOUL-SMELLING MUCK”
--Red “The Shawshank Redemption”
The PMP® to CSM®
pipeline…
Слайд 88We are telling people to give up the tools, methods, processes,
and behaviors that have made them successful.
Слайд 89INSPECT:
How the team manages their work
Focus of Daily Scrum meeting
Unsolicited advice
Interrupting
progress to pontificate
Слайд 90ADAPT:
Questions over statements (2:1 ratio)
Make failure an option – and then
fail
The team owns tasks and solutions
Ask for permission to help
Слайд 92http://agileanswerman.com
ryan@agileanswerman.com
@ryanripley
Podcast available on iTunes, Stitcher, and AgileAnswerMan.Com
Слайд 93IMAGE ATTRIBUTION
“Broccoli” - ©Julia Frost – Flickr.com – Creative Commons License
“Singleton
Bank Rail Crash” – Public Domain
“Soap” - ©Frankleleon – Flickr.com – Creative Commons License