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.
40 lines
1.8 KiB
YAML
40 lines
1.8 KiB
YAML
id: open-agile-roadmap
|
|
title: Open Agile Roadmap Planning
|
|
description: >-
|
|
A collaborative planning method where a team builds a visual roadmap by
|
|
placing stories on a timeline together, negotiating dependencies and
|
|
priorities in real time. Used in Agile and Lean software teams as a
|
|
alternative to top-down roadmap assignment.
|
|
source: Agile planning tradition / Mike Cohn, "Agile Estimating and Planning"
|
|
source_url: https://www.mountaingoatsoftware.com/
|
|
tags: [agile, roadmap, planning, collaboration, teams]
|
|
forked_from: null
|
|
image: null
|
|
steps:
|
|
- headline: Lay out the timeline
|
|
description: >-
|
|
A long wall or board is laid out with a time axis — quarters or
|
|
months. The team gathers around it with story cards ready.
|
|
- headline: Place stories together
|
|
description: >-
|
|
Each team member places stories they believe belong on the roadmap,
|
|
explaining the placement. Others may move them, with discussion.
|
|
- headline: Negotiate dependencies
|
|
description: >-
|
|
The team draws dependency arrows between stories, surfacing what
|
|
must come before what. Conflicts are resolved in the open.
|
|
- headline: Mark priorities and risks
|
|
description: >-
|
|
The team marks the highest-priority stories and the highest-risk
|
|
ones, so the roadmap shows not only sequence but attention.
|
|
- headline: Photograph and commit
|
|
description: >-
|
|
The roadmap is photographed and recorded. The team commits to it as
|
|
a living plan, revisiting it each iteration.
|
|
outcome: >-
|
|
A shared roadmap that all participants shaped, with dependencies and
|
|
priorities visible, owned by the team rather than handed down.
|
|
practice: >-
|
|
The physical placement is the point — people who place cards themselves
|
|
commit to them more than those who receive a slide. Revisit it; a
|
|
roadmap that does not change is not being used. |