Who does what
Whoever Defines It, Tests It
The Definers, and the gates to ship
When AI does the building, the team is made of Definers. Each one sets what "right" means for their part, and tests the result against it. No one tests against someone else's definition.
| Definer | Defines | Tests | Before AfterAgile™ |
|---|---|---|---|
| CX | The customer need – the what and the why. Identifies the most pressing customer challenge. | Does it meet the need, on the customer's best day and their worst? | Filed tickets, and gathered feedback after launch |
| Product | Commercial viability – why now, the market, and the money | Is it viable, and did it move the number the business was promised? | Managed the backlog, wrote tickets, negotiated story points |
| UX | The brand, the UI and the workflow | Does it look, feel and flow right, on every device? | Drew screens and handed them off |
Engineering keeps the build sound – architecture, security, data, integrations and the release safety net. The Reviewers own the business outcome.
Everyone Can Build. Not Everyone Can Ship.
Prototypes should be free, fast and encouraged. Anyone can build one to ask, "Is this what we mean?" The path to production is different. It has gates.
Clear Ownership
Every area of the product has a named Definer who approves changes to it.
Definer Review
Each Definer tests against their own definition. Engineering reads what's merging.
The Intent Check
Does this do what the Intent says, and only that?
Automated Gates
Tests, accessibility scans, performance budgets and security checks, run by the Pipeline.