Slides from my talk at DDD North 2017 on mob programming and it's relation to other development styles, xp, pairing and swarming.

1. Married
to the Mob
(programming)

2. hey hi hello
derek graham @deejaygraham

6. The characters and events
depicted in this
presentation are fictitious.
Any similarity to actual persons,
living or dead, is purely
coincidental

7. Mob?

11. are you
XP?

12. XP Engineering Practices
• Continuous
Integration
• Pair Programming
• Test Driven
Development
• Simple Design
• Refactoring
• Collective Code
Ownership
• Sustainable Pace

13. Swarming

14. – Our Team
“Swarming … is the first time
we’ve felt like a genuine
team instead of individuals
all working for the same
manager.”

16. –Woody Zuill
“All the brilliant people,
working on the same thing,
at the same time,
in the same space,
and at the same computer.”

17. Mob = XP++

18. –Rachel Davies (Agile Coach)
“ Mobbing would be
in the XP book
(if they'd thought of it)”

19. Mob !=

20. Mechanics

21. •One set of Input Devices (keyboard
and mouse)
•Everyone can see thecode
•Everyone has a role
•Roles rotate through the team

22. *reconstruction

23. Mob Roles

25. Navigator Driver

26. Driver
*reconstruction

27. Navigator
*reconstruction

28. *reconstruction

29. Navigator
Navigator
Navigator
Facilitator?
Driver
*reconstruction

31. Mob Rule(s)

32. •Kindness
•Consideration
•Respect
•“Yes and…” ideas
•Strong Pairing

34. – Woody Zuill
“We decided for one day to
pretend to be kind,
considerate and respectful.
And then we decided to do it
again.”

35. –Norm Kerth
“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.”

36. if you aren’t learning or
contributing, find a better
use for your time.

37. Driver

38. Driver Typist

40. Cortana for Code
1.Listen to the mob
2.Translate that into code
3.There is no 3

41. Siri for Syntax
• Write the Code
• Talk about the Code
• Rollback?
• Patience
• Incomplete Understanding

42. Alexa for Algorithms

43. If you have the keyboard,
you can’t have the ideas

44. Mob % Typist

45. Mob
1.Collaborate & Discuss
2.What is the next step?
3.Talk to the Typist
4.Park other issues

46. The team is like an extended
brain, it needs to talk out
loud to know what it thinks

47. Environment

50. Other computers are
allowed!

51. Rotation

52. *reconstruction

53. Navigator
Navigator
Navigator
Facilitator?
Typist
*reconstruction
Timer

55. Team work

56. When to mob…
• Always :)
• Green field projects
• New work
• Hard problems
• Code Merges?
• Group learning

57. When not to…
•Sys admin and Dev Ops (pair instead)
•Long running tasks
•Small problems
•JFDI

58. Disagreements
& Uncertainty

60. Inspect
& Adapt

61. •Informal Huddle
•As often as you need to:
•How are we doing?
•What is easy?
•What is hard?

62. Turn up the Good!

63. <strong>
</strong>

64. Have you ever
had a bug?

70. –Llewellyn Falco
“For an idea to go from
your head into the computer,
it MUST go through
someoneelse'shands.”

71. Finding the right level
•Abstractions
•Language syntax
•Files, line numbers
•Key presses

72. Resources

73. Mob-Positive Teams
• Hunter Industries
• Industrial Logic
• Alaska Airlines
• LateRooms.com
• pluralsight.com
• GDS (gov.uk)
• Unruly Media
• Blue Fruit
• Menlo innovations
• …and many more

74. • Mobbing - http://mobprogramming.org
• Woody Zuill - https://www.industriallogic.com
• Chris Lucian - http://www.chrislucian.com/
• mob timer - https://github.com/dillonkearns/mobster
• Strong style pairing - https://llewellynfalco.blogspot.co.uk/
• Amy Edmondson - https://hbr.org/2013/12/the-three-
pillars-of-a-teaming-culture

75. https://leanpub.com/mobprogramming

76. https://leanpub.com/codingdojohandbook

77. https://github.com/willemlarsen/mobprogrammingrpg

78. Problem Solving
Bray, R. M., Kerr, N. L., & Atkin, R. S. (1978). "Effects of group size,
problem difficulty, and sex on group performance and member
reactions." Journal of Personality and Social Psychology, 36,
1224-1240.

79. What can you
take away?

80. •Experiment and discover what works
for you
•Expect to evolve
•Culture change is hard
•Flash Mob?
•If nothing else…

81. <strong>
</strong>

85. Me
• @deejaygraham
• deejaygraham@icloud.com
• deejaygraham.github.io
• http://www.nebytes.net
• https://www.meetup.com/Agile-North-East/