1. ## When to Estimate

Can someone shed light on test effort estimations from the following perspectives: When to estimate? What kind of effort to estimate? Should we revise the estimate at some points?

2. ## Re: When to Estimate

[ QUOTE ]
Can someone shed light on test effort estimations from the following perspectives: 1. When to estimate? 2. What kind of effort to estimate? 3. Should we revise the estimate at some points?

[/ QUOTE ]

1. Before a project begins.
2. All efforts. Also included are things that impact schedule such as vacations and much more.
3. Yes. At a minimum you would refine estimates when it is clear that the previous estimates are inaccurate AND will significanlty impact the project timelines, et al.

3. ## Re: When to Estimate

Beg to differ with Jake on point 1. Estimations done before project are WAG estimates, they are in the true essence, wild [stupid is as stupid does] guesses. The efforts spend to make such estimates prove futile when the picture becomes more clear. Check out the link http://www.testinglounge.com/2007/06/12/qa-estimation/
for a few pointers.

4. ## Re: When to Estimate

An estimate is an estimate. If you have a general description of what is intended/needed, a general estimate can be made. Most shops I have worked in this has consisted of a range. As more information is known, that estimate can be refined. If there is enough information for formulate a Request for Services (or whatever the shop calls a service request from clients) there is enough information to build an estimate. In most shops I have worked in, the first task in the estimate is normally "define the project."

5. ## Re: When to Estimate

[ QUOTE ]
Beg to differ with Jake on point 1. Estimations done before project are WAG estimates, they are in the true essence, wild [stupid is as stupid does] guesses. The efforts spend to make such estimates prove futile when the picture becomes more clear.

[/ QUOTE ]

So, I get a invitation to tender, part of which is to come up with an esimtate on how long it would take to test. I assume you are not suggesting that I say it can not be done. So estimating does take place before the project starts, and includes everything that needs to be done, as Jake said. What he did not say (as this was not the question) is that you refine estimates as the project goes on when more details are required.

6. ## Re: When to Estimate

Well although all of my seniors are present here but i would like to share my experience with all of U, I mean i m going to tell u estimation process which we done in our software house:

When to estimate?
Well after the completion of FS Document, or after analysis of functional requirements U can estimate the project like in how many working days or hours it will be completed

What kind of effort to estimate?
Of course against each Functional requirement u need estimation. indeed u have to mention each hour like how many days or hours are required in order to complete a specific task

Should we revise the estimate at some points?
Yup of course u can review the estimation with the refinement of application, if in beginning ur estimation is accurate then there will be a difference of hours or few days

hope so i m right [img]/images/graemlins/smile.gif[/img]
thx

7. ## Re: When to Estimate

[ QUOTE ]
[ QUOTE ]
Beg to differ with Jake on point 1. Estimations done before project are WAG estimates, they are in the true essence, wild [stupid is as stupid does] guesses. The efforts spend to make such estimates prove futile when the picture becomes more clear.

[/ QUOTE ]

[/ QUOTE ]Robin, your disagreement excluded my <font color="blue">item number 3 below.</font> Key word = refinement. Key phrases that I did not include above are contractual requirement and Original Order of Magnitude (OOM) estimates (see below ref. Where I work OOMs are established for many projects twice weekly via formal estimting processes. These estimates are then passed on to the customer to digest and consider before the project contract is accepted/signed by the customer. These estimates encompass all aspects of the project and do include testing estimates for all the levels of testing. WAGs that they might be at this point in project time; WAGs are a part of good project management practices.

<font color="blue">3. Yes. At a minimum you would refine estimates when it is clear that the previous estimates are inaccurate AND will significanlty impact the project timelines, et al. </font>

Ref: http://www.sqaforums.com/showflat.ph...age=0&amp;vc=1

#### 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.