Decision-Driven Delivery
Govern software through decisions, not tasks.
An open framework for software development in the age of AI.
Read the guide01
The Cycle
Every decision moves through five modes — not sequentially, but at the speed it needs.
01Explore— Investigate the solution space
02Decide— Choose deliberately, document
03Execute— Build with focus
04Validate— Measure outcome against decision
05Learn— Feed insights back
02
The Decision Map
A table that shows what still needs to be decided — and where each decision currently stands.
| Entscheidung | Owner | Explore | Decide | Execute | Validate | Learn |
|---|---|---|---|---|---|---|
| Auth solution? | Schmidt | ✓ | ✓ | ● | ||
| Cloud provider? | Yilmaz | ✓ | ● | |||
| Data migration? | — | ● | ||||
| API versioning? | Weber | ✓ | ✓ | ✓ | ✓ | ● |
● aktuelle Phase✓ abgeschlossen— kein Owner
03
Your Decision Map
Try it.
Enter the most important open decisions in your current project. Not tasks. Not features. Decisions.
Examples
01
02
03
From Scrum to D³
What you know — what changes.
Working with Scrum? You know these concepts. D³ doesn't replace them — it shifts focus from tasks to decisions.
Sprint Planning
→
Map Review
Mondays · 30 min
Sprint Review
→
Validation Review
Fridays · 45 min
Daily Standup
→
Optional
Triage as needed
Retrospective
→
Integrated into Learn mode
Product Backlog
→
Decision Map
User Stories
→
Decision Records
Sprint
→
Decision Cycle
The Roles
You have your first Decision Map. The Guide shows what comes next.
Start Monday
Quick Start, Decision Record template, rituals, metrics, migrating from Scrum.
Read the introduction
The full article — for everyone who governs software