What is quality [PM Course discussion]

Various definitions of the concept of quality have been put forward.

One generic definition (Pass, 2006b) is as follows:

The overall characteristics of a product or service that fulfill the requirements of customers in terms of quality.

This definition aligns with the viewpoint of Joseph Juran, who, in the 1950s, defined quality as ‘fitness for use’ (as quoted in ASQ, 2019).

This definition is largely consistent with the definition of quality provided by APM (2019, p. 214):

The suitability for the intended purpose and the degree to which the output of a process or the process itself conforms to the requirements.

Now take a moment to consider the following statements about quality. Which ones do you agree with?

  1. Quality should prioritize the customer’s needs.
  2. Quality is an internal focus.
  3. Quality should be considered from the project’s inception.
  4. The execution phase of a project is crucial for achieving quality goals.
  5. Quality issues should be openly discussed to identify corrective actions.
  6. Quality problems should be concealed from customers and possibly managers.
  7. Individuals are enthusiastic about producing high-quality outcomes.
  8. Team members do not produce quality outputs without close supervision.

Share your thoughts on these statements in the discussion section below.

What is quality [PM Course discussion]

2,156 thoughts on “What is quality [PM Course discussion]

  1. Team members do not produce quality output without close supervision
    Quality issues should be discussed openly to find corrective actions.
    Quality should be considered from the beginning of the project

  2. I agree that quality should be considered from the project’s inception and the execution phase of a project is crucial for achieving quality goals.

  3. Quality should be considered from the beginning of the project.
    This is very important as it can affect the whole construction of the project which might lead to disputes between the project team and the client as there need to be a sustainability of the project which can shorten the lifespan if the quality isn’t put into consideration.

  4. I believe that quality should be considered from the project’s inception. This sets the tone of how the project will be run.
    The execution phase of a project is crucial for achieving quality goals, and quality issues should be openly discussed to identify corrective actions.

  5. I totally agree with the facts about quality, however, the statement that “Team members do not produce quality outputs without close supervision” does not apply to all and thus not true in all cases.
    Team members with strong work ethics don’t joke with quality.

  6. 1. Quality should prioritize the customer’s need because they are the one will want to satisfy and feel more appreciable to come to use next time to deliver or assign any task related issues to you as a Project Manager.

    2. Quality should be considered from the project’s inception.
    3. Quality issues should be openly discussed to identify corrective actions.
    4 Quality problems should be concealed from customers and possibly managers.
    5. Individuals are enthusiastic about producing high-quality outcomes.

  7. 1. Quality should prioritize the customer’s needs
    2. Quality should be considered from the project’s inception.
    3. Quality issues should be openly discussed to identify corrective actions.
    4. Team members do not produce quality outputs without close supervision.

  8. 1. Quality should be considered from the beginning of the project. I strongly agree with this, because the quality of a project should be measured from the beginning as you can predict the success of a project from the very beginning. A client’s satisfaction rest on the quality deliverables. In as much as you are trying to save cost and time, you should also add quality to the to-do list.

    2. Quality issues should be discussed openly to find corrective actions. When working on a project with the team, all hands must be on deck. There are people who would want to rush the process and there are also people who will take their time to produce quality work, all of these should be brought to the open so that corrections be made and there will be no errors.

    3. Quality problems should be hidden from customers and possibly also managers. I believe there should be no such thing as ‘hidden from customers’, if you have worked on, and with quality, you should not have anything hidden from either the customers or even the manager. Your work will definitely speak for you.

    4. Team members do not produce quality outputs without close supervision. Like I said earlier, there are people who rush processes and this can alter the quality of a project. On a team, everyone cannot be perfect, the few people in the team who are the ones who make close supervision a must for projects. Otherwise, you should know that with or without supervision, a job must be done correctly with adequate quality.

  9. 1. Quality should prioritize the customer’s needs. I strongly agree with this cause, the overall characteristics of a product or service is to satisfy the requirements of customers.
    2. Quality should be considered from the project’s inception. I agree with this because, with quality been put into consideration from inception of the project; the right project plans, deliverables and project team members can be organized to deliver a quality project.
    3. Quality issues should be openly discussed to identify corrective actions. I agree with this because effective communication and transparency is a key tool to tackle quality issues and also build trust.

  10. I totally agree with the facts about quality, however, the statement that “Team members do not produce quality outputs without close supervision” does not apply to all and thus not true in all cases.
    Team members with strong work ethics don’t joke with quality.

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top