During a sprint our client does 300 user points with 13 QA resouces, client has the story points increase to 425, how many more resouces should i add to QA to conduct thorough testing?Please provide me your inputs Saving Changes...
Using a mathematical algorithm could be one way to approach this - it's the classic puzzle: If three men can dig a hole in 10 days, how many would you need to dig one in five days?
There may be other, more accurate, approaches - but the above method of approximation should be good enough for an initial estimate. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I will write with the information you are giving me. If you use an Agile based method then you do not need additional QA people because the QA process is embeded on the method and if you follow the method as defined QA activities are performed during construction due to stakeholder participation. So, you have to review your process. Saving Changes...
It sounds like you are exceeding the velocity of the team so wouldn't this additional work just go on the backlog for a subsequent sprint? Adding folks to the team won't automatically increase velocity and if you are getting to the extremes of reasonable team size might actually reduce it.
Kiron Saving Changes...
S RajasekarSenior Project Manager| AllscriptsBangalore, Karnataka, India
There is no fixed formula for resource loading , average calculation can be done which will not be 100 %correct. It depends on feature / complexity/knowledge/no of test cases/execution...etc
First why are they pumping points to be delivered in a sprint ? Saving Changes...
S RajasekarSenior Project Manager| AllscriptsBangalore, Karnataka, India
There is no fixed formula for resource loading , average calculation can be done which will not be 100 %correct. It depends on feature / complexity/knowledge/no of test cases/execution...etc
First why are they pumping points to be delivered in a sprint ? Saving Changes...
If your team's velocity is 300 points per sprint and the client wants you to complete 425 points in a sprint, you are either underutilizing your team, or you need to add more people to do the work before you even consider QA.
Now, if you are sizing your stories correctly, the points include QA tasks. If 300 points per sprint is your team's fully-utilized velocity, and your QA team of 13 can't finish more than that in a sprint, simple math would say add 5-6 people. You're adding a little over 40% to the points, so add a little over 40% to the people.
It's rarely that simple, and this doesn't address that this is not an ideal situation to be in.
Are there more variables that need to be considered? Saving Changes...
Community Champion
