-
Test tickets in a sprint?
Hello,
What is the best method for scoping testing issues in a sprint? we currently have developers assigning allocated hours before a sprint starts for each issue. However, testers are meant to test tickets within the sprint as the developers finish their daily tasks. The point is for continuous development and testing whereby the developer can constantly drop their daily progress for testers to test against at most times. At present, we are scoping the developer ticket with additional hours allocated for testing but this is turning out very inefficient with either over estimating or under estimating thereby effecting burn downs. Please advice on what methods you guys tend to use in sprints for testers? do you not allocate any hours at all to testers and just create sub tasks to test the sprint scope?
-
2 Replies
-
@thambu my problem is you are separating testing from development. You end up with two “tickets” when in fact, there should just be one. Instead of “develop ABC” and “test ABC” as two tickets, it should be “do ABC” as one ticket. There can be separate tasks in that ticket for developers and testers. The team should be estimating together to come up with reasonable numbers for how long it will take to get the entire ticket (user story, product backlog item, or whatever it is called) to “done”. Separating things out creates a waterfall situation where one group does the work and passes it to another group, rather than the agile way where the group works together.
-
We are now scoping the developer ticket with additional hours assigned for testing, but this is becoming wasteful due to either overestimating or underestimating, resulting in burn downs. https://agileforall.com/forums/reply/103115 doodle jump
Log in to reply.