Atlas › 20 Agile & Scrum › Estimation and Blockers☰ Read as one page
Estimation and Blockers
3.1Estimating Testing EffortWhen the team estimates story points, testing effort must be included. A story is not "2 points for dev and then QA tests it." It is 2…3.2Factors That Increase Testing EffortWhen the team estimates a story, QA should consider:3.3The QA Estimation Anti-PatternThis is wrong. If testing is separate from the story, the story's "done" status becomes meaningless. Testing effort should be baked into…3.4Raising BlockersA blocker is anything that prevents you from completing your testing work. Raise blockers early, clearly, and publicly. "I cannot test the…3.5The Agile QA ChecklistUse this checklist to ensure nothing falls through the cracks during a sprint.3.6Sprint Velocity and QAIf the team's velocity is inconsistent, testing effort is often the hidden variable. Track these metrics to understand the impact:3.7Hands-On Exercise1. Review the stories in your current sprint. For each one, assess whether testing effort was adequately estimated. 2. Identify your…