Kickoff - Junior Edda

Description

Kickoff establishes the Delivery Manager, normalizes validated business evidence into a Vision/Scope Handover Package, and drafts Charter v0 before Inception begins. Bootstrap the Team is a one-time onboarding shell that starts here and deliberately continues across Inception, Elaboration, and the first Construction iteration; only its first three activities belong to Kickoff.

Activities in this Phase

Order	Name	Actions
Bootstrap the Team
#1	Assign the Delivery Manager	Read the 'BTM-1 Assign the Delivery Manager' activity from playbook 'Junior Edda' (workflow 'Bootstrap the Team'). Follow its guidance when assisting me. ## Objective Have the project sponsor appoint the Delivery Manager before the Delivery Manager performs any project work. An AI agent must not appoint itself or infer a person. ## Procedure 1. Obtain the sponsor's explicit appointment. 2. Record it in `docs/project/DELIVERY_OWNERSHIP.md` with: - Delivery Manager name and contact; - start date and timezone; - decision authority and approval boundaries; - escalation route and response expectation; - backup/delegate; - responsibility for Charter ownership, cadence, AIN oversight, and Risk/Problem tickets. 3. Confirm the appointee accepts the role. 4. If no person is available, record the sponsor as interim DM with an expiry/review date; do not leave ownership implicit. ## Completion evidence The assignment record exists, names both sponsor and DM, contains authority boundaries, and includes appointment and acceptance timestamps. Staffing is a human/sponsorship action; the activity deliberately has no executing Mimir Agent.
#2	Absorb Vision/Scope Handover	Read the 'BTM-2 Absorb Vision/Scope Handover' activity from playbook 'Junior Edda' (workflow 'Bootstrap the Team'). Follow its guidance when assisting me. ## Objective Normalize validated business evidence into `docs/project/VISION_SCOPE_HANDOVER.md`, the single handoff consumed by Charter drafting and ESM. ## Required external inputs Use the latest approved outputs from Testing a Business Idea when that playbook was run: Customer and USP Dossier, Experiment/Test Charter, Approved Learning Card, Feasibility Decision, and Recommended Next Experiment. The external playbook currently ends at Approve the Learning and Decision; do not look for a nonexistent activity named “Prepare handover package for Junior Edda.” Equivalent sponsor-approved evidence may be used when Testing a Business Idea was not run. ## Procedure 1. Inventory each source with title, version/date, owner, and location. 2. Fail fast if there is no approved feasibility decision or if the decision is `stop`. An `adapt` decision must state the approved adaptation before continuing. 3. Extract: target customer/personas; jobs/pains/gains; USP; observed evidence; assumptions; product scope; excluded scope; constraints; success/failure criteria; outstanding risks; recommended next step. 4. Preserve provenance. Label every item `observed`, `approved decision`, or `assumption`. 5. Reconcile contradictions with the sponsor; do not silently choose one source. 6. Write the normalized document and an unresolved-questions table with owner and due date. ## Completion evidence The handover exists at the canonical path, cites every source, contains an explicit continue/adapt decision, distinguishes evidence from assumptions, and has no ownerless blocker. Record its version and approval.
#3	Draft Charter v0	Read the 'BTM-3 Draft Charter v0' activity from playbook 'Junior Edda' (workflow 'Bootstrap the Team'). Follow its guidance when assisting me. ## Objective Create the executable project-management contract at `docs/project/CHARTER.md` from the normalized handover. Charter v0 must be approved before Inception starts. ## Plan first Enter the ADE's planning mode when available. Otherwise write a step-by-step drafting plan. Sections may be drafted in parallel only when each worker writes a separate section and one final worker checks cross-section consistency. ## Required structure 1. Goals — outcome, measure, target, target date, evidence source, owner. 2. Team Roster — person/agent, mission, authority, owned workflows/artifacts, meetings, backup. Include team maturity: `L2 \| early-L3 \| late-L3 \| L4`, supporting evidence, assessor, and assessment date. 3. Variables We Track — one row per stable `variable_id` with definition, unit, source system, exact query/command, aggregation/window, freshness limit, Green/Yellow/Orange/Red or Green/Red thresholds, missing-data behavior, owner, and `gating_policy: observe \| pause_new_work \| block_release`. 4. Artifact Coverage Decision — artifact, required?, canonical path/system, owner, freshness rule, validation command. 5. Cadence — current iteration-length decision process, ceremonies, participants, trigger, duration; recurring meetings only when team size is greater than one. 6. Release Roadmap — alpha/beta/gamma/RC, explicitly marked aspirational until EST validates it. ## Procedure and gates - Cite every statement back to the Vision/Scope Handover or label it as an assumption. - Use stable IDs for variables and artifacts; display names may change without breaking history. - Define `Unknown` handling separately from performance bands. Missing/stale evidence is never Green. - Obtain explicit sponsor and Delivery Manager approval. ## Completion evidence All six sections exist; every variable is mechanically measurable; every required artifact is locatable and testable; maturity has evidence; gating policies are explicit; the roadmap is labeled aspirational; approval and version `v0` are recorded.