Skip to content
Intent DrivenProduct

Foundational information

This is not waterfall.

Waterfall delays learning until after implementation. Intent‑driven delivery brings learning forward, when it’s cheaper.

This model only works if teams are protected in doing upstream thinking, especially under urgency.

Skipping clarity doesn’t save time — it defers cost with interest.

Clarity

What this is — and is not

What this is not

  • It is not waterfall

    • We do not attempt to predict everything upfront
    • We expect change
    • We revise specs when intent changes
  • It is not big‑design‑up‑front

    • Specs capture decisions, not exhaustive designs
    • Unknowns are allowed, assumptions must simply be visible
  • It is not more bureaucracy

    • Approval is a quality gate, not a meeting
    • Most alignment happens once instead of repeatedly during build

What this is

  • It is Agile

    • We welcome change with explicit intent
    • We prioritize outcomes over output
    • We inspect and adapt continuously
  • It is Scrum‑aligned

    • Scrum events inspect delivery and outcomes
    • They do not replace upstream decision‑making
    • They become lighter because clarity already exists
  • It is realistic in an AI world

    • AI increases execution speed
    • Without constraints, it multiplies rework and risk
    • Specs provide those constraints

Why this actually increases speed

Decide once, clearly.

This isn’t about slowing down to be safe. It’s about moving faster by deciding once, clearly.

  • Less rework mid‑sprint
  • Fewer clarifying meetings
  • Fewer “wait, that’s not what we meant” moments
  • Faster onboarding for humans and AI

What we deliberately avoid

Waste we refuse

To preserve speed and reduce waste, we avoid:

  • Writing specs to compensate for unclear thinking
  • Treating urgency as an excuse to skip decisions
  • Using Scrum events as approval theater
  • Letting AI fabricate certainty
  • Starting development “to learn what the problem is”

What success looks like

Signals we’re on track

  • Fewer clarification cycles during development
  • Less rework from misaligned expectations
  • Stronger confidence at “Ready for Dev”
  • Scrum ceremonies that feel lighter, not heavier
  • Product Owners with more leverage and less noise
  • AI that accelerates delivery without eroding quality

Revisit

Read the manifesto

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.