Product v. Project Defects
There are always two quality aspects to any project - the quality of the product and the quality of the project. And a poor quality product does not necessarily indicate a poor quality project. Coming up w/ a standard for best practices for PM at an organisation is the best way to measure how a project fared for quality. There are industry standards, etc. In my experience, poor quality products result from poor requirements and inadequate schedules and funding. Most good PMs will point out these deficiencies. Sometimes, this gets the problem addressed and sometimes it does not. I would caution about many any project quality assessment which includes an assessment of the product, or an assessment of the client's satisfaction w/ the product. As long as the product meets criteria, i.e. it is produced as spec'd, it is not an assessment of project quality management. Don't mix the criteria for project w/ criteria for product. Otherwise, the crappy product produced that that project quickly deteriorates into that crappy project. And we all know what happens to the person who managed that crappy project.
Keep Up with TechRepublic