0%
Lab: Friday 4pm Backlog — Full Scenario Pack
14 min
Scenario pack — Friday 4pm
You are on-duty QA for a B2C web + mobile product. Release train: Monday.
Capacity left today: one senior + one junior (~6 hours). Support queue is already hot.
Backlog (no priorities set)
| ID | Summary | Notes |
|---|---|---|
| B1 | Login fails ~2% Safari 17 | Workaround: Chrome or password reset. Tickets rising. |
| B2 | Marketing hero typo "Recieve" | Campaign Monday morning. No functional break. |
| B3 | Payment double-charge on double-click Pay | ~1/200 on slow network. Finance saw 3 cases. Manual refunds. |
| B4 | Admin CSV export 90s | Internal only. Filter smaller ranges helps. |
| B5 | Checkout CTA contrast fails WCAG dark mode | ~12% dark mode. Button still works. |
| B6 | Missing 'X-Frame-Options' on blog | Scanner flag. Main app headers OK. No known exploit. |
Operating rules for this lab
- Use P0–P3 as defined earlier
- Prefer containment when full fix is large
- You cannot honestly mark six items P0 with six hours left
Worked example (B3)
Severity: High — real money integrity
Priority: P0/P1 — contain today (debounce / confirm / monitor), durable idempotency fix ASAP
Why not P3: Rarity does not cancel money risk
Worked example (B2)
Severity: Low–Minor brand
Priority: P3 (or junior drive-by if idle) — not ahead of B3/B1
Your decisions
For the quiz, prioritize like you will defend the call to the CTO in one sentence each.