Scaling Agile Frameworks Flashcards
7 cards from real DAC practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Scaling Agile Frameworks flashcards as text
In the DA toolkit, the 'Lean Portfolio Management' process blade is analogous to which SAFe competency?
Answer: Lean Portfolio Management (LPM)
DA's Lean Portfolio Management process blade and SAFe's Lean Portfolio Management competency both address investment funding, prioritization, and governance at the portfolio level.
A scaled agile team struggles with 'Integration Hell' at the end of each sprint. Which DA practice most directly addresses this problem?
Answer: Applying Continuous Integration (CI) to merge and test code multiple times per day
Continuous Integration (CI) eliminates integration hell by merging and validating code frequently, catching conflicts early rather than accumulating them.
What does the concept of 'Economic Framework' mean in the context of SAFe and DA scaled agile?
Answer: A set of financial guardrails and decision rules that guide decentralized economic decision-making
An Economic Framework provides guardrails — including cost of delay, resource constraints, and investment priorities — that enable teams to make fast, decentralized decisions aligned with business value.
In a scaled DA environment, which technique helps teams visualize and manage the flow of work across multiple teams simultaneously?
Answer: A scaled Program Board or dependency map showing cross-team work and blockers
A Program Board or scaled dependency map makes cross-team work, dependencies, and risks visible, enabling proactive coordination across multiple teams.
When should a DAC practitioner recommend that an organization NOT adopt a formal scaling framework like SAFe or LeSS?
Answer: When only 2-3 teams are collaborating and lightweight coordination suffices
DA's context-sensitive guidance recognizes that small numbers of teams often need only lightweight coordination, and heavyweight frameworks add unnecessary overhead.
In LeSS Huge (for very large-scale adoption), what role is introduced that does not exist in basic LeSS?
Answer: Area Product Owner
LeSS Huge introduces Area Product Owners who are responsible for a subset of the product's feature areas, supporting the overall Product Owner when teams number in the dozens.
According to DA's scaling guidance, what is the recommended approach when two teams have conflicting priorities due to shared dependencies?
Answer: Use a collaborative prioritization session involving both teams and stakeholders to align on value
DA recommends collaborative prioritization involving relevant teams and stakeholders to resolve dependency conflicts based on overall value and organizational goals.