Product Quality Management Flashcards
7 cards from real Product Management practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Product Quality Management flashcards as text
A PM is evaluating whether to fix a known bug or ship the feature on schedule. Which framework helps weigh the risk of leaving a defect in production?
Answer: Risk matrix (Probability × Impact)
A risk matrix evaluates defects by multiplying the probability of harm by its impact, helping PMs make data-driven decisions about acceptable risk.
What is 'shift-left testing' in software product development?
Answer: Introducing testing earlier in the development lifecycle
Shift-left testing moves quality checks earlier (to the 'left' of the timeline), catching defects when they are cheapest to fix.
Which of the following BEST describes a 'quality gate' in a product delivery pipeline?
Answer: A checkpoint where defined quality criteria must be met before work proceeds to the next stage
A quality gate is a mandatory checkpoint in the delivery pipeline where predefined quality standards must be satisfied before the product advances.
A product team uses error budgets to manage reliability. If the error budget is exhausted, what should the team do?
Answer: Halt new feature work and focus on reliability improvements
When an error budget is depleted, teams should pause feature development and prioritize reliability work until the budget is restored.
What does 'voice of the customer' (VoC) data primarily help a PM do in quality management?
Answer: Align product quality priorities with actual customer expectations and pain points
VoC captures customer needs, expectations, and complaints, enabling PMs to prioritize quality improvements that have the highest customer impact.
Which concept describes the practice of making quality everyone's responsibility rather than solely the QA team's job?
Answer: Total Quality Management (TQM)
Total Quality Management (TQM) is a philosophy where every team member—engineering, design, PM, and beyond—shares ownership of product quality.
A PM wants to reduce the number of post-launch defects over successive releases. Which metric should they track over time?
Answer: Defect density (defects per unit of software)
Defect density tracks the number of defects relative to the size of software delivered, making it the best metric to observe quality improvement trends across releases.