CAD Agile Principles and Mindset 3 — Questions and Answers
Question 1: What is meant by 'sustainable pace' in Agile development?
- Releasing software at a pace that satisfies market demand
- The ability to maintain a constant development speed indefinitely without burnout (Correct answer)
- Slowing down development to reduce defects
- Matching competitor release cadences
Correct answer: The ability to maintain a constant development speed indefinitely without burnout
Agile Principle 8 states that sponsors, developers, and users should maintain a constant pace indefinitely, preventing team burnout and degraded quality.
Question 2: Which Agile principle directly supports DevOps collaboration between developers and business stakeholders?
- Business people and developers must work together daily throughout the project (Correct answer)
- The best architectures emerge from self-organizing teams
- Deliver working software frequently
- Technical excellence enhances agility
Correct answer: Business people and developers must work together daily throughout the project
Agile Principle 4 mandates daily collaboration between business people and developers throughout the entire project, which is foundational to DevOps culture.
Question 3: How does the Agile Manifesto treat processes and tools relative to individuals and interactions?
- Processes and tools are more important than individuals
- Processes and tools and individuals are equally important
- Individuals and interactions are valued more, though processes and tools still matter (Correct answer)
- Processes and tools are irrelevant in Agile teams
Correct answer: Individuals and interactions are valued more, though processes and tools still matter
The Manifesto values individuals and interactions over processes and tools, meaning both have value but human collaboration takes precedence.
Question 4: A product owner wants to add a feature that conflicts with the team's current technical architecture. What should an Agile team do?
- Refuse the feature to protect the architecture
- Implement the feature without considering architectural impact
- Discuss the trade-off transparently and find a solution that balances value and technical health (Correct answer)
- Defer the feature indefinitely until the architecture is refactored
Correct answer: Discuss the trade-off transparently and find a solution that balances value and technical health
Agile teams balance delivering business value with technical excellence through transparent dialogue, not unilateral decisions.
Question 5: Which concept best describes an Agile team's relationship with its work environment and processes?
- The team follows predefined processes set by senior management
- The team regularly reflects on how to become more effective and adjusts accordingly (Correct answer)
- The team waits for external audits to identify process improvements
- The team adopts industry-standard processes without modification
Correct answer: The team regularly reflects on how to become more effective and adjusts accordingly
Agile Principle 12 directs teams to regularly reflect on their effectiveness and tune their behavior accordingly through retrospectives.
Question 6: In the Agile mindset, what role does trust play between business stakeholders and the development team?
- Trust is unnecessary if contracts clearly define deliverables
- Trust is built by giving business stakeholders direct control over technical decisions
- Trust is foundational and built through transparency, collaboration, and frequent delivery (Correct answer)
- Trust is assumed from the start and never needs to be actively maintained
Correct answer: Trust is foundational and built through transparency, collaboration, and frequent delivery
Agile builds trust through consistent delivery, transparency, and close collaboration, rather than relying on contracts or assumptions.
Question 7: What distinguishes an Agile mindset from a traditional project management mindset regarding requirements?
- Agile freezes requirements at project kickoff to prevent scope creep
- Agile treats requirements as living artifacts that evolve through feedback (Correct answer)
- Agile eliminates all formal requirements documentation
- Agile requires customer sign-off on every requirement before development begins
Correct answer: Agile treats requirements as living artifacts that evolve through feedback
Agile embraces evolving requirements as normal and beneficial, using feedback loops and iterative development to refine what gets built.
CAD Agile Principles and Mindset 3
What is meant by 'sustainable pace' in Agile development?