Methodology · From need to evidence

An engineering methodology for working with AI without losing judgment, control or traceability.

DCP Flow combines adapted Scrum practices, Solution Discovery, architecture, AI agents, Quality Gates, Evidence and Human Gates. It does not copy Scrum; it reuses useful components inside a broader system focused on verifiable decisions.

DCP FLOW · PROCESS MAP

From problem to evidence

Follow the end-to-end cycle. Human Gates apply according to risk.

6 STEPS
01 / 06
Problem

Define the problem and constraints before selecting tools.

INTERACTIVE LAB · 01

Discover before you build

Try four scenarios or shape your own. Changing a condition recalculates candidate paths, trade-offs and missing evidence.

Shape the scenario

FIRST PATH TO INVESTIGATECONFIGURE

Scenario factors

    Compare alternatives

      Risks and dependencies

        Evidence still needed

          Educational simulation: the relative index is not a probability, TCO or normative verdict. The Solution Discovery Gate governs decision modes; validate actual products, licensing, costs, Golden Flow and ADR before the Human Gate.

          Scrum → DCP Flow

          What we take from Scrum and how we reuse it

          DCP Flow preserves iteration, backlog, prioritization, sprints, review and continuous improvement. It reduces ceremonies and rigid roles when they add little value and reframes the sprint as a contract for a verifiable outcome.

          01

          Backlog

          Kept as an explicit prioritized work list, but connected to Project Truth, risk, discovery and architecture decisions.

          02

          Sprint

          Not only a time box: a bounded commitment to one or more verifiable outcomes, expected evidence and explicit limits.

          03

          Sprint Planning

          Reused as outcome preparation: scope, dependencies, risk, Golden Flows, involved agents and Definition of Done.

          04

          Daily / synchronization

          A daily ceremony is not mandatory. Coordination is proportional to team and risk, especially with multiple agents or humans.

          05

          Review

          Becomes Human Review supported by evidence: the result is checked against outcome, Golden Flows, Quality Gates and the real artifact.

          06

          Retrospective

          Expanded into Lesson Learned: what worked, what failed, what stays local and what may evolve Standards, Blueprints, Skills or Gates.

          07

          Roles

          Scrum roles are not copied by dogma. DCP Flow distinguishes Human Owner/Reviewer, Kai, Execution Agents and technical responsibility by context.

          08

          Increment

          The increment must be demonstrable. Code, docs or config count as progress only with evidence proportional to risk.

          Beyond Scrum

          Principles that extend Scrum inside DCP Flow

          Discovery before execution

          Before BUILD, SaaS, OSS and components are investigated; coding is not the automatic first answer.

          Architecture & Project Truth

          Work does not start from isolated tickets: it starts from context, ADRs, Blueprint, repository truth and boundaries.

          AI-native with governance

          Kai and agents accelerate work, but technical capability does not equal operational authorization.

          Quality Gates + Evidence

          “Done” is not enough. Outcomes require checks, artifacts, browser/runtime evidence and Human Acceptance when applicable.

          DCP Flow

          The DCP Flow journey

          01

          Problem

          Understand the need before choosing technology.

          02

          Capabilities

          Define what the solution must be able to do.

          03

          Discovery

          Compare SaaS, OSS, components and real alternatives.

          04

          Decision

          ADOPT / CONFIGURE / INTEGRATE / EXTEND / BUILD with evidence.

          05

          Architecture

          Choose structure, stack, boundaries and risks.

          06

          Sprint

          Turn the objective into verifiable outcomes.

          07

          Execution

          Humans, Kai and agents work with shared context.

          08

          Quality Gate

          Evidence determines whether progress is allowed.

          09

          Learning

          Lessons can remain local or evolve DCP Flow.

          Discovery Gate

          Solution Discovery before BUILD

          The first response is not to code. DCP Flow requires investigating what exists, testing candidates and measuring GAP before justifying custom development.

          ADOPT

          Use an existing solution when it reasonably meets the outcome.

          CONFIGURE

          Solve through supported configuration rather than reflexive coding.

          INTEGRATE

          Connect existing systems or capabilities through explicit contracts.

          EXTEND

          Expand a platform using supported extension points.

          BUILD

          Build custom software when evidence justifies doing so.

          Kai supporting architecture analysis within DCP Flow
          Kai supporting architecture analysis within DCP Flow

          Kai · Architecture context

          Kai supports context, not replaces architecture

          Kai can help read the project, connect prior decisions, analyze repositories and infrastructure, and prepare handoffs. Architecture remains a traceable DCP Flow decision and stays subject to Human Gates.

          Evidence

          Quality Gates: evidence before confidence

          A change is not ready because an agent says it works. It is ready when sufficient evidence exists for the risk level and relevant Golden Flow.

          KKai recommended pathContinue with Solution Discovery01 → 03 → 06 → 12