Agile & Lean Principles 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 Agile & Lean Principles flashcards as text
A team is debating whether to use Scrum or Kanban for a new product. A DAC applying DA principles would recommend:
Answer: Evaluate the team's context and choose the approach that fits best
DA's 'choice is good' and 'context counts' principles mean the right framework depends on the team's specific situation.
The Lean concept of 'muda' (waste) that most directly applies when developers build features that customers never use is:
Answer: Overproduction
Building unused features is overproduction—creating output beyond what the customer actually needs or pulls.
In DA, which agile principle justifies empowering teams to choose their own tools and practices rather than standardizing across the enterprise?
Answer: Build projects around motivated individuals and trust them
Trusting motivated individuals to choose their tools reflects the Agile principle of building projects around people and empowering them.
A DAC notices a team's Definition of Done does not include performance testing. Which DA/Lean principle does this gap most violate?
Answer: Build quality in
Excluding performance testing from DoD means quality is not built in throughout development, violating the 'build quality in' principle.
The DA 'Lean-agile mindset' characterizes failure in experiments as:
Answer: An opportunity to learn and improve the system
A Lean-agile mindset treats experimental failure as valuable learning data that informs smarter next steps.
When DA guidance says to 'prove it with working software,' this most directly reinforces which Agile Manifesto value?
Answer: Working software over comprehensive documentation
Proving value with working software directly enacts the Manifesto's prioritization of working software over documentation.
A DAC is coaching a scaled program where multiple teams feed into a shared integration environment that creates a bottleneck. The Lean principle most relevant for resolving this is:
Answer: Optimize the whole
A shared integration bottleneck is a system-level constraint, and optimizing the whole means addressing cross-team flow rather than individual team throughput.