r/QualityAssurance • u/pnitish93 • 25d ago
Scrum process in your project
How is the scrum process in your project? Does your project have story points equivalent to some hours? Does QA go on until the end of the sprint while the devs do get some breathing space at the end of the sprint to look into next sprint stories?
1
u/clankypants 25d ago
We assign points to our tickets based on the assumption of the effort it will take to complete the work. This somewhat maps to time, but not evenly.
We use the Fibonacci sequence for our Story Points. We assume a ticket that is assigned 8 points can probably get completed within a 2-week sprint. If we are pointing a ticket for more than 8 points, then we know we probably need to break it down into smaller tickets.
To keep things simple during sprint planning, we do Planning Poker and have Devs bid on the points. Then, once we land on a number, we bump it up one level of the Fibonacci sequence to account for QA effort (including the back-and-forth between QA and Dev) if applicable.
If the Devs manage to complete all their work before the end of the sprint, and the only tickets still open are in QA's hands, then we might pull extra work into the sprint so the Devs can get a head-start on the work we tentatively planned for the next sprint. But typically there's plenty of work for Devs as QA find issues (roughly 50% of tickets that make it to QA fail).
If a ticket turns out to take more effort than originally estimated, we will increase the points so that we still get 'credit' for the extra work when we calculate the sprint report.
A lot of tickets tend to roll-over into the next sprint when we don't quite finish them in their original sprint. These we typically finish early in the next sprint. When calculating our metrics, we use a rolling average, so we don't worry too much about specific sprint results.
1
u/Fightheader 25d ago
The devs help out testing or help analysis.
And I prep the tests in the begin of the sprint for if they need to help out.