Agile Principles and Mindset Flashcards
7 cards from real CAD 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 Principles and Mindset flashcards as text
Which Agile principle underpins practices like Test-Driven Development (TDD) and refactoring?
Answer: Continuous attention to technical excellence and good design enhances agility
Agile Principle 9 emphasizes continuous attention to technical excellence and good design, which directly motivates practices like TDD and refactoring.
A newly formed Agile team has a detailed process manual from a previous project. How should they approach it?
Answer: Use it as a starting point but adapt it through retrospectives based on their own context
Agile values adapting processes to context; teams should inspect and adapt rather than blindly following or discarding prior work.
What is the significance of the Agile principle that states 'the best architectures emerge from self-organizing teams'?
Answer: Teams that control their own work produce better technical outcomes than top-down design
Agile Principle 11 recognizes that teams empowered to make their own technical decisions generate better architectures than those imposed from above.
How does Agile define 'done' in terms of working software?
Answer: Software that meets the team's agreed Definition of Done and delivers real user value
In Agile, 'done' means software that meets the shared Definition of Done, ensuring it is truly complete and ready to deliver value to users.
A manager insists on attending every Agile team ceremony to ensure control. How does this conflict with Agile principles?
Answer: It undermines team self-organization and can reduce psychological safety
Excessive management presence can inhibit self-organization and open communication, contradicting Agile's principle of empowering motivated individuals.
Which scenario best demonstrates the Agile principle of 'customer collaboration over contract negotiation'?
Answer: The team and customer co-create user stories and review working software together regularly
Customer collaboration means ongoing joint work — building together, reviewing frequently — rather than negotiating terms through formal contracts.
In an Agile context, what is the primary measure of project progress?
Answer: Amount of working software delivered that meets user needs
Agile Principle 7 explicitly states that working software is the primary measure of progress, not plans, stories, or logged hours.