Open Agile Architecture Practitioner flashcards
Open Agile Architecture Practitioner · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Open Agile Architecture
- An Open Group standard that reframes enterprise architecture as a continuous, product-centric discipline blending Agile delivery with lightweight, outcome-focused architecture governance.
- Agile Architecture
- The half of the O-AA body of knowledge covering practices such as architecture runway, intentional and emergent design, decision-making, and architecture as code.
- Agile Organization
- The half of the O-AA body of knowledge covering operating-model transformation, autonomous teams, team topologies, and organizing around value.
- Intentional architecture
- Deliberate, high-level structural decisions made early, typically for irreversible or high-impact choices that affect many teams and are costly to change later.
- Emergent design
- Architecture structure that evolves through delivery feedback and refactoring, suited to reversible, local decisions where teams can adapt quickly.
- Fitness function
- An automated or repeatable check that verifies an architectural characteristic such as performance, security, or modularity remains intact as the system evolves.
- Architecture runway
- A time-boxed, demand-driven backlog of architecture work needed to keep delivery teams unblocked for the next few iterations.
- Architecture as code
- Expressing architecture decisions, models, and constraints as versioned artifacts stored in the same repository and pipeline as software.
- Architecture decision record
- A lightweight, versioned record capturing the context, decision, and consequences of an architecture choice, owned by the deciding team.
- Value stream
- The end-to-end flow of value to the customer; the primary unit for aligning strategy, architecture, and delivery in O-AA.
- OKRs
- Objectives and key results that connect enterprise outcomes to team-level objectives, justifying architecture work by the outcomes it enables.
- Organizing around value
- Structuring teams by value stream or product rather than by functional silo or technology layer, enabling continuous flow.
- Team topologies
- A model of stream-aligned, platform, enabling, and complicated-subsystem teams with defined interaction modes that reduce cognitive load.
- Autonomous teams
- Cross-functional teams that own their architecture decisions within guardrails, supported by architects who coach and enable rather than approve.
- Guardrails
- Testable principles and standards that enable decentralized decisions while keeping architecture aligned; they replace stage-gate approvals.
- Agile governance
- Lightweight, outcome-focused governance using principles and guardrails, with decisions decentralized to the lowest competent level.
- Evolutionary architecture
- Designing for change through decoupled components, fitness functions, and avoidance of irreversible big-bang decisions.
- Continuous delivery
- CI/CD, automated testing, and trunk-based development practices that are architectural enablers supporting deployability.
- Platform team
- A team providing self-service capabilities that reduce duplicated effort and cognitive load for stream-aligned delivery teams.
- Outcome-based roadmap
- A roadmap organized around outcomes and value rather than feature lists or fixed project timelines.
- Product over project
- An O-AA principle favoring persistent, value-stream-funded product teams over temporary project structures that cause stop-start delivery.
- Customer-centricity
- An O-AA theme prioritizing customer outcomes and value flow as the basis for strategy, architecture, and delivery decisions.
- Systems thinking
- A practitioner competency for understanding interconnections across value streams, teams, and technology rather than optimizing isolated parts.
- Architect as enabler
- The O-AA shift from gatekeeper approving designs to coach and facilitator who builds guardrails and helps teams decide.
- Decision forum
- A lightweight, collaborative session where cross-team architecture decisions are facilitated and recorded as ADRs.
- Review board bottleneck
- An anti-pattern where periodic architecture approvals slow delivery; avoided by decentralizing decisions with guardrails.
- Big upfront design
- An anti-pattern of complete target-state blueprints before delivery; O-AA replaces it with just-enough intentional architecture plus emergent design.
- Ivory-tower architect
- An anti-pattern of architects disconnected from delivery; avoided by embedding architects in teams and shifting to coaching.
- Stale documentation
- An anti-pattern of unmaintained architecture documents; avoided by treating architecture as code and keeping ADRs with the codebase.
- Value-stream funding
- Funding persistent value streams or products rather than temporary projects, enabling continuous flow and reducing stop-start delivery.
- Transformation roadmap
- A sequenced plan of operating-model changes in structure, governance, funding, and culture alongside technology changes, iterated continuously.
- Reversibility test
- A decision rule: irreversible, high-cost choices get intentional architecture treatment; reversible, local choices emerge through delivery.