For Scrum teams working with AI coding agents

AI writes code. Your team owns delivery.

Bring AI-generated changes into one workflow. Developers review the design and the code; the Product Owner verifies the result against agreed criteria.

Book a demoSee how it works
CRM-07142 06 accept · waiting for youHuman approval at 4 of 6 stagesBudget reserved before every model callOne branch and one pull request per change

Your team stays in charge of every change.

Find your role

Fig. 1 — The console's inbox: what waits for you, with its evidence and its cost.

More AI-generated code means more work to verify.

AI agents can produce changes quickly. Teams still need to agree on requirements, review technical decisions, check the implementation and verify the result. Under deadline pressure, keeping those steps consistent becomes harder.

Dekku connects them in one workflow. Each change carries its specification, its check results and its approval history, so your team can see what is ready and what still needs attention.

Design review and acceptance stay required, even under deadline pressure.

One workflow connecting requirements, code and decisions.

SpecificationAn approved specification gives agents and reviewers a shared reference.
ChecksA failed check holds the change until something it reads changes and the check passes.
Acceptance evidenceTests and screenshots are linked to each acceptance criterion.
Approval historyEvery approval names the person, the stage and the version they reviewed.
Changed requirementsChanges to the specification or its acceptance criteria require approval again.

Six stages. Who does what, and who decides.

  1. 01

    Spec

    Define the expected behavior and acceptance criteria. The Product Owner approves the specification.

  2. 02

    Design

    Review the technical approach. The architect approves the design.

  3. 03

    Build

    AI agents write the code and tests against the approved specification and design.

  4. 04

    Integrate

    Your test suite and the checks you require run on the change. A failed check blocks progress until its relevant inputs change and the check passes.

  5. 05

    Review

    A developer reviews the code and approves it or requests changes.

  6. 06

    Accept

    The Product Owner reviews the result and its evidence against the agreed criteria.

Sent back at any stage, a change returns with the reviewer's note, and the next attempt starts from it.

Ask for a change. Approve the result.

Questions teams ask first.

How does Dekku keep our backlog updated?

Each change is one backlog item. Dekku keeps the linked Jira item updated and marks it Done when the approved, checked change is merged.

How do acceptance criteria relate to our Definition of Done?

Acceptance criteria describe the expected behavior of a specific change. Your Definition of Done sets the quality standards that apply across changes. Dekku enforces the configured checks and approvals; your team remains responsible for making sure they cover its Definition of Done.

What happens when a change needs rework?

A reviewer requests changes with a note, and the agent's next attempt starts from it. A failed check blocks progress until something it reads changes, such as the code, the tests or the configuration, and the check passes.

Who can approve each stage?

Your project's policy assigns each approval to a role, for example the design to the architect, and Dekku enforces it. In a one-person setup, that person holds every role.

What work stays with our team?

Your team defines requirements, approves technical decisions, reviews code and verifies results. AI agents write the code within that workflow.

Where does Dekku run?

On your own infrastructure, from one laptop to a team server. You manage code storage, logs and credentials, and connect AI models through your organization's own account.

See how Dekku handles a change from your backlog.

Bring a backlog item to the demo. We'll walk through its specification, technical reviews, checks and acceptance, showing what each person sees and decides.

A walkthrough with the people who build Dekku.