Test tickets in a sprint?
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?
Log in to reply.