Reference no: EM131933382

Project defines quality

The scope of the project, one of the triple constraints of a project, describes in detailed the outcome of the project, which I argue describes and/or dictates the quality. Example my project is a Chevy so the end quality is that of a Chevy, verse if the project is a BMW then the quality is different from that of the Chevy and dictates the quality of a BMW. The other two constraints of the project time and budget also dictates the quality as it is congruent with the scope that is why many authors have quality in the middle of the triangle of the triple constraints.

 My argument is based on the fact that the scope defines the outcome and thus the quality of the project and the budget and schedule flow from achieving the outcome. With respect to TQM it is about removing defects within the system/process to be effective and end with a quality product and/or service thus reducing cost, so TQM is an integral part of any project which would include the final quality of the output of our project, thoughts?