Agile Standown
Use when asked about an agile "stand-down" — an informal end-of-day or end-of-session closing check-in some teams run as the counterpart to a morning standup (see agile-standup). This is a less standardized, less common practice than the standup itself — verify what a specific team actually means by the term before assuming a fixed format.
A "stand-down" is an informal team practice some organizations use as a closing counterpart to the morning Agile Standup — a brief end-of-day (or end-of-session) check-in summarizing what was actually accomplished, rather than what's planned. Unlike the standup, this isn't a standardized term with one universally agreed format — it shows up under this name in some distributed/remote teams and in organizations with a military or emergency-services background where "stand-down" already means "end of an active period," but a given team using the term may mean something a little different. Confirm what a specific team actually intends before assuming a fixed structure.
A common shape, where it's used
Where teams do run one, it typically mirrors the standup's brevity and timebox but flips the temporal focus:
- What did I actually get done today (as opposed to what was planned this morning)?
- Is there anything unfinished that needs to be flagged before the day ends, so it's not silently carried over unnoticed?
- Any blocker that needs attention before tomorrow, rather than waiting until the next morning's standup to surface it?
Why a team might want one
A morning standup plans the day; a stand-down closes it out — for teams spanning time zones, an end-of-day stand-down from one group can hand off open items to a team starting their day elsewhere, which a morning-only standup structure doesn't naturally support. It can also catch a blocker before it sits unaddressed overnight, rather than only surfacing it at the next morning's standup.
Relationship to standup and reflection
A stand-down isn't the same as Agile Reflection's retrospective practice — a stand-down is a brief, daily, factual check-out; a retrospective is a deeper, less frequent (commonly per-sprint) examination of process and behavior change. Nor is it a requirement of any major agile framework the way the standup effectively is in Scrum — treat it as an optional practice a team can adopt if it solves a real coordination problem (like time-zone handoff), not as something every agile team is expected to run.
Common pitfalls
- Assuming "stand-down" means the same thing across every team — given the lack of a standardized definition, confirm what a specific team means before facilitating or documenting one on their behalf.
- Running both a standup and a stand-down with identical content — if the stand-down just repeats the same three standup questions without the forward/backward temporal distinction, it's redundant meeting overhead rather than a genuinely useful addition.
- Treating it as a substitute for a real retrospective — a daily factual check-out doesn't provide the deeper process reflection Agile Reflection is meant to produce.
Learn more
- Agile Standup for the well-established morning counterpart this practice mirrors.
- Agile Reflection for the deeper, less frequent retrospective practice this is not a substitute for.