The article about estimation techniques in agile testing. This article is purely based on practical industry experiences. Especially for beginners who wants to be a part of sprint estimation team.
Estimation techniques in agile testing
I think before start sharing the practical experiences, you must aware the basic level information regarding sprint estimation.
Recognize base user stories.
It is very important to recognize single or multiple platform or reference user story against which you would do relative sizing of the backlog. This story is select from current product backlog or a different user story which we have done earlier. Scrum team should be confident of this base user story.
Discuss through the business requirements of the user story.
Product Owner will clarify questions and provide explanation about what exactly this user story requires.
If this user story is about the same amount of work as one you have already sized, give it the same number of points. If it is more difficult, provide a proportionally higher value. If this user story is related to another but less work in some way, provide a lower value.
Above information is sufficient to know basic awareness about sprint estimations, now I can share my practical industry experiences and challenges.
At first, I would like to add one more important point, as we have each sprint duration is 3 week. Product backlog containing all User stories, business Task and defects etc.
We can follow steps:
As per sprint planning meeting, all required user stories and defects which needs to be tested in the same sprint that all will be move in to current sprint.
Here the testing Estimation and team capacity part comes in focus. At first read carefully the descriptions of the user story, select user stories priority wise like critical to low. If you aware about functionality of the user story’s then it helps you to decide, how many hours require to complete testing?
Calculate your office working days excluding office holidays and weekends, then provide your estimated hours to user story. Generally in testing many sub testing are included such as Scenario writing, Test case writing, Test case execution, defect log and regression testing around the functionality, so ensure that you have considered all aspects before providing estimation.
Provide your staging due dates to each defect, so development team can decide how to meet QA staging due dates.