You are on page 1of 5

The Facilitator’s Guide to SAFe®

Architect Sync

Purpose & Topics Purpose & Topics

Preparation
Purpose
The Architect Sync serves multiple purposes. It allows all Architects and stakeholders to Tips and Tricks
align a technical implementation to support the Solution’s Vision and make high-impact Overcoming Challenges
decisions. Architect Syncs provide transparency on the technical approach and decisions
across the entire Solution. They also give all Solution builders a view into the detailed
Solution design to determine how it may impact their work.

Topics
Architect Syncs are held as often as needed and the duration can be adjusted as needed. They
usually run on a weekly cadence with a 30 – 60-minute timebox. They are facilitated by the
Solution Train Engineer or ‘Chief Architect’ if that role exists for the Solution.
Some topics for an Architect Sync include:

• Discuss progress and impediments on current Enabler work.

• Review technical designs for feedback and adjustments.

• Socialize and discuss significant design issues and


create alignment across teams.

• Discuss technical approaches to implementing Features and Stories


and any support required by teams.

• Review the Architecture’s ability to support the long-term Solution


Vision to raise risks and adjust the Architectural Runway.

• Review Architectural Runway backlog and prioritization.


The Facilitator’s Guide to SAFe®
Architect Sync

Preparing for the Architect Sync Purpose & Topics

Preparation
Attendees will vary based on the agenda. Solution Train and certain ART members will likely
attend most sync meetings. Others participate as needed to provide input on decisions and Tips and Tricks
get feedback from the group. Overcoming Challenges

Solution Train leadership


Solution Train leadership, particularly technical roles, typically attend every meeting.
These include individuals in Solution Management and Solution Architect/Engineering.
Business Owners also participate when the agenda requires their input or for
transparency on technical direction.

ART representation
Most of the ART’s Product Management and System Architects attend every meeting for
alignment. Product Owners and certain team members may also participate as needed
to provide input and receive feedback.

Other development value streams


Architects and technical leads from outside the Solution Train may also attend to discuss
work and dependencies with other development value streams.

Development and technical leads


Other technical individuals who are not on the ARTs may provide technical expertise and
gain alignment.

Additional stakeholders
Individuals from quality, security, UX, and others may attend based on the agenda
topics.
The Facilitator’s Guide to SAFe®
Architect Sync

Facilitator preparation Purpose & Topics

Preparation
Establish the cadence and timing of the Architect Syncs, and schedule these events far
Tips and Tricks
enough to ensure key stakeholders’ attendance.
Overcoming Challenges
Invite representatives from Product/Solution Management, Business Owners, and other
stakeholders to the meeting. They can provide key inputs, and Architects can socialize
architectural needs and concerns.

Ensure the participation is right based on the agenda. Engage early with individuals new to
the sync event to help them prepare.

Decide who will facilitate each Architect Sync. Facilitation may be a shared responsibility.

Select and communicate the topics to the attendees ahead of the next sync.

Create an adjustable but reusable Architect Sync agenda template, and make sure to update
it before the upcoming sync to facilitate an organized flow of discussion.

Architect Sync attendees expectations


Come prepared with any requested information (e.g., technical risks, the
status of high-profile Enabler work).

Report any outputs back to your ART or team (e.g., new technical direction, a
change in priority or scope).
The Facilitator’s Guide to SAFe®
Architect Sync

Tips & Tricks Purpose & Topics

Preparation
Prepare by defining the goals/outcomes and end the meeting reiterating them. Connect the
outcomes to business value to align the Architects and the other stakeholders. Tips and Tricks

Overcoming Challenges
Publish the agenda early, so the right individuals know to attend and come prepared.

Make the meeting useful to participants by ensuring they receive the input they are looking
for and adjusting and refining as needed.

Get the group in the right mindset to foster an active, vocal culture of contribution.

Keep everyone focused on the current agenda as these events can quickly diverge
into other technical topics.

Have attendees use the outputs of these meetings as inputs into ART and team-level
meetings.

Align the Architect Sync events with the ART Syncs. The Architect Sync conversations can often
feed topics into the ART Sync.

Have a good facilitator, which, depending on the facilitation skills, could be someone from
Solution Architect/Engineering or one of the STE or RTEs.
The Facilitator’s Guide to SAFe®
Architect Sync

Overcoming Challenges Purpose & Topics

Preparation

Tips and Tricks

Overcoming Challenges

Potential Issues

Architect Sync turns into a


Key stakeholders will not attend The event is too long
status report to stakeholders

Ways to overcome: Ways to overcome: Ways to overcome:


Make sure to hold the meeting when Re-orient the participants around Consider adding additional
they can attend and, on occasion, the sync’s purpose and the current Architect Sync events rather than
adjust the meeting schedule to fit agenda. Facilitate it tightly. In cases making individual syncs longer. It is
their calendar. If the problem where the facilitator is a member of better to have more frequent,
persists, work with the stakeholders the Architect team, try having the focused events than large ones.
to assign a proxy that has the STE or one of the RTEs with strong
authority to make decisions on their facilitation skills run the sync. If
behalf. there is no clear technical agenda
for the next sync, cancel it.

You might also like