Mob programming - Speaker Deck

Slide 1

Slide 1 text

Mob programming Ivan Zimine 22 March, 2018

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

Mob programming workshop, Singapore, Nov 2017

Slide 5

Slide 5 text

— Woody All the brilliant minds working on the same thing… at the same time… in the same space… on the same computer… What is Mob programming? Woody Zuill

Slide 6

Slide 6 text

How does it look in practice?

Slide 7

Slide 7 text

https://www.youtube.com/watch?v=p_pvslS4gEI

Slide 8

Slide 8 text

https://devblog.xero.com/mobprogramming-xp-34d1a8c99a9d Big table Big screen One keyboard

Slide 9

Slide 9 text

http://benjiweber.co.uk/blog/2014/11/30/the-unruly-mob/ Two screens One keyboard

Slide 10

Slide 10 text

driver big screen navigator/ observers ﬂip chart Typical setup

Slide 11

Slide 11 text

BIG screens http://www.chrislucian.com/2016/05/mob-programming-q.html

Slide 12

Slide 12 text

Anti-pattern http://www.full-stackagile.com/2016/07/28/mob-programming-what-is-it/

Slide 13

Slide 13 text

Alternative setup

Slide 14

Slide 14 text

mirrored screens Alternative setup ﬂip chart

Slide 15

Slide 15 text

It’s not about the keyboard

Slide 16

Slide 16 text

Summary of how whole team works in the same physical space the space is comfortable and ergonomic team decides how to setup their space

Slide 17

Slide 17 text

Driver Navigator Observer

Slide 18

Slide 18 text

For an idea to go from someone’s head into the computer it must go through someone else’s hands — Llewellyn Falco

Slide 19

Slide 19 text

Driver: follows instructions from navigator (smart input device) Navigator: Solves current problem Observer: Thinks about what to do next driver navigator observer

Slide 20

Slide 20 text

Rotation: - time-box - task driver navigator observer

Slide 21

Slide 21 text

Summary of Driver/Navigator/Observer Driver == “smart input device” Navigator and observer: solve the problem Separation of cognitive load Discipline and respect for all ideas

Slide 22

Slide 22 text

Why would anybody want to work this way?

Slide 23

Slide 23 text

How can 5 people be productive working on the same computer?

Slide 24

Slide 24 text

How about asking another question…

Slide 25

Slide 25 text

(slides from Woody’s workshop) Most of those disappear when the team works together most of the time.

Slide 26

Slide 26 text

Key benefits Team jelling Focus & flow Code and product quality Continuous learning

Slide 27

Slide 27 text

How to get started? Must be voluntary Team’s decision to experiment Learn to work well together There is no “one right way” Frequent retrospectives

Slide 28

Slide 28 text

— Woody The people doing the work can best determine how to do that work Summary of why