Quality & Acceptance

Make quality criteria, testing evidence and acceptance decisions usable.

• The deliverable is complete, but the customer will not accept it. What should we check?Completion-acceptance mismatch
• Testing is scheduled only at the end. How can we reduce risk now?Late quality feedback
• The team marks tasks complete without evidence. What should change?Evidence-free completion
• We have many defects but no severity agreement. How do we prioritize?Inconsistent defect severity
• Can we launch with known defects?Uncontrolled residual quality exposure
• Our acceptance criteria change after delivery. What should we do?Moving acceptance boundary
• The test environment differs from production. How much does that matter?Unrepresentative verification
• Quality reviews find the same defects repeatedly. How do we improve prevention?Repeated defect causes
• The customer signs off a demo but rejects real use. Why?Demonstration-acceptance gap
• Who should perform user acceptance testing?Unclear business verification ownership
• The team is rushing inspection to meet handover. What should happen?Schedule pressure on verification
• How do we distinguish quality assurance from quality control?Process-versus-output checks
• Our test cases cover the happy path only. What is missing?Incomplete scenario coverage
• A defect fix breaks another feature. How can we prevent this?Insufficient regression protection
• We cannot reproduce a reported defect. Should we close it?Insufficient defect evidence
• The supplier provides a certificate but no test evidence. Is that enough?Unverified assurance evidence
• How do we measure quality without counting defects alone?Narrow quality metrics
• An acceptance test fails because the requirement was wrong. What should happen?Requirement validation failure
• How should we handle conditional acceptance?Uncontrolled acceptance conditions
• How do we keep quality evidence usable after handover?Unusable evidence archive