A Pair of Programming People

driver

navigator

driver

navigator

Navigator is bored or doesn't know what's going on

Driver is confused, navigator has trouble explaining

A different way: "pob programming"

driver

navigator

driver

navigator

Choosing a Task

1. Limited Scope (2 - 3 points)
2. Choose your mobbers (3 - 4 people)
3. Span 2+ parts of the stack (ops/frontend/backend/jobs)
4. Something fun!

Before the Session

1. Create a branch for your mob work
2. Compile everything relevant (frontend, backend)
3. Push it to GitHub
4. Poke your fellow mobbers and make sure they have the branch compiling before the session

Session Start!

1. Fact-finding session: talk through ideal implementation details for 20 minutes. Get relevant background from knowledgeable mobbers.
2. Assign a time keeper
3. Determine order of mob cycle (I like random.org)
4. Go!

During the Session

1.  Current driver writes code, using navigating mobbers as support
2. When time (20 minutes) is up, time keeper instructs driver to commit their code.
3. Next driver pulls the code and continues where previous driver left off.
4. Continue until each mobber has driven at least once (alt: until the feature is complete).

After the Session

1.  Retrospect on your changes: What went well? What didn't? What did we learn? What is left to do?
2. Assign an owner to finish up the rest of the task, if incomplete
3. Owner completes task as a part of their iteration work