Library › Book 20 › Estimation for QA Work
Estimation for QA Work
4.1🔒The Estimation ProblemWhen 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…
4.2🔒Factors That Increase Testing EffortWhen the team estimates a story, QA should consider:
4.3🔒The QA Estimation Anti-PatternHere is a conversation that happens on many teams:
4.4🔒Estimation Workshop: Worked ExamplesLet us walk through several estimation scenarios to build your estimation instinct.
4.5🔒Estimation Technique: Planning Poker with QA InputPlanning poker works best when QA participates actively. Here is how to make the most of it:
4.6🔒Raising BlockersA blocker is anything that prevents you from completing your testing work. Raise blockers early, clearly, and publicly. "I cannot test the…
4.7🔒Sprint Velocity and QAIf the team's velocity is inconsistent, testing effort is often the hidden variable. Track these metrics to understand the impact:
4.8🔒Q&ASelf-Assessment Quiz: Chapter 41. Why should testing effort be included in story point estimates rather than tracked separately? 2. Name three factors that significantly…
4.9🔒Exercises: Chapter 4[Beginner] Exercise 4.1: Review the stories in your current sprint. For each one, assess whether testing effort was adequately estimated…
4.10🔒Career Translation- Integrated QA estimation into the team's planning poker process, reducing story spillover rate from 21% to under 5% across 6 sprints…
4.11🔒Q&AInterview Depth CheckPrompt: A story is estimated at 3 points by the developers. You believe it is a 5 because it requires testing across 4 user roles and a…