KEMBAR78
Collaboration Principles from Mob Programming | PPTX
© 2010 Columbia Tristar Marketing Group, Inc.
© 2010 Columbia Tristar Marketing Group, Inc.
It takes high quality collaboration
Collaboration Principles from
Mob Programming
Mike Clement
@mdclement
mike@softwareontheside.com
http://blog.softwareontheside.com
Why listen to me?
https://twitter.com/ChristophLucian/status/482651109173895168
27 Jun 2014
https://twitter.com/ChristophLucian/status/482651109173895168
27 Jun 2014
Why listen to me?
Maybe you
shouldn’t?
"All methodologies are based
on fear."
Kent Beck
"All methodologies are based
on fear."
Kent Beck
What is Mob Programming?
https://twitter.com/ChristophLucian/status/482651109173895168
27 Jun 2014
https://twitter.com/ChristophLucian/status/482651109173895168
27 Jun 2014
All the brilliant people,
working on the same thing,
at the same time,
in the same space…
All the brilliant people,
working on the same thing,
at the same time,
in the same space,
and at the same computer.
Driver (at the keyboard)
Navigator
Mobber
Mobber
https://github.com/willemlarsen/mobprogrammingrpg
Mob testing, Mob design
Quality Collaboration is
Challenging
Coordination
Coordination
Working together
Why bother?
"All methodologies are based on
fear. You try to set up habits that
prevent your fears from becoming
reality."
Kent Beck
Unproductive meetings
https://vincentdnl.com/drawings/pair-programming2
https://www.chrislucian.com/2016/05/mob-programming-q.html
Six Reasons For Meetings
• Connect
• Align
• Decide
• Ideate/Brainstorm
• Plan
• Produce
Mamie Kanfer
Stewart
Zoom Fatigue?
What is
zoom
fatigue?
Artificial Harmony
Productive
Ideological Conflict
Interruption
Distributed Cognition
https://tanzu.vmware.com/content/blog/another-perspective-on-interrupting-developers-at-work
Strong Style Pairing
"For an idea to go from
your head into the
computer, it MUST go
through someone
else's hands"
-Llewellyn Falco
Intent
Location
Detail
Stagnant Skills
“What happens if we
invest in developing our
people and then they
leave us?”
“What happens if
we don’t, and they
stay?”
“What happens if we
invest in developing our
people and then they
leave us?”
Learn as you go
Learn from each other
Hidden Work and Queues
Luke Barrett via User Story Mapping, Jeff Patton
Rogue Features
Merging
https://www.wsbtv.com/news/local/north-fulton-county/3-cars-try-fitting-sandy-springs-i-285-exit-same-time/P7WM6SS6EBDSNO4H3E2I6UT7IQ/
Google Docs/Sheets
Low Quality Work
Work Out
Loud
Not Finishing
"All methodologies are based on
fear. You try to set up habits that
prevent your fears from becoming
reality."
Kent Beck
Fears
• Unproductive Meetings
• Interruptions
• Stagnant Skills
• Hidden Work/Rouge Features
• Merging
• Low Quality Work
• Not Finishing
Join us at Emmersion as a "guest
mobber":
https://bit.ly/emmersion-guest-mobber
Mike Clement
• @mdclement
• mike@softwareontheside.com
• http://blog.softwareontheside.com
• https://www.linkedin.com/in/mclement/
• https://github.com/mdclement
• Software Crafters Atlanta
• Find us on meetup.com
• UtahSC
• http://utahsc.org/
• Global Day of CodeRetreat
• https://www.coderetreat.org/

Collaboration Principles from Mob Programming

Editor's Notes

  • #2 Creation of software is portrayed in the media as a solo endeavor
  • #6 Stop around 20 seconds in
  • #10 Instead of this nonsense, what does adding additional people to a team look like?
  • #20 Hunter Industries, birthplace of Mob Programming
  • #21 Hunter Industries, birthplace of Mob Programming
  • #23 Mob first Hybrid mob, even before the pandemic
  • #26 And mob programming is no different
  • #29 And mob programming is no different
  • #31 Often more the same than we think
  • #33 Hunter Industries, birthplace of Mob Programming
  • #34 Hunter Industries, birthplace of Mob Programming
  • #35 Woody Zuill defines Agile as…
  • #49 Not “Fear Driven Development”
  • #59 Mob first
  • #60 Mob first
  • #64 Diversity vs Conformity
  • #65 Reduce unproductive conflict – via commit wars/pr battles, passive aggressive comments
  • #70 Lottery factor
  • #83 Might be as trivial as keyboard shortcuts As significant as understanding the architectural patterns of the system
  • #84 Onboarding is simplified
  • #89 Much hard to know if we align with knowledge work
  • #91 One thing – Priority
  • #92 Working together towards a unified outcome
  • #96 Trunk based development
  • #102 Feedback loops
  • #113 Not “Fear Driven Development”