Open Agile Architecture Practitioner study plan
Open Agile Architecture Practitioner · Give each week a clear focus.
8 weeks · About 7 hours per week
Open Agile Architecture
Map the full Open Agile Architecture body of knowledge into a one-page concept graph linking agile operating models, architecture practices, and continuous delivery
Define the core vocabulary of the framework in your own words: agile architecture, intentional versus emergent architecture, architecture runway, and the role of the architect in a product operating model
Identify how O-AA positions architecture as an enabler of business agility rather than a gatekeeping function
List the main reference models and frameworks the syllabus compares against O-AA and note one distinguishing feature of each
Your checkpoint
A one-page concept graph plus a 25-term personal glossary with your own definitions
Open Agile Architecture
Break down the O-AA structure into its layers, viewpoints, and how they interlock across strategy, portfolio, and delivery
Explain how intentional architecture and emergent design coexist and where the handoff points sit in practice
Translate the framework's principles into concrete behaviors an architect performs in a sprint cadence
Draft three short scenarios where O-AA guidance would change a decision compared with a traditional architecture method
Your checkpoint
A two-page written comparison of intentional versus emergent architecture with three worked scenarios
Open Agile Architecture
Deconstruct the agile operating model elements: value streams, teams, funding, governance, and portfolio flow
Connect architecture practices to value stream mapping and show where architecture decisions enter the flow
Analyze how lean portfolio management and continuous funding replace annual planning cycles
Identify the metrics O-AA uses to judge architecture effectiveness and explain why each matters
Your checkpoint
A value stream diagram for a fictional organization annotated with architecture decision points and metrics
Open Agile Architecture
Examine how O-AA treats governance, guardrails, and decision rights in a decentralized model
Distinguish fitness functions, architecture principles, and standards and state when to use each
Evaluate the trade-offs between centralized platform teams and federated architecture enablement
Prepare for the mid-point check by consolidating weeks one to four into a single mental model
Your checkpoint
A governance playbook of one page listing decision rights, guardrails, and escalation paths
Open Agile Architecture
Map the continuous delivery and DevOps practices O-AA expects architects to support, including automated testing and deployment pipelines
Describe how architecture runway is planned and replenished to avoid blocking delivery teams
Explain the architect's role in product lifecycle management, from discovery through retirement
Identify anti-patterns that signal architecture is becoming a bottleneck
Your checkpoint
An architecture runway plan covering two quarters with explicit replenishment triggers
Open Agile Architecture
Analyze how O-AA addresses data, technology, and application architecture domains within an agile context
Compare the framework's guidance on API and platform strategy with mainstream microservice practice
Draft architecture principles that are testable and short enough for a team to remember
Assess how security and compliance concerns are embedded rather than bolted on
Your checkpoint
A set of five testable architecture principles each paired with a fitness function
Open Agile Architecture
Synthesize the whole framework into an end-to-end narrative from strategy to running software
Practice applying O-AA to a realistic transformation scenario with conflicting stakeholder priorities
Rehearse explaining trade-offs aloud as you would in a scenario-based exam question
Review your glossary and concept graph and correct any gaps or misconceptions
Your checkpoint
A recorded ten-minute walkthrough of an O-AA adoption scenario with trade-off reasoning
Open Agile Architecture
Consolidate weak areas identified in weeks one to seven into a prioritized revision list
Answer practice scenario questions under time pressure and review each wrong answer for the underlying concept gap
Verify you can define every glossary term without notes
Finalize a one-page exam-day reference sheet of frameworks, principles, and metrics
Your checkpoint
A scored practice set with a written error analysis and a finalized one-page reference sheet
Milestones
Week 2: You can explain intentional versus emergent architecture and give one concrete example of each without notes
Week 4: You can draw the O-AA structure from memory and place governance, value streams, and decision rights correctly
Week 6: You can write a testable architecture principle and its fitness function in under five minutes
Week 8: You score at least 80 percent on a timed practice set and can define every glossary term unaided