My vendor's ratio is 1.2 which seems excessive for a MS Dynamics CRM custom solution. We are using an agile approach on a T&M basis. Time spent on QA includes development of test steps, time spent executing tests and documenting bugs before release of software to client, and triaging and estimating of client feedback. If any vendors have rules of thumb they use when planning projects any insights would be appreciated. Thanks Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
40-20-40, where the last 40% of total project time is about QA and Implementation activities. QA is composed by control and assurance.
...
2 replies by Anupam and Tim PM
Nov 24, 2016 9:09 PM
Anupam
...
Hello Sergio,
Is there really a fixed standard, i mean the ratio?
Will it not be correct to check historical records of similar projects in past?
Please advise.
Nov 28, 2016 8:39 AM
Tim PM
...
Really good topic. However, firstly I have several questions- Sergio, just to confirm, do you mean 40 requirements, 20 build, 40 test? Leslie, by ratio is 1.2 , do you mean 1.2 hours QA for every hour of dev, or 2 hours QA for every hour's dev? Best to be certain. Additionally, when talking project time, are we talking effort or duration? Also, are they using automated testing tools (HPE Loadrunner etc) that are already integrated into the environment? Sorry for so many questions, but there are many variables to consider. Best regards.
40-20-40, where the last 40% of total project time is about QA and Implementation activities. QA is composed by control and assurance.
Hello Sergio,
Is there really a fixed standard, i mean the ratio?
Will it not be correct to check historical records of similar projects in past?
Please advise. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Lot of information outside there. And I have validate that in my personal experience to adjust my estimations for each initiative. One of the seminal is "The Mytical Man Month". I do not know if thre is an standard too. Those are the percentage but the life cycle and the way you distribute the percentage along the activities inside the life cycle is up to you
Lot of information outside there. And I have validate that in my personal experience to adjust my estimations for each initiative. One of the seminal is "The Mytical Man Month". I do not know if thre is an standard too. Those are the percentage but the life cycle and the way you distribute the percentage along the activities inside the life cycle is up to you
Thanks Sergio Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
I can pass along the ratio from our contracted firm. You'll find it is also seemingly excessive. I'll post back Monday (hopefully I remember). I cannot recall at this time. Saving Changes...
40-20-40, where the last 40% of total project time is about QA and Implementation activities. QA is composed by control and assurance.
Really good topic. However, firstly I have several questions- Sergio, just to confirm, do you mean 40 requirements, 20 build, 40 test? Leslie, by ratio is 1.2 , do you mean 1.2 hours QA for every hour of dev, or 2 hours QA for every hour's dev? Best to be certain. Additionally, when talking project time, are we talking effort or duration? Also, are they using automated testing tools (HPE Loadrunner etc) that are already integrated into the environment? Sorry for so many questions, but there are many variables to consider. Best regards. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
40-20-40 are percentage from the total project estimation. 20 is related to construction. The first 40 is about all activities before construction. The last 40 is about activities after construction. But before and after is not exactly right because it will depends on your project life cycle. Saving Changes...
Hello and thank you all for your input. I am specifically interested in the number of QA hours compared to the number of pure development hours. When I say factor of 1.2 I mean that there are 1.2 QA hours spent for every hour of development. Development hours include unit testing by developers. QA hours refer to testing by a separate resource(s) as well as replicating and investigating bugs and developing estimates for enhancements. WRT other questions - no automated testing tools are being used. It is effort not duration that is of primary interest here. Any metrics or additional information would be greatly appreciated. Saving Changes...
Interesting. So we've got say 100 hours of Dev and Unit Test, 120 hours of what I would call System Test by the vendor, then your own staff will presumably be doing User Acceptance Test as well (I'd estimate 50-70 hours, though I tend to view UAT as a duration priority - as many people as possible in a short time). Plus any performance and DR tests etc. Does sound quite a lot of testing, but lack of automation of it is a factor, although perhaps the system is unusually complex, e.g. it is accessed in many different ways, interfaces to many other systems, has a large amount of old data to convert and migrate, etc etc
Interesting. So we've got say 100 hours of Dev and Unit Test, 120 hours of what I would call System Test by the vendor, then your own staff will presumably be doing User Acceptance Test as well (I'd estimate 50-70 hours, though I tend to view UAT as a duration priority - as many people as possible in a short time). Plus any performance and DR tests etc. Does sound quite a lot of testing, but lack of automation of it is a factor, although perhaps the system is unusually complex, e.g. it is accessed in many different ways, interfaces to many other systems, has a large amount of old data to convert and migrate, etc etc
Conversion can be ba a big surprise Saving Changes...
