Quality Assurance & Compliance Flashcards
7 cards from real ICP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Quality Assurance & Compliance flashcards as text
In agile, who is primarily responsible for ensuring the quality of the product increment?
Answer: The entire cross-functional team
In agile, quality is a shared responsibility of the entire cross-functional team, not delegated to a separate QA function.
What is the purpose of a Definition of Done (DoD) in agile quality assurance?
Answer: To provide a shared checklist confirming an increment is truly complete
The Definition of Done establishes a shared, transparent checklist that an increment must meet before it is considered complete and potentially shippable.
Which testing practice involves writing tests before writing the production code?
Answer: Test-Driven Development (TDD)
Test-Driven Development (TDD) requires writing a failing test first, then writing just enough production code to make it pass.
How does continuous integration (CI) support agile quality practices?
Answer: It automatically builds and tests code on every commit to detect integration issues early
Continuous integration automatically runs builds and tests whenever code is committed, surfacing integration defects quickly rather than at the end of a sprint.
A team consistently delivers features that pass acceptance criteria but customers are still dissatisfied. What is the most likely root cause?
Answer: The acceptance criteria do not accurately capture the customers' real needs
If acceptance criteria do not reflect true customer needs, passing those criteria will not produce satisfaction — the criteria themselves are flawed.
What does 'shift left' mean in the context of agile quality?
Answer: Bringing testing and quality activities earlier in the development process
Shifting left means integrating testing and quality checks earlier in the lifecycle so defects are caught when they are cheapest to fix.
In regulated industries, how should agile teams handle compliance documentation?
Answer: Create compliance artifacts as a natural by-product of their agile workflow, not as a separate phase
Agile teams in regulated environments integrate compliance evidence into their workflow so documentation emerges continuously rather than being produced in a costly batch.