SAFe Architecture Flashcards
1
Q
Describe Agile Architecture
A
- Evolves systems over time while supporting the needs of current users
- Avoids overhead and delays associated with phase-gated processes
- Ensures systems always run
- Supports the continuous flow of value
- Balances intentional architecture and emergent design
2
Q
Name 6 common architecture domains
A
- Business Architecture
- Information Architecture
- Application Architecture
- Technical Architecture
- Integration Architecture
- Security Architecture
3
Q
Business Architecture
A
- focus on how business must evolve to meet strategic objectives;
- articulates business Vision and impact on Value Stream;
- identifies business change requirements that inform work in other domains
4
Q
Information Architecture
A
- Focuses on how information stores and flows support business need;
- identifies information change requirements and how data is consumed;
- designs systems that manage data storage, accuracy and flow
5
Q
Application Architecture
A
- Focuses on systems and services used directly by customers/end users;
- designs applications that support desired user experiences;
- manages evolution of application portfolio
6
Q
Technical Architecture
A
- Focuses on evolving infrastructure in alignment with business needs;
- designs hardware, network, and other systems in support of apps and data;
- manages evolution of hosting environments
7
Q
Integration Architecture
A
- Focuses on how application, systems, and services intercommunicate
- Defines common services, APIs, and messaging protocols
- Defines how messages and payloads are routed and managed
8
Q
Security Architecture
A
- Focuses on protecting access to and use of sensitive information
- Determines security requirements and design supporting policies and systems
- Designs procedures for detecting and reacting to security breaches
9
Q
What is the (general) role of Architects in Safe?
A
- Architect solutions for continuous value flow
- Participate in design and execution of the Continuous Delivery Pipeline
- Bridge communications b/t business, development & operations
- Collaborate w/ strategic suppliers to ensure shared DevOps mindset
- Automate architectural compliance checks
- Evangelize and exemplify CLAMR principles
10
Q
How can Architects impact Flow
A
- Minimum viable architecture vs big design up front
- Automated compliance checks vs architecture review boards
- Continuous collaboration vs ivory towers
- Loosely coupled systems vs monolithic systems
- Architecture as code vs architecture as documentation
- Federated architecture vs architecture silos
11
Q
How many architectural domain(s) does each architect cover in SAFe?
A
SAFe says that Architects should span multiple domains
12
Q
What is Conway’s Law?
A
- architecture mimics team structure- if teams are large/disorganized so will be the architecture- if teams are loosely coupled and agile, so will the architecture
13
Q
What is the Inverse-Conway Maneuver?
A
- define organization that promote desired architecture; organize around natural seams in the system architecture
14
Q
What do Architects do during PI Planning?
A
- Present the architecture Vision
- Elaborate on nonfunctional requirements (NFRs) and desired implementation patterns and practices
- Ensure consistency and alignment of the implementation approach in team breakouts by actively engaging with the teams during breakout sessions
- Identify and resolve risks in real time/ anticipate dependencies
- Support ROAM (resolve, own, accept, or mitigate) activity by identifying and/or owning program risks [Program-level risks]
- Participate in Management review and problem solving
15
Q
How do Architects contribute to Features and Capabilities?
A
- Identifying measurable benefits and Metrics
- Gauging architectural impact
- Determining acceptance criteria
- Defining nonfunctional requirements (NFRs)
- Participating in backlog prioritization
