# Thread: estimate using HLR and identification of resource

1. ## estimate using HLR and identification of resource

how to formulate QA estimate using HLR and how to identify number of resources are required for the project

2. ## Re: estimate using HLR and identification of resource

Hi Tusharkumaravi,
what do you mean by HLR ?

Regards,
Syed.

3. ## Re: estimate using HLR and identification of resource

High Level Requirements i have do high level estimate

4. ## Re: estimate using HLR and identification of resource

Hi TusharKumaravi,

Doing a estimate on Higl level requirement is ok but identifying the resources is a bit tricky part as if you under estimate you will be in jeopardy later at project execution.

5. ## Re: estimate using HLR and identification of resource

hi

so can u plz let me know how i have to do High level estimate, suppose i have 60 reqts classified as 30Medium,21High and 9 low.

If u provide some example that would really helpful for me.

6. ## Re: estimate using HLR and identification of resource

Hi TusharKumaravi,
You can make use of your past experience to arrive at high level estimates based on HLR.

Like you have said that you have requirements classified as high, medium and low.
Arrive at the number of test cases that you can prepare for each type of requirement.
# test cases for High complexity requirements = H * x
# test cases for Medium complexity requirements = M * y
# test cases for Low complexity requirements = L *z

Now your total estamte would be sum of the above.
To this you can add 10 to 20% buffer.

when you provide the same to the customer, tell him that these are high level estimates and would be revised once the details requirements are available.

NOTE:
The actual estimates may be much more or less than the high level estimate.

Regards,
Syed.

Thanks

8. ## Re: estimate using HLR and identification of resource

Depending upon your team, you will need to account for skew related to the efficiency of your team. With manual functional tests the skew is usually not that great, 25-30% longer, but as you move into automation the skews can become quite large. As an example, on the performance front the different between a green, untrained, unmentored individual tossed into a performance testing role and a person who has been trained and mentored is roughly 5x. As you add experience on top of the professional development, then the difference in efficiency grows to 10x (i.e. it takes the green individual ten times longer to accomplish the same task as a seasoned one). You can take a look at this post for some insight on at least the script development phase for a performance test engagement. Functional automation tool skews/efficiencies can easily be at the 5x difference between the green and the seasoned.

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.