Some parameters to consider before we jump and move on
Before giving estimates, we need to ask ourselves about the commitments and priorities on some tests tasks which are repetitive by nature. They are number of builds that we plan to test. Do we take daily build or weekly builds or else? How much risks are there if we do not repeat all the tests we did in the previous build? What are the duplicate tests that we can avoid from one milestone to the other? What about the compatibility tests of the regression? Do we need to perform all tests for each Service Pack? Do we need to repeat the whole test suites for the platform, O/S, different versions of the components of the product? This varies from a group to another. This also varies among products as the newly developed product will require more extensive testing and the risk factor is higher. There are many factors which can change the outcome of the estimate. This also depends on some tangible factors like machine resource and testers available. How many tests have been automated will also affect the estimate outcome
Vinay Jagtap
A hard core Technocrat with over a decade of extensive experience in heading complex test projects coupled with real time experience of project management and thought leadership. Extensive experience in Performance, Security and Automation Testing and development of automation frameworks and ability to setup and execute Global service centers and Center of Excellences for testing.
