Hi Guys This is really good topic. Because testing effort is going to be different for different industry, technology, platform, etc... Based on my experience for a fixed bid project, the testing effort will be less than 25%. But at the time of execution the effort may increase, that is what hits the profit of the project. Because most of the customer, give the work to the top IT company because of there best practice, quality technical/functional resource with deep knowledge, review panel, process audit. Keeping all this in mind the customer expects the effort to be less than 25% in a fix bid project. Again am not debating whether it is right or wrong, am just stating based on my experience of writing more than 100 plus proposal in last three to four years. And 85% of time we had finished within the schedule and cost.
By
Mihir Jhaveri, PMP, CSCM, Senior Manager/Pre Sales & Solution Lead/SCM/Strategy, Bristlecone India
| 05 20 2009 17:48:41 +0000
I think it should be lower that 25% of development effort. If you look at the manufacturing industry the effort invested in Quality is not in Quality Control (which is testing in IT) but on Quality Assurance (which should be integrated with dev.)
By
Abhijit Dixit, Director Paymanets and Cash Managment, HSBC Technlogy and Services, Mexico
| 06 18 2008 22:41:47 +0000
|
It is always better to be on safer side ... so i think for any new product the cost should be more than 25%...
By
Santosh A. Jadhav, Sr. Officer Sales
| 08 20 2010 04:11:44 +0000
Yes it should be 25% of higher bcoz it give the final result to the client so it must be perfect .
By
Yogita Jaywant Patil, Associate consultant, Datamatics (CDIS)
| 08 19 2010 13:41:16 +0000
Testing of any produce at initial stage before launch is better though it is costly (can be more than 45-50%). Because after marketing if the maintenance cost is zero or very minimal than the produce will have good raport over market and it would gather max. market coverage. To get a good and reputed product it should be tested under various conditions and applications which could not be so easier after launch so it is better to spend more on testing at initial stage to minnimize the down time.
By
N. NAGESHWARAN, ADMINISTRATIVE OFFICER, M/s. KEC INTERNATIONAL LTD. (an RPG group)
| 05 13 2009 13:16:49 +0000
surely more then 25%...
By
varsha , Head/VP/GM-Quality, frac
| 04 02 2009 18:41:00 +0000
In standerd it's followed 40% of dev time, and this does not only include testing, debugging time is also in this.
By
Diptanjan Mukherjee, Team Leader -(Technical), Navayuga Infotech
| 04 02 2009 18:38:07 +0000
I feel we are not talking of unit testing here coz that I feel should be 75% of the coding effort for function blackbox testing it can range up to 40-50% of the total effort
By
Darpan Sinha, Tech Architect, Royal Bank of Scotland
| 11 06 2008 07:45:09 +0000
It should be more then 25% of Development time.
By
Prashant Gajjar, QA Engineer, Cybage Software Pvt Ltd.
| 08 20 2008 03:27:11 +0000
Earlier the defect is found, less will be the cost to fix the defect. Because if you fix any issue later , you may have to run loads of already executed tests in order to regress the effect of your recent fix which results in increased testing cost.As they say prevention is always better than cure So we should work more towards QA.
By
Ekta Bhatia, Quality and Test Engineer
| 06 24 2008 05:28:37 +0000
Software testing is a necessity. Scheduling of software projects is difficult, often requiring a lot of guesswork. Basically,When deadlines
loom and the crunch comes, mistakes are made. In my opinion more than 30 percent of their total project can be spent on testing as software programs are increasing in complexity.
By
Chirag Sehgal, QA/QC Manager, IBM
| 06 19 2008 03:23:57 +0000
|