The situation
Developers or project leaders say QA is slowing the sprint or release because testing takes too long.
Do not accept the label without flow evidence
Testing delay may be a symptom of late handoff, unclear acceptance criteria, unstable builds, environment outages, defect rework, oversized stories, missing automation, or late test data.
Look at the entire flow
Requirements
↓
Development
↓
Build Stability
↓
Environment / Data
↓
Testing
↓
Defect Rework
↓
Regression
↓
Release
Questions to ask
- When did QA first receive testable work?
- How often was the build rejected?
- Were AC stable?
- How much rework occurred?
- Were environments available?
- How much regression is manual?
- Were stories too large?
- Were dependencies late?
AskAQA recommendation
Recommendation
Measure the delivery flow before concluding QA is the bottleneck. Fix the largest source of waiting and rework, even if it occurs upstream of formal testing.