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.
36 lines
1.4 KiB
YAML
36 lines
1.4 KiB
YAML
id: stand-up-meeting
|
|
title: Daily Stand-Up
|
|
description: >-
|
|
A short daily team sync in which each member states what they did, what
|
|
they will do, and what is blocking them. Originating in Scrum and Agile
|
|
software development, derived partly from Toyota's morning meetings
|
|
(chorei).
|
|
source: Scrum Guide / Agile Alliance
|
|
source_url: https://www.agilealliance.org/
|
|
tags: [agile, standup, teams, sync]
|
|
forked_from: null
|
|
image: null
|
|
steps:
|
|
- headline: Gather standing
|
|
description: >-
|
|
The team gathers standing, at the same time and place each day, around
|
|
the team's visible work board. Standing signals brevity.
|
|
- headline: Each person reports
|
|
description: >-
|
|
Each member states three things: what I did since last stand-up, what
|
|
I will do by next stand-up, and what is blocking me.
|
|
- headline: Park discussions
|
|
description: >-
|
|
Any topic requiring more than a minute is "parked" for a separate
|
|
conversation after the stand-up, with those involved.
|
|
- headline: Confirm blockers
|
|
description: >-
|
|
The facilitator confirms who will address each blocker and by when,
|
|
and the stand-up closes.
|
|
outcome: >-
|
|
The team synchronises daily on progress and impediments in under fifteen
|
|
minutes, with blockers surfaced and owned.
|
|
practice: >-
|
|
Keep it under fifteen minutes. The stand-up is not problem-solving —
|
|
park everything that is not a status report. Face each other, not the
|
|
manager. |