Well, if this was an interview question, maybe the interviewer was looking to find out how you would think through the problem. As was stated by the moderator and others, there really isn’t a good formula. Different groups have different methods/processes/ tools/models by which they arrive at their estimates. I think it’s safe to make a statement that those methods/processes/ tools/models take into consideration some of the variables that are outlined below.
Specifically speaking to the models, they should be reviewed periodically based on historical data to see if there are updates that are required. In my current organization, one of the items on our plates is to revisit our current estimation model. We’ve got our first release under our belts and are part way through our second release. We have some data to begin refining our estimation model. This will be an ongoing process where the model is periodically reviewed and updated.
Getting back to the original question, if this was an interview question, then you might want to explore an answer within the context of your current role and explain to the interviewer that this is the context in which you’re answering your question.
Just a different way to explore it
There is no formula.There are too many variables: the maturity of the product, the quality of the developers' work, the skill of the developers, the skill of the
testers, development and test environments, etc.. In the end, there is no formula based on developers' time
QA Time vs. Development Time
Subscribe to:
Post Comments (Atom)
1 comment:
Would you say it is similar to the answer of the question, How many programmers should we hire vs. how many QA testers for our Development Dept.? This alternate question is often answered in an ideal world an average would be 1 QA Tester to 2 Programmers, but most companies with useful software products try and get by with 1 QA Tester to 3 Programmers.
Post a Comment