BUILD & CONNECT
Agentic delivery lifecycle
Move from discovery and requirements to review, release and learning.
Overview
A reliable delivery lifecycle covers discovery and requirements as well as implementation. Documents, diagrams, tests and other artefacts are part of the deliverable and should be reviewed with the same care as code.
Discover
Clarify the business outcome, users, constraints, risks and existing process. Keep open questions visible.
Specify
Create acceptance criteria, architecture decisions, data boundaries and a plan for testing and rollback.
Build
Produce the necessary implementation and supporting artefacts in a controlled workspace with traceable changes.
Verify
Run relevant automated checks and human review. Test security, accessibility, responsive layouts and failure cases as appropriate.
Review and release
Use the repository’s change controls, approvals and deployment process. Do not assume a merge means a production deployment succeeded.
Learn
Monitor the result, capture feedback and defects, assign follow-up work and update documentation when behaviour changes.
Worked example
A release with evidence
Treat the implementation, supporting artefacts and operational hand-off as one deliverable.
- 1Agree the business outcome, constraints and measurable acceptance criteria.
- 2Specify architecture, data boundaries, tests and rollback expectations.
- 3Implement in a controlled branch with traceable changes.
- 4Run the relevant automated checks and human review, including security and accessibility where appropriate.
- 5Release through the repository's normal controls, verify the deployed result, and update affected guides.
Was this guide useful?
Send feedback or flag a gap. Include the article link so the team can improve the right guide.