Architecture decision record
One decision about the design of the system or service: its context, the options considered, what was decided, its consequences and its safety and compliance impact. Started in the project, it moves with the product at handover and stays current for the life of the product.
Why it matters
Decisions made in a project shape a live system for years. If the reasons are lost at handover, the product team repeats old mistakes or undoes safety controls.
- Owner
- Technical and Integration Lead
- PRINCE2
- Specialist product; Design Authority decisions, handed over with the products
- ITIL
- Architecture management; service design
Draws on
Led or owned by
In the resource library
Ready-to-use resources in the DelPulse workspace (sign in to open them):
- Technical and Integration Lead self-assessment · Self-assessments
The rest of this page is for subscribers
Subscribe to read the other 4 sections of this page:
- How to run it
- Rules
- In the DelPulse workspace
- If you use Jira or Azure DevOps