Skip to content
FitSD

S0 — The stand-up workshop

Seat: the team manager, acting as FitSD Management System Owner, running the half-day stand-up with the executive (who ratifies). The scenario’s people table names both. Runs: first, before everything. Reads: {SCENARIO}, findings-template.md, the standard at {STANDARD}. Writes: {RUN}/artifacts/S0-adoption-pack.md; {RUN}/findings/S0-standup.md.

Brief

You are standing FitSD up for the scenario’s team, some months before the project begins (the scenario’s timeline says when). Do the actual work: read the standard the way a real adopting manager would — README, then the adopter’s path (Quickstart, Framework Charter, Requirements, Implementation Guide — your main script — Service Acceptance Criteria, Information Stores), following wherever the checklist sends you.

Produce the adoption pack by working the Implementation Guide’s stand-up checklist in order, every step:

  1. The scope statement.
  2. Named owners and the Approver — including your escalation line and the alternate approver, if the standard prompts for them; log a finding either way.
  3. The four forms adopted + your net-new effort line (pick a number, justify it in a line).
  4. Your ratified SAC baseline — the heart of the exercise. Fill every row with concrete, realistic thresholds for the scenario’s team (real availability target, real backup-test cadence, real patch timescales, a real continuity rule, a real severity scheme, real support-model answers, a documentation set, applicability rules if any). Complete the ratification block.
  5. The implementation profile — point the reference-out capabilities at plausible, invented local policies.
  6. The registers, each with a named home.
  7. The review cadence.

Findings focus

Log from both hats (the manager doing the work; the executive who must ratify and later defend it): Was each step completable from the standard alone? Where did you have to invent structure (not values — the values are yours by design)? What confused you — who ratifies, who approves at what risk, where the pack itself lives? What worked well?

Constraints

In character in the artifact (a real team’s internal page, dated on the scenario timeline); out of character in findings. British English. Do not modify the standard. Do not read any other run files.

ccFitSD is released under CC BY 4.0