Demo: mapping the architecture roles on the Larkspur program
On This Lesson 3 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
assign every architecture concern on the Larkspur program to the right role. Prepares ARC-001-LAB1.
Draft outline details
Step by step
- List the program's concerns: commerce platform choice, cloud landing zone, customer data model, ERP interface design, coding standards inside the web team, capability roadmap.
- Place each concern on the five-role table (software, solution, enterprise, cloud, data).
- Draw the interface list: who the solution architect talks to weekly, and what each party gives and expects.
- Write decision rights for the three biggest decisions.
- Planned mistake: assign the coding standards and the capability roadmap to the solution architect "because it is architecture". Fix: coding standards go to the team's software architect or tech lead; the roadmap to enterprise architecture.
- Review the result with a role-played sponsor for gaps and overlaps.
Check your understanding
What test quickly shows a concern is not yours?
Show answer
It sits outside the solution's scope, or the decision right is written as someone else's.
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.