Acceptance criteria are measurable conditions that define what success looks like for a platform change. They guide design, expose misunderstandings before implementation, and provide a basis for evaluating results. section 2.2.1
Use acceptance criteria throughout the delivery lifecycle:
- Define them during planning so work aligns with the platform roadmap, dependencies, incremental delivery, and priorities. section 2.2.1
- Address them during design alongside architectural challenges, experiments, and evidence about usage and effectiveness. section 2.2.1
- Turn them into automated tests before development, reducing misunderstanding and confirmation bias. section 2.2.1
- Verify them through the automated pipeline across environments, integrations, functional tests, and end-to-end tests. section 2.2.1
Incremental platform capability
For a new platform capability, define measurable success conditions, release a small experiment, gather usage and effectiveness data, and expand only when the evidence supports sustained implementation. section 2.2.1
Figure 2.7 The software delivery lifecycle covers all stages from feature planning through running in production.
Use the lifecycle figure to trace acceptance criteria from planning and design through testing and production. section 2.2.1
