Skip to content
Intent DrivenProduct

Practices

Hybrid Scrum, intentionally applied

Scrum remains our execution cadence, not our discovery engine.

Preserving agility without adding overhead. Scrum ceremonies and Intent‑Driven/SDD events should be combined when able and timeboxed for further overhead reduction.

  1. 01Intent

    Problem Framing

    Purpose: Define the right problem and align outcomes before discussing solutions.

    Problem framing creates alignment. It prevents teams from building the wrong thing efficiently.

    • User: Specific, contextual
    • Problem: Clear friction or failure
    • Business Impact: Measurable outcome
    • Evidence: Data or insights
    • Assumptions: Keep this high level. Reinforce clarity and specificity for each component

  2. 02Intent

    Hypothesis

    Purpose: Define testable intent and make explicit decisions before committing to scope.

    Hypotheses constrain scope. They allow teams to say no with confidence and yes with intent.

    Confidence emerges from

    • A specific user and behavior
    • A measurable, testable outcome
    • Evidence‑based rationale
    • Explicit risks and assumptions

  3. 03Intent

    Spec Planning

    Purpose: Lock decisions into a single source of truth before execution begins.

    Specifications do not explore possibilities; they encode decisions. They enable humans and AI to move fast without interpretation.

    Execution clarity emerges from

    • Clearly stated outcomes
    • Defined scope and non‑scope
    • Explicit constraints and tradeoffs
    • Acceptance criteria tied to hypotheses
    • Known risks and assumptions

  4. 04Execution

    Sprint / POD Planning

    Purpose: Commit to outcomes, not interpretations.

    If intent is still unclear during Sprint/POD Planning, the work is not ready.

    • Input: Approved specs representing locked decisions
    • Output: A Sprint Goal tied to measurable value
    • Task breakdown supports execution, not alignment

  5. 05Execution

    Daily Scrum

    Purpose: Inspect progress toward intent.

    The central question is: “Are we still on track to deliver the intended outcome?”

    • Focus on progress, risk, and blockers related to the Sprint Goal
    • Not a status meeting
    • Not a reporting ritual
    • Timeboxed to 5 minutes per POD of 2–3 developers

  6. 06Learning

    Sprint Review

    Purpose: Validate outcomes against intent.

    Reviews test truth, not effort.

    • Demonstrate working increments
    • Inspect results against hypotheses and constraints
    • Capture learning that may refine intent

  7. 07Learning

    Retrospective

    Purpose: Improve how intent becomes reality.

    Retrospectives improve how we think, and what is needed going forward, not just how we execute.

    Reflect on

    • Where intent was unclear
    • Where hypotheses were weak
    • Where AI helped or hurt clarity
    • Where decisions arrived too late
    • What measurable outcomes can be actioned going forward

Next

This is not waterfall — foundations

Closing

This manifesto does not replace Agile or Scrum. It completes them for an AI‑assisted world.

When execution accelerates, clarity must arrive earlier.

We commit to paying the cost of thinking sooner because it is cheaper, faster, and safer there.