Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Why and When to Fire a Scrum Master

null
by

Andrej Ruckij

on 5 December 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Why and When to Fire a Scrum Master

When and Why to "fire"
Football
a Scrum Master?

team game
complexity
coaching
tactics
strategy
leaders
people
fans

About myself
development manager
@ruckiand
www.agilemindstorm.com
Interested in:
- network organizations
- no management
a.k.a. Scrum Master
Football coach?
* called Manager in UK; and responsibilities differ in various clubs
so,
when
and
why
to fire
Analogies i use in my head...
competition
Football team
Product team
Developer/QA/...
Defender/Striker/...
Scrum Master
Team coach
Tournament (normally several)
Product Roadmap
Game
Sprint
Club Manager + Fans + Others
PM/PO + Users + Others
World level
Football team
without the Coach
I suppose you don't imagine...
When?
why?
Makes most decisions
for the team
Team loses opportunity to get better
but team plays the game
Agreed instructions before,
Micro management of the team
When?
why?
Actions are taken only based
on results of latest game
Tournament is the target
must look 5/10 games ahead
Sometimes you seek a draw in a game
Problems are analyzed in the scope of single sprint, not the Roadmap
Every game is not
"The Finals"!
When?
why?
Games are not analyzed
Team and players will not learn and improve
Each game is analyzed
No (powerful) retrospectives
Mistakes are discussed
No data gathered for a discussion
When?
why?
Not preparing for the game
Good result depends on knowing:
weaknesses, tactics, objectives, importance
Team prepares for each game,
but knows the final Target
No Roadmap No backlog grooming
No clear priorities
When?
why?
Critical problems are not
addressed immediately
Won't make changes, will lose the game
Substitute injured player
Discipline
Scope creep
Interruptions
Change tactics
Lousy requirements
When?
why?
Status Quo
is not challenged
You can't win the tournament(s)
without changing the game
Not a transformation agent
No (powerful) retrospectives
Experiments with:
tactics, strategy, homework tricks
Not trying new things
Can't win if predictable
When?
why?
Doesn't care about
the Trophy!
Because it's weird
Process is the goal,
not a tool to achieve results
They have the same
Target!
When?
why?
Doesn't care about
the Fans!
Fans are huge motivation for the team
No users at your sprint reviews
No real feedback from users
Team plays for fans!
Playing at home stadium is an advantage
Players love appreciation and support
When?
why?
Team doesn't win
Developers, POs, Other teams
Culture, Organization, Obama
are blamed...
No one cares, team must achieve results
Common saying:
Team wins the game,
but coach loses
There are more...
Team formation/Hiring

Education/Training

Youth

Bad players sit on bench
but all this might be less relevant for SM role...
when at least 3 things are missing
Thinks about value
& process is a tool

Maintains big picture
Focused on improvements

& Radiates information
Last game
Next game
How many are needed?
What should be
responsible for?

Depends on...
Your personal understanding

Company/work type

Culture

Budgets
One club example...
First team manager
4 coach assistants
Goalkeeper coach
Technical director
Medical director
Fitness coach
Youth team manager
Under 21 coach
Senior scout
Academy manager
Match analyst
24 players in the first team
14 "coaches/supporters"
uncertainty
9 statements
Dynamics are important,
not the last game
Team thinks only one sprint ahead
and create value for users
"Fire" carefully :)
Conclusion
Scrum Master
Coach
"fire"
or
But
...

It's the same Team Member
although has different,
non-technical skills.
Which can boost your team a lot!
Diversity rocks!
www.nomanagement.org
Full transcript