The interesting part of Sprint QA is not the checklist itself. It is the moment when the team realizes a quick pass and a trustworthy pass are not the same thing.
My checklist for Sprint QA is not meant to turn testing into box-ticking. It exists so pressure does not erase the few important questions that protect quality work inside sprint flow, not after it. That difference matters because stories are marked done before QA questions have even found the risky seams.
A good checklist keeps important risk visible when the room gets busy.
Before I Start
- Make the change area explicit
- Write down the most expensive failure in one sentence
- Confirm which scrum teams balancing delivery pace and predictability should review open risk
- Choose the environment that will tell the truth fastest
During the Check
- Exercise the normal path that should protect quality work inside sprint flow, not after it
- Run an awkward-path example based on a sprint board that looks healthy until the last two days collapse into bug traffic
- Watch for mismatches between visible success and hidden state
- Capture the one detail that will matter during sign-off later
Before I Close the Work
I finish by asking whether the evidence would still make sense to someone who was not present during testing. For this topic, the evidence I want usually looks like early story review, test notes during development, and visible risk before code freeze.
If the answer is yes, the checklist did its job. If the answer is no, I am not done yet. When the conversation gets better, the testing usually gets faster as well.