Day-to-Day – System Architect
Similar to Product Management, the System Architect is also looking ahead as well as keeping abreast of the current execution of the ART.
ART Events and the System Architect
Let’s look at some of the ART events the System Architect attends or facilitates.
The System Architect and PI Planning
The System Architect has a key role in the PI Planning Event – that is, preparing and sharing the architecture vision briefing. The System Architect is a key individual at Management Review and Problem Solving and influences the Business Owner in estimating Business Value and plan acceptance.
The System Architect and ART Sync
At the ART Sync, the System Architect is an active participant and helps address and remove any impediments and discusses opportunities with Feature and Enabler development. It’s also a good opportunity to review quality metrics.
Pro tip
While SAFe® doesn’t identify a Technical Sync, I have found that, in the same fashion, there is a Coach Sync (formerly the Scrum of Scrums) and a PO Sync, and that teams often have a technical leader, often in an unofficial capacity. I have had success in formalizing that role and establishing a Technical Sync that the System Architect leads, just as the RTE or Product Management would lead the Coach Sync or PO Sync, respectively.
This creates a similar and scalable context for sharing information regarding technical challenges in the teams, architectural design patterns, infrastructure discussions, and so on. The System Architect has a daunting role in keeping abreast of constantly changing technology, security threats, compliance needs, and performance demands.
If your ART decides to hold a Technical Sync, make sure you invite the RTE.
The System Architect and Iteration System Demos
At the Iteration System Demos, the System Architect can see the collective progress as they likely aren’t able to attend every team’s itineration demo. The System Architect will often use this opportunity to ask questions of the teams regarding technical practices and progress on Enablers.
The System Architect and Inspect & Adapt (I&A)
The System Architect actively participates in the PI System Demo and will often compliment Product Management and share some of the technical underpinnings of the system that have been developed. It is important for the System Architect to actively participate in the quantitative and qualitative measurement and retrospective and problem-solving workshops.
Pro tip
As a Coach, it is important to ensure that the System Architect is engaged daily with the ART. This includes actively attending and participating in the ART events.
In my experience, System Architects tend to be a bit introverted and likely don’t understand the full expectations of the role and will benefit from some extra knee-to-knee guidance and Coaching.
Ongoing Activities for the System Architect
In addition to supporting the ART in the various events, the System Architect has five key areas of responsibility:
Figure 7.4 – System Architect responsibilities (© Scaled Agile, Inc.)
The System Architect stays very busy and is constantly working with the teams and organization to deliver quality solutions.
While being embedded in to aligning architecture with business priorities and fostering Built-in Quality and attending to NFRs, the System Architect needs to continually refine the ART Backlog in conjunction with Product Management. They may need to work closely with the Product Owners to decompose both business and Enabler Features into consumable stories for the teams.
Pro tip
As a Coach, encourage the System Architect to set aside dedicated time each week to work on the backlog. Most System Architects need at least 3 to 4 dedicated hours per iteration to stay ahead of the ART. Often, the System Architect and Product Management will set aside time together every iteration to work on the backlog together in addition to independent work.
