1.3Daily Standup

Standup is for coordination, not status reports. Keep it concise and focused on what the team needs to know.

QA Standup Pattern

Yesterday:

"I completed testing on SHOP-456 (login redesign). Found two medium-severity bugs, both filed and assigned."

Today:

"I am testing SHOP-789 (cart optimization). Need the staging database refreshed before I can start integration tests."

Blockers:

"The payment sandbox has been returning 503 since yesterday. I have opened a ticket with the provider but cannot test checkout until it is resolved."

Standup Tips for QA

• Lead with impact, not activity: "Found 2 bugs in login" is more useful than "Ran 50 test cases."
• Be specific about blockers: Include what is blocked, why, and what is needed to unblock.
• Surface dependencies early: If you need a developer to deploy a fix before you can continue testing, say it now, not at 4 PM.
• Keep it under 2 minutes: Save detailed discussions for after standup.