Accountabilities and boundaries
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
be explicit about what the architect owns and what they do not.
Planned topics
- Accountable for: the solution design's fitness, options and recommendations, decision log, architectural risks, quality attribute coverage.
- Not accountable for: business priorities and budget (sponsor), enterprise standards (EA), delivery schedule (project manager), code quality inside a team (tech lead).
- Write decision rights down: who recommends, who decides, who is consulted.
- Boundaries prevent both gaps and turf wars.
Draft outline details
Demonstration
a short decision-rights table (RACI style) for three Larkspur decisions: choose the commerce platform, choose the payment provider, approve a one-off exception to the API standard.
Check your understanding
Who decides the program budget?
Show answer
The sponsor or business owner; the architect advises on cost implications.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.