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?
- Quality should prioritize the customer’s needs.
- Quality is an internal focus.
- Quality should be considered from the project’s inception.
- The execution phase of a project is crucial for achieving quality goals.
- Quality issues should be openly discussed to identify corrective actions.
- Quality problems should be concealed from customers and possibly managers.
- Individuals are enthusiastic about producing high-quality outcomes.
- Team members do not produce quality outputs without close supervision.
Share your thoughts on these statements in the discussion section below.
Quality should be focused on the customer needs and should be considered from the beginning of a project . It also involves maintaining standards.
Quality is a multifaceted concept, often defined as the totality of attributes of a good or service that meet customer requirements. This aligns with Joseph Juran’s “fitness for use” and the Agile Project Management (APM) framework’s emphasis on “fitness for purpose and conformance to requirements.”
Reflecting on statements about quality, I agree that quality should focus on customer needs and be considered from the project’s start. Openly discussing quality issues is crucial for improvement, and people are generally keen on producing quality outputs. However, quality is not solely an internal focus, and hiding problems is counterproductive. While execution is important, quality is a continuous process. Empowering team members fosters a culture of quality without needing close supervision.
In summary, quality involves meeting customer needs, adhering to standards, and continuous improvement. Focusing on customer needs, early consideration, and open communication helps achieve high-quality outcomes.
When it comes to quality it may come with different versions of how one perceives quality, however I do agree with the quality in which it meets the customers needs. However quality should also be discussed openly in order to rectify any quality issues at hand.
In project management quality should be considered from the beginning of project with focus on customers needs. As much as the execution phase shows the output of project I don’t believe it’s the most critical in achieving project quality. The intiation and planning phase of the project is also very critical.
A agree with the definition of Quality prioritizing the customers needs, quality being an internal focus, it should be considered from the project’s inception. Quality should be considered in all aspects from the production stage until the delivery period.
I agree with the following statements:
1. Quality should be focused on the customer’s needs: Understanding customer requirements is essential to delivering high-quality products or services.
2. Quality should be considered from the beginning of the project: Integrating quality considerations from the outset ensures that quality is built into the project, rather than being an afterthought.
3. Quality issues should be discussed openly to find corrective actions: Transparency and open communication are crucial for identifying and addressing quality issues promptly.
4. People are keen on producing quality outputs: Most individuals take pride in their work and strive to produce high-quality outputs.
I believe that the discussion for quality of project process should be done internally, customers should be pre-informed so they know what to expect and make changes if it doesn’t meet their expectations to prevent waste of time and resources.
I do not agree with the last point that says “team members do not produce quality output without close supervision” 100% because teams differ from each other, one team can be made up majorly of people with integrity who want to keep the reputation of the company afloat, while another could be made up of people who do not care what people think. So it’s a question of integrity here for me.
I totally agreed with all the points listed on quality but strongly disagree with the one that says quality problems should be concealed from customers and possibly managers, team members do not produce quality outputs without close supervision because since the project has been explained from the beginning, i see no reasons why team members must be closely monitored to deliver quality.
The above are very important points on how quality should be managed or controlled but however some of them are exercised based on the kind of product and the market it is being sold to. The first point says that quality should prioritize customers needs which is absolutely correct and I strongly agree with on all levels of management.
Quality should prioritize the customer’s needs.
Quality is determined by how well a product or service satisfies the customer. If it doesn’t meet their needs, it fails its purpose, regardless of how well it was executed internally.
Quality should be considered from project conception. A proactive approach ensures fewer issues down the line.
I totally agree with the above points about quality control. As a project manager, it is important to put them into good use.