Quality Assurance & Compliance Flashcards

What is the primary benefit of pair programming from a quality assurance perspective?

Answer: It provides real-time code review, catching defects as they are introduced

Pair programming acts as continuous code review, allowing two developers to catch errors immediately rather than discovering them later in a formal review cycle.

Which agile practice uses short feedback loops from actual users to validate whether a feature delivers value?

Answer: Frequent releases and user feedback cycles

Releasing frequently and gathering real user feedback validates whether built features actually deliver value, closing the loop between assumptions and reality.

A new regulatory requirement emerges mid-project. How should an agile team handle it?

Answer: Add it to the product backlog, prioritize with the Product Owner, and incorporate it into upcoming sprints

Agile's adaptive nature means new requirements, including regulatory ones, are added to the backlog and prioritized collaboratively for inclusion in future iterations.

What distinguishes verification from validation in agile quality assurance?

Answer: Verification checks if the product works as designed; validation checks if it meets user needs

Verification confirms the product was built correctly according to specifications, while validation confirms the right product was built to satisfy actual user needs.

How does a team's Definition of Done differ from acceptance criteria on a user story?

Answer: The DoD applies to every increment team-wide; acceptance criteria are story-specific conditions

The Definition of Done is a team-wide quality standard applied to all work, while acceptance criteria are story-specific conditions defined by the Product Owner for individual backlog items.

Which technique helps agile teams identify the root cause of a recurring defect rather than just fixing the symptom?

Answer: Five Whys analysis

The Five Whys technique iteratively asks 'why' to drill down from a symptom to its underlying root cause, enabling permanent rather than symptomatic fixes.

In an agile context, what is the role of automated regression testing?

Answer: To ensure previously working functionality remains intact as new code is added

Automated regression tests provide a safety net that confirms existing functionality is not broken by new changes, enabling teams to move fast with confidence.