This book is licensed under a Creative Commons by-nc-sa 3.0 license. See the license for more details, but that basically means you can share this book as long as you credit the author (but see below), don't make money from it, and do make it available to everyone else under the same terms.
This content was accessible as of December 29, 2012, and it was downloaded then by Andy Schmitz in an effort to preserve the availability of this book.
Normally, the author and publisher would be credited here. However, the publisher has asked for the customary Creative Commons attribution to the original publisher, authors, title, and book URI to be removed. Additionally, per the publisher's request, their name has been removed in some passages. More information is available on this project's attribution page.
For more information on the source of this book, or why it is available for free, please see the project's home page. You can browse or download additional books there. To download a .zip file containing this book to use offline, simply click here.
Project quality refers to two distinct aspects of the project. Project quality can refer to the quality of the product or service delivered by the project. Does the end product meet client specifications? For example, does a software development project develop a program that performs to the client’s requirements? A software program that performs the basic work functions but does not integrate with existing software would not be considered a quality product, as long as the client specified that the software must interface with existing software.
Project quality can also refer to managing the project efficiently and effectively. Almost any client specification can be met if the project manager has unlimited time and resources. Recall that high quality means meeting the requirements for a particular grade while providing value. Meeting project deliverables within the time and resource constraints is also a measure of project quality. Developing a project execution plan that matches the complexity level of the project is the most critical aspect in developing a project plan that meets project specifications within the time frame and at the lowest costs. These two aspects of project quality have similarities and differences to quality as applied to parent organizations.
All successful quality programs have (1) a requirement for commitment to quality by all the employees and their partners and (2) an emphasis on error prevention and client satisfaction. To comply with TQM, Six Sigma, ISO, or other quality standards required by the client or by the project management firm, the project manager must engage in quality programs and provide documents that specifically comply with the quality standards in use. For example, a project is typically required to follow the parent organization’s work processes related to procurement and document management. Any project processes that interface with the organization’s quality processes will be required to meet the quality standards of the organization.
If a large project involves repetitive processes such as welding or pouring concrete, statistical processes control methods can be used to maintain the quality of the product. These processes control methods are similar to those used by process managers in the manufacturing environment. The intent is for the work of the project to meet design specifications. The welding tools and equipment must be sufficient to perform the welds established in the welding specifications, and the welds must be tested, usually by an independent tester, to assure the end product meets the design specifications. The civil engineers design a concrete pour to meet certain criteria that will support a structure. The criteria, detailed in the design specifications, provide the parameters that the construction crew must meet when pouring the concrete. On large projects, which sometimes have thousands of welds and hundreds of yards of concrete to pour, the use of quality control tools and methods are critical to meeting design specifications
Because projects are temporary, spotting trends in samples produced by repetitive processes is not as important as considering quality in the planning of the project. Instead, the project manager must be able to provide documentation that demonstrates that the correct processes are in place to prevent quality failures.
The cost of quality (COQ) must be considered in the scope document and the project budget. If the group or company that is providing the project management is separate from the client, the project budget will bear the cost of prevention while the client will reap the rewards of avoiding the costs of failure. If senior management does not recognize the benefit to the organization of reducing cost of failure by spending more on prevention during the project, the project manager can be placed in the position of producing a product or service that he or she knows could be of higher quality.
If the cost of quality is not specifically considered and approved by senior management in the scope of the project, quality might be sacrificed during the project to meet budget goals.
At a midwestern university, a new building was being built, but it was over budget. To reduce the cost of the energy management system and avoid a late penalty, the project manager installed a cheaper energy management system. The less expensive system could not reduce power to the air circulation fans during peak electrical price periods, and it was not compatible with other campus systems. Five years after the building was built, when a central control unit was installed to coordinate building energy consumption, the incompatible system was replaced because it could not communicate with the central campus energy control system or save as much in electrical costs. The university did not take the time to specify the quality of the building control system in the scope statement and was not aware of the implication of the substitution at the time it was made. As a result, the cost of quality was lower in the prevention category but much higher in the cost of failure category. Because the parties acted in their own interests instead of the interest of the total university and quality was not a team effort, waste occurred and total cost increased.
Some separation of responsibility for quality is necessary. For example, if a project is undertaken to build a facility that makes something, it is important to distinguish between the quality of the work done by the project team and the quality of the items produced after the project is over. The client provides specifications for the facility that should result in production of quality products. It is the client’s responsibility to provide appropriate project requirements that will result in a facility that can produce quality products. It is the project manager’s responsibility to meet the project requirements. The project manager must focus on meeting requirements for project activities, but as part of the quality team, opportunities to improve the quality of the final product should be discussed with the client. If the final products fail to meet quality standards, someone will be blamed for the failure. It could be the project manager, even if he or she met all the requirements of the project specified by the client.
An electronic parts manufacturer chooses to expand operations and needs to hire and train fifty employees. It uses its own human resources department to handle the selection and hiring of the employees, but it contracts with a nearby technical college to provide some of the training. The technical college is responsible for designing and delivering training on the topic of plant safety practices. The objective of the training project is to reduce the number of workplace accidents, but that is not the characteristic by which the quality of the training program is determined because the rate of accidents for employees who go through the training will not be known until after they have been employed for months or years. The criteria for determining the quality of the training must be something that can be controlled and measured by the project manager during the project.
Because projects are time sensitive, meeting activity finish dates is a common characteristic of quality work on a project that is not typical of a requirement of a process manager.
At a remote mining site in South America, the gasoline and diesel fuel must be brought in by truck over poorly maintained roads to run the trucks and heavy equipment used to set up an ore processing facility. The vendor for supplying fuel is required to provide fuel in the right grades for the various vehicles, in the appropriate quantities, and in a timely manner. If fuel of the right type and grade, with acceptable levels of impurities, is delivered a week after the vehicles have run out of fuel, the work on the fuel-delivery activity is of low quality.
Cost of Failure after the Project
Consider a project you have been involved in, in which the cost of prevention would be part of the project budget but the cost of failure would be incurred after the project was completed. Describe why you think top management would have to be involved to make the best decision for the company.