Make a date-quality tradeoff without violating Definition of Done or hiding risk.
Quality pressure The launch date is close. The requested shortcut is to skip a required test and still call the feature done. The project can adapt, but it cannot keep transparency if done is quietly weakened. Transparency under pressure Date-quality tradeoff Protect the Definition of Done, look for scope tradeoffs first, and log any accepted residual risk. Shortcut Skip the check and hope no one notices. The date discussion stays honest and decision-ready. Quality gates are project commitments, not optional decorations. 01 Done 02 Scope 03 Risk Definition of Done How do you respond to skipping accessibility testing?
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in