SAFe Architect

Framework
SAFe

My notes from SAFe 5.0 training videos

SAFe for Architects course trainers should have the following experience:

  • Experience architecting using Agile principles
  • Experience guiding teams through implementation
  • Experience with full life-cycle delivery

SAFe Architect responsibilities:

  • Aligner l’architecture aux principes SAFe / ?
  • Développer et communiquer la vision et l’intention de l’architecture
  • Planifier la ligne d’architecture pour des livraisons réussies
  • Construire l’architecture pour livrer en continu et releaser à la demande
  • Guider et coacher les architectes et les membres d’équipe durant le PI Planning et l’exécution
  • Leadership durant la transformation Lean-Agile

1. Exemplify Agile Architecture

  • 1.1 Décrire l’architecture Agile
  • 1.2 Décrire les rôles impliqués dans l’architecture et leur collaboration
  • 1.3 Les principes SAFe liés à l’architecture

Exercice: Potential issue & Resolved issue board .

1.1 Describe Agile architecture

Agile architecture is different than traditional architecture

Agile architecture may require a significant mindset shift

Impediments to Agile architecture should be tracked

1.2 Describe SAFe Architect roles and collaborations

SAFe Enterprise Architect focus on Enterprise organization / across value streams

SAFe Solution Architect focus on Solution structure / across systems

SAFe System Architect focus on a single system

Comment Business, Information, Application, Technical, Security, … architectures affects each perspective Full stack architects ?

The three architect roles in SAFe

SAFe architect roles span common architecture domains

Full coverage across domains requires collaboration

1.3 SAFe Principles guide architecture practices

All architects should know and apply al SAFe Principles

Exercice: comment les principes s’appliquent à l’architecture et comment chacune des perspective peut mettre en oeuvre un principe SAFe-Lean Agile

2. Architecting for DevOps and Release on Demand

  • 2.1 Renforcer la culture DevOps
  • 2.2 Décrire comment la valeur est créée et circule dans le Continuous Delivery Pipeline
  • 2.3 Architecture pour et via l’exploration continue
  • 2.4 Architecture pour l’intégration continue
  • 2.5 Architecture pour le déploiement contin
  • 2.6 Architecture pour releaser à la demande

2.1 Eviter les silos

DevOps is a mindset, a culture, and a set of technical practices

Walls of confusion are a major impediment to DevOps

Architects can help steer the culture

2.2 Describe how value flows through the continuous delivery Pipeline

DevOps addresses flow through the entire Value streams

Value Stream mapping is an essential tool for identifying where DevOps practice are needed most

Achitecture significantly impacts value flow

Activity: Combien de temps passons nous le plus de temps ? Architect/Design steps. Overarchitecting / Overengineering

2.3 Architect for and facilitate Continuous exploration

Continuous Exploration aligns business and technology strategy

Architects should be actively involved un every aspect of Continuous exploration (metrics / measurement to support business&technology strategy for example)

Architects should define the minimum viable architecture required to enable continuous value flows

2.4 Continuous integration

Continuous integration ensures that quality is built in at development time

Continuous integration reuires loosely coupled architecture

2.5 Continuous deployment

Continuous deployment ensures time-yo-market objectives can always be mettre

Deployment is different from releaser

Architects often need to help to design solutions and infrastructure that enable Continuous deployment (need automation)

2.6 Architect for release on demand

Release on Demand empowers the business to control when and how features go to market

The production architecture must support a high degree of flexibility, resiliency, and telemetry

3. Aligning Architecture with business value

  • 3.1 Describe how Strategic Themes, Portfolio Canvas, and Portfolio VIsion influence architecture
  • 3.2 Explain how value streams support the Business
  • 3.3 Explain how Solution Trains and Agile release Trains deliver value

3.1 Describe how Strategic Themes, Portfolio Canvas, and Portfolio VIsion influence architecture

Strategic Themes, Portfolio Canvas and Portfolio Vision strongly influence the scope of architecture

Architects should contribute to the creation of these artifacts

Architects must be able to understand where their work fits in to the broader enterprise strategy

Learners need to understand the TTC business context

3.2 Explain how value streams support the Business

Architects manage systems that are designed to support and optimize Operational Value streams

Development Value Streams involve designing, building, testing, and deploying those systems

Learners need to understand TTC’s autonomous vehicle delivery Value Stream and how the Architecture vision supports it

3.3 Explain how Solution Trains and Agile release Trains deliver value

A Solution Train is a colection of ARTs and Suppliers that together deliver large, integrated solutions

TTC’s Autonomous Delivery Program Solution Train consists of three ARTs and two Suppliers

Learners must choose their ART and understand which parts of the operational value stream they are responsible for enabling

4. Developing Solution Vision, Solution Intent and roadmaps.

Align Solution Vision with Strategic themes and solution context

Contribute to solution intent

Manage quality with non-functional requirements and the lean quality management systems

Contribute to roadmaps

4.1 Align Solution Vision with Strategic themes and solution context

Solutions operate in specific contexts (when you have the knowledge of the context you can perform architecture)

Solution Vision must be traceable to Solution Context and Strategic themes

Architects should be able to explain how the Solution Vision supports business objectives

4.2 Contribute to solution intent

Solution intent is a shared knowledge repository

Architects need to balance fixed and variable solution intent

4.3 Manage quality with non-functional requirements and the lean quality management systems

Defining and testing NFRs is criical to managing solution quality

NFRs can exist at all levels of SAFe

Lean QMS enables more continuous delivery while maintaining high levels of compliance

4.4 Contribute to roadmaps

Solution Roadmaps inform PI roadmaps

Visibility of Enablers is critical

Enablers are often identified and managed by Architects

5. Preparing Architecture for Program Increment(PI) Planning

  • 5.1 Contribute to the Program Backlog
  • 5.2 Sequence and prioritize work un the Program Backlog
  • 5.3 Contribute to solution Pre-Pi Planning

5.1 Contribute to the Program Backlog

Architects need to understand Backlog item types and how they relate to each other

Architects need to write Enablers and contribute to other backlog items

TEMPLATE ENABLER WORKSHEET

5.2 Sequence and prioritize work un the Program Backlog

Architects can influence backlog prioritization by participating in WSJF sessions

Architects should collaborate with Product, Program, and Solution Management on capacity allocation

WSJF

5.3 Contribute to solution Pre-Pi Planning

Pre-PI planning aligns the SOlution Train to a common SOlution VIsion

Solution Architects should be prepared to present the Solution Architecture Vision to ART and Supplier stakeholders

6. Coordinating Architecture throught PI Planning

  • 6.1 Contribute to Pi Planning
  • 6.2 Contribute to Management Review and Problem-Solving
  • 6.3 Contribute to SOlution Post-PI planning

6.1 Contribute to Pi Planning

Exercice: Architectural themes, Enablers in scope and links to business features, NFRs, design patterns, tech standards, major touch points with other ARTs and Suppliers. Architects play an important role in all PI Planning events Unforseen issues and risks often surface during PI Planning that need to be resolved quickly

6.2 Contribute to Management Review and Problem-Solving

PI Planning contains built-in processes for resolving risks

Architects should help by taking responsbility for risks they know how to resolve

6.3 Contribute to SOlution Post-PI planning

Post-PI planning results in commitment to the SOlution-level plan

Avoid having to rework the plan during Post-PI Planning

7. Supporting Continuous Delivery during PI Execution

7.1 Guide architecture and Continuous Delivery througout the PI

Architects actively participate throuthout the PI Execution

Architect Syncs can help ensure that the solution is evolving as it should

7.2 Prepare for Iteration Reviews and System and Solution Demos

Iteration Reviews, System Demos, and Solution Demos provide critical feedback about how the architecture is evolving

Architects should attend these Demos

Architects need to demo their work as well (to showcase)

7.3 Relentlessly improve through Inspect and Adapt

The purpose of I&A is to facilitate relentless improvement

Architects attend and contribute to I&A

8. Supporting New Strategic themes and Value streams

8.1 Align architecture to Enterprise strategy

Enterprise strategy can change suddenly, impacting Value streams

Enterprise Architects may need to shift technology strategy significantly in response

8.2 Evolve the Solution Portfolio

Continually evolve the technology ecosystem by:

  • exploring trends in emerging technology
  • investing in valuable technology experiments
  • supporting and extending core technology assets
  • minimizing technology duplication and “shadow IT”
  • retiring technology that no longer delivers appreciable Value
  • minimizing technology licensing and support costs
  • managing the technology portfolio through mergers and acquisitions cycles

The technology ecosystem evolves constantly Enterprise Architects praticipate in investment decisions that balance many simultaneous business needs

8.3 Contribute Enable Epics to the Portfolio Kanban

Epic Hypothesis Statement TEMPLATE

Lean Business Canvas TEMPLATE

Capture large technology initiatives as Enabler Epics

Enterprise Architects often serve as Epic Owners

Enabler Epics require hypothesis statements

8.4 Coordinate across Value streams

Exercice: Systems shared / integrated across Value streams ? Comment chaque value stream pourrait évoluer différemment au cours du temps ? Qui devrait gérer la coordination ?

Coordination across Value Streams is important when they share systems and dependencies

Enterprise Architects typically collabrate with Solution Portfolio Management and the Agile Program Management Office

9. Leading as an Architect during the Lean Agile transformation

9.1 Describe how architects perform as Lean-Agile leaders

How architects influence morale and productivity. How they Enable / Inhibit autonomy, mastery… (intrinsic drives)

Architects have string influence

Architects can motivate people and teams by exemplifying Lean-Agile values

9.2 Describe how to lead the transition to Agile Architecture during a transformation

Conway Law and reverse

Successful transformations require structure and ongoing support

Architects should participate actively with transformation leadership to instill Agile Architecture values

9.3 Develop an action plan to support your organization’s transformation

Review the Potential Issues board

Review the Course Expectations board

Learners are motivated and ready to take action