Protocolbot
3522c2ec5c
Added 94 new protocol YAML seed files covering diverse global cultures and practices: Indigenous & traditional: Maori powhiri, Aboriginal yarning, Somali xeer, Moroccan jmaa, Tswana kgotla, Zulu imbizo, Peruvian ronda campesina, Ohlone land-back, Inuit IQ consensus, Haudenosaunee condolence, Navajo peacemaking, Ojibwe pipe ceremony, Polynesian talanoa, Rwandan gacaca, West African palaver tree, Mexican tequio, Javanese musyawarah-mufakat, Tibetan story council, Korean yangban, Filipino utari, Ainu practices Religious communities: Quaker meeting for business, clearness committee, Amish shunning (Meidung), Mennonite discernment, Jewish hevruta, Rastafari nyabinghi reasoning Facilitation: World Cafe, Open Space, Future Search, Six Thinking Hats, Dynamic Facilitation, Socratic Seminar, Delphi method, Copenhagen Consensus, Lean Coffee, Hackathon sprint, Agile retrospective, Stand-up meeting, Pair programming, Roadmap planning Governance: Sociocratic consent selection, Dynamic self-governance, Cooperative consensus, Hackerspace consensus, Mastodon governance, Climate assemblies (x2), Basque asamblearismo Conflict & repair: Restorative conference, circle sentencing, Nonviolent Communication (3 protocols), Active listening mirror, Appreciative apology repair Community & care: Community kitchen, Gratefulness circle, Passing circle, Paired walking, Deep listening dyad, Mutual aid, Permaculture charrette Education: Barefoot College night school, Socratic seminar Everyday: Various greeting, transition, and gratitude protocols All protocols credit original sources. Cultural context noted in descriptions. All YAML files validated.
43 lines
1.8 KiB
YAML
43 lines
1.8 KiB
YAML
id: pair-programming-driver-navigator
|
|
title: Pair Programming Driver-Navigator
|
|
description: >-
|
|
A software development practice where two programmers work at one
|
|
keyboard, switching between the "driver" who types and the "navigator"
|
|
who reviews in real time. Originating in Extreme Programming (XP),
|
|
formalised by Kent Beck.
|
|
source: Kent Beck, "Extreme Programming Explained"
|
|
source_url: https://www.agilealliance.org/
|
|
tags: [pair-programming, xp, software, collaboration, agile]
|
|
forked_from: null
|
|
image: null
|
|
steps:
|
|
- headline: Assign roles
|
|
description: >-
|
|
The pair decides who will drive (type, focus on the immediate code)
|
|
and who will navigate (review, think ahead, raise concerns). Only
|
|
the driver types.
|
|
- headline: Work the task together
|
|
description: >-
|
|
The pair works the task, talking continuously. The navigator
|
|
questions and suggests; the driver implements and explains what they
|
|
are doing.
|
|
- headline: Switch on a timer
|
|
description: >-
|
|
The pair switches roles at a fixed interval — often 25 minutes — or
|
|
at natural breakpoints, so both drive and both navigate.
|
|
- headline: Negotiate the approach
|
|
description: >-
|
|
When the pair disagrees on approach, they discuss until they reach a
|
|
shared way forward. If they cannot, they may test both approaches
|
|
briefly and choose.
|
|
- headline: Commit together
|
|
description: >-
|
|
The pair commits the code together, with both names on the commit.
|
|
The work is owned by both.
|
|
outcome: >-
|
|
Code is produced with continuous review and shared understanding, owned
|
|
by both programmers, with knowledge transfer built in.
|
|
practice: >-
|
|
The timer-driven switch is what keeps it from becoming one person
|
|
watching another type. If the navigator goes silent, the pair has
|
|
broken — name it and re-engage. |