A project has a more stringent quality management requirement, but it brings a higher management cost, and how to balance it? Saving Changes...
Sort By:
Jaleel .PMP, Associate Director| MetricStreamBangalore, India
Why balancing? If the project requirement is high quality and involves cost, then it is required. However if the requirement is both then it needs to be evaluated and it's better to provide/have clarity on what is it that can be achieved with the constraints put forth. This not only for quality but for an project requirement, be it scope, schedule etc.
...
1 reply by zong li
Mar 22, 2018 5:29 AM
zong li
...
Thanks to the reply, it is in the evaluation, but the quality requirements and the cost requirements are contradictory.
Why balancing? If the project requirement is high quality and involves cost, then it is required. However if the requirement is both then it needs to be evaluated and it's better to provide/have clarity on what is it that can be achieved with the constraints put forth. This not only for quality but for an project requirement, be it scope, schedule etc.
Thanks to the reply, it is in the evaluation, but the quality requirements and the cost requirements are contradictory. Saving Changes...
Quality of a project depends on the project requirement and in line with that cost must be determined for the project. Project budget takes into consideration the cost of quality so why balancing is required . If quality is not maintained or compromised ,the cost of failure must be a matter of major concern. Saving Changes...
This is the analysis work that goes into COQ (Cost of Quality). The hope is that any direct and indirect costs of conformance will be more than made up by reductions in the cost of non-conformance, and if some of the requirements are from an external or regulatory perspective, then those costs should be considered the "cost of doing business" in that industry.
By weighing up the cost vs benefit of implementing quality management. Saving Changes...
Paul HollingsIT Project Manager| Self EmployedHerne Bay, Kent, United Kingdom
Having spent many years in regulated industries I completely agree with Kiron's comment that these are costs of doing business that are factored into all aspects of the company activities.
However, even in these industries you can operate a "just good enough is good enough" philosophy. Quality requirements should be assessed to ensure that they are met, but it is not necessary to go above and beyond the requirements.
As a project manager you have a responsibility to differentiate between needs and wants, and communicate this clearly to sponsors and stakeholders. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Money must be spend into quality assurance not quality control. If you are spending money in quality control then you are making things very bad. Saving Changes...
Amir AliProject Manager| Northbay Solutions Pvt LtdLahore, Punjab, Pakistan
Doing things right the first time (as mentioned by Philip Crosby) is a pro-active solution and help to avoid deciding between quality and cost. Fixing defects involve cost either identified by test driven development, automated unit testing, manual testing by Quality Assurance team or even running automated test cases.
We should spend pre-defined effort on earlier phases by doing complete impact analysis, designing the right approach and implementation with complete focus. Influencing the team members is also important to improve the mind set with an attempt to 'zero defects'.
Even if we have to jump into decision to choose between cost of project and quality, we should spend as much effort as required to maintain quality. Otherwise production and maintenance cost will be much higher later on. Saving Changes...
"Technology is a gift of God. After the gift of life it is perhaps the greatest of God's gifts. It is the mother of civilizations, of arts and of sciences."
