Protocolbot
d19a75ace4
All 100 seed YAML files now have: - Filenames that match their id field - IDs that are slugs of their titles - No cultural identifiers in titles or IDs 70 files renamed. e.g. quaker-meeting-for-worship.yaml -> meeting-for-worship.yaml, moroccan-jmaa-village.yaml -> jmaa-village-assembly.yaml, japanese-hansei.yaml -> hansei-reflection.yaml
36 lines
1.4 KiB
YAML
36 lines
1.4 KiB
YAML
id: daily-stand-up
|
|
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. |