Spec-to-Outcome Check: Does Your Workflow End at the PR?
Assess your agent harness for outcome orientation, trustable output, and continuous improvement. Extend spec-driven development through the product lifecycle.
Assess your agent harness for outcome orientation, trustable output, and continuous improvement. Extend spec-driven development through the product lifecycle.
Is Scrum still relevant when agents write the code? Yes, and more than before, provided you are willing to customize it. A companion to the Scrum Guide walking the accountabilities, events, artifacts, and values for a team running an AI-native, spec-driven lifecycle.
A companion to the Kanban Guide for Scrum Teams for AI-native product teams. What changes in your Definition of Workflow, WIP limits, flow metrics, and Scrum events once agents do the building, and what happens to scaling when the old dependencies start dissolving.
Starting numbers for active work and queues, covering solo and multiplayer spec-driven development, pod topology, flow buffers, and replenishment cadence.
AI agents write code faster than ever, but the bottleneck moved to human decision latency and review capacity. Here is the operating model that closes it: roles, rituals, and metrics.
When AI coding raises the arrival rate of pull requests, telling reviewers to work faster is the wrong move. Fix reviewability and end-to-end flow instead.