CDA Enterprise Agile Scaling 2 — Questions and Answers
Question 1: In DA, what is the primary purpose of a 'Team of Teams' structure when scaling agile across an enterprise?
- To eliminate the need for individual team retrospectives
- To coordinate dependencies and align multiple agile teams toward shared enterprise goals (Correct answer)
- To replace traditional program management with self-organizing chaos
- To ensure all teams use identical agile frameworks and ceremonies
Correct answer: To coordinate dependencies and align multiple agile teams toward shared enterprise goals
A Team of Teams structure in DA coordinates multiple agile teams, managing cross-team dependencies and aligning efforts toward common enterprise objectives.
Question 2: Which DA scaling tactic involves sending team members from one team to temporarily join another team to transfer knowledge?
- Scrum of Scrums
- Communities of Practice
- Ambassadors (Correct answer)
- Release Train Engineering
Correct answer: Ambassadors
In DA, Ambassadors are team members who temporarily join another team to share knowledge, facilitate collaboration, and reduce inter-team dependencies.
Question 3: When applying DA at enterprise scale, how does the 'Coordinate Activities' process blade address inter-team dependencies?
- By mandating that all teams work on the same backlog simultaneously
- By providing lightweight coordination mechanisms tailored to the context (Correct answer)
- By requiring a dedicated dependency management team for every project
- By eliminating dependencies through strict team autonomy rules
Correct answer: By providing lightweight coordination mechanisms tailored to the context
DA's Coordinate Activities blade offers context-sensitive, lightweight coordination options rather than prescribing a single dependency management approach.
Question 4: In enterprise agile scaling with DA, what role does the 'Architecture Owner' play at the program or portfolio level?
- Approving every technical decision made by individual teams
- Guiding technical strategy and ensuring architectural coherence across teams (Correct answer)
- Writing all user stories related to technical infrastructure
- Replacing the enterprise architect role entirely
Correct answer: Guiding technical strategy and ensuring architectural coherence across teams
At program or portfolio level, the Architecture Owner guides overall technical strategy and ensures teams maintain architectural coherence without becoming a bottleneck.
Question 5: Which of the following best describes the DA concept of 'Guided Continuous Improvement' (GCI) in an enterprise scaling context?
- A prescriptive improvement framework imposed top-down on all teams
- A structured coaching approach helping teams evolve their WoW over time (Correct answer)
- An automated tool suite that identifies and fixes process inefficiencies
- A one-time transformation program with a fixed end date
Correct answer: A structured coaching approach helping teams evolve their WoW over time
GCI in DA is a structured coaching strategy where improvement coaches help teams experiment with and evolve their Way of Working continuously over time.
Question 6: In a DA enterprise scaling scenario, what is the key difference between a 'Release Train' and a 'Solution Train'?
- Release Trains are used in SAFe only, while Solution Trains are exclusive to DA
- Release Trains coordinate a program increment; Solution Trains coordinate multiple Release Trains for large solutions (Correct answer)
- Solution Trains focus on software delivery, while Release Trains handle hardware
- Release Trains require PI Planning, while Solution Trains use only Kanban boards
Correct answer: Release Trains coordinate a program increment; Solution Trains coordinate multiple Release Trains for large solutions
A Solution Train coordinates multiple Agile Release Trains working together on very large, complex solutions that a single program increment cannot deliver alone.
Question 7: When an enterprise is scaling DA across geographically distributed teams, which strategy is most aligned with DA's principle of 'enterprise awareness'?
- Requiring all distributed teams to work in the same time zone to ease coordination
- Choosing coordination mechanisms that respect local context while maintaining enterprise alignment (Correct answer)
- Centralizing all decision-making at headquarters to reduce coordination complexity
- Standardizing one agile framework for all locations regardless of local conditions
Correct answer: Choosing coordination mechanisms that respect local context while maintaining enterprise alignment
DA's enterprise awareness principle means distributed teams select coordination strategies that fit their local context while still contributing to overall enterprise goals.
In DA, what is the primary purpose of a 'Team of Teams' structure when scaling agile across an enterprise?