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.
39 lines
1.6 KiB
YAML
39 lines
1.6 KiB
YAML
id: agile-retrospective-five-steps
|
|
title: Agile Retrospective
|
|
description: >-
|
|
A five-step team reflection meeting held at the end of an iteration to
|
|
improve process. Formalised in the Agile software development tradition,
|
|
drawing on Norm Kerth's retrospective prime directive.
|
|
source: Esther Derby and Diana Larsen, "Agile Retrospectives"
|
|
source_url: https://www.agileretrospectives.com/
|
|
tags: [agile, retrospective, teams, improvement]
|
|
forked_from: null
|
|
image: null
|
|
steps:
|
|
- headline: Set the stage
|
|
description: >-
|
|
The facilitator states the retrospective prime directive and checks in
|
|
each person briefly, setting psychological safety.
|
|
- headline: Gather data
|
|
description: >-
|
|
The team collects what happened during the iteration — events,
|
|
metrics, feelings — without interpretation.
|
|
- headline: Generate insights
|
|
description: >-
|
|
The team analyses the data for patterns and root causes, asking why
|
|
things happened as they did.
|
|
- headline: Decide what to do
|
|
description: >-
|
|
The team selects one or two actionable improvements for the next
|
|
iteration, with owners and due dates.
|
|
- headline: Close
|
|
description: >-
|
|
The facilitator closes with appreciation and a check on how the
|
|
retrospective itself went.
|
|
outcome: >-
|
|
The team commits to one or two concrete improvements owned by named
|
|
people, with shared understanding of why.
|
|
practice: >-
|
|
The prime directive matters: "Regardless of what we discover, we
|
|
understand and truly believe that everyone did the best job they could."
|
|
It prevents blame. |