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.
The concept of quality can be multifaceted and is often approached from different perspectives. The definitions provided suggest that quality involves meeting the requirements of buyers or customers, reflecting the idea of “fitness for use” and the degree of conformance to requirements. Let’s reflect on the statements about quality:
Quality should be focused on the customer’s needs.
This statement aligns with the customer-centric definition of quality. Meeting customer requirements and expectations is a fundamental aspect of ensuring the quality of a product or service.
Quality is focused internally.
This statement contrasts with the customer-focused approach. While internal processes are crucial for achieving quality, it’s essential that these processes are designed and executed with the end goal of meeting customer needs.
Quality should be considered from the beginning of the project.
The concept of building quality into a project from the start is consistent with best practices. Early consideration of quality can prevent issues downstream and ensure that customer requirements are integral to the project’s objectives.
The execution phase of a project is the most critical to achieve quality targets.
While the execution phase is undoubtedly crucial, considering quality only during this phase might lead to overlooking critical aspects that should be addressed earlier in the project life cycle.
Quality issues should be discussed openly to find corrective actions.
Open communication about quality issues is essential for continuous improvement. Addressing problems openly promotes a culture of transparency and learning from mistakes.
Quality problems should be hidden from customers and possibly also managers.
Hiding quality problems is generally not advisable, as it can lead to more significant issues in the long run. Transparent communication about challenges allows for timely corrective actions and builds trust with customers and stakeholders.
People are keen on producing quality outputs.
In general, individuals and teams strive to produce quality outputs, especially when they understand the importance of meeting customer needs and conforming to requirements.
Team members do not produce quality outputs without close supervision.
This statement may vary depending on the context and the level of expertise and empowerment within a team. Trust and empowerment can contribute to a more self-regulating and quality-conscious team.
In the discussion, participants might share their experiences related to these statements, discussing practices that have worked well in ensuring quality and addressing challenges. Exploring how different organizations approach quality and sharing insights on fostering a quality-focused culture can also contribute to a rich discussion.
Quality in project management refers to the degree to which a project meets the specified requirements, objectives, and customer expectations. It encompasses various aspects of the project, including the deliverables, processes, and overall performance.
There are several key elements that contribute to achieving quality in project management:
– Requirements management
– Planning and documentation
-Risk management
– Quality control
– Stakeholders Engagement
– Continuous improvement
Quality stands as the paramount criterion in any project, serving as a decisive factor in its success. Therefore, in project management, emphasizing quality from the project’s inception is crucial and should be a top priority.
Open discussions about quality should be initiated early in the project to identify and implement necessary corrective actions. It’s evident that maintaining rigorous and transparent supervision over team members is essential to ensure the delivery of high-quality project outputs.
As a project manager, I agree that;
•Quality should be considered from the projects inception because if adequate plans and arrangements are not carried out at the beginning of a project, the project team might end up delivering and product that is not up to the client/stakeholders expectations.
•Quality issues should be openly discussed to identity corrective actions. In the course of carrying out a project, the project manager, the project team and the clients should ensure that there is a constant flow of communication in order to avoid encountering errors and ensure that they deliver a product according to the client’s
Qualityis the first creterial in any project and to determines the success of it. Hence, in project managements quality should be considered from the beginning of the projectas a high creterial of consideration.
It should be discussed openly to identify corrective actions.
It’s clear that strict and open supervision toward team members must be applied for the sake of project quality outputs.
I believe that the quality of a product determines the success of it. Therefore, in project managements quality should be considered from the beginning of the project.
It should be discussed openly to identify corrective actions.
I equally agree that team members do not produce quality outputs without close supervision.
Quality should be considering at the beginning of every project. While the idea of getting the job done and within the stipulated time is considered, quality is key to ensuring the success of the project and through the life span of it.
As someone that works in the Data Management space, the quality of the data that is used within the organisation is one of the goals if not the goal of why we manage data or why data management has become a big thing within organisations. When working on data projects, the dimensions of data quality are considered from the start and this is imperative. While the project manager (the project manager will not necessary be called that within the organisation) may lead the charge, quality data that is fit for purpose is the responsibility of everyone in the organisation especially those involved with creating data.
Let me first say that if there’s no quality in the idea of carrying out a task or making a produce, then there might be tendencies of having less or no good products to be sold.
So I must say that before a team can successfully go ahead with a production then there must have been a quality check on what to produce, how to produce, when to produce and where to produce.
Quality as the name implies and as Joseph Juran said fitness for use. Quality should focus on all the different concept as stated because it should prioritise the customers need who is the end user, it should be an internal process, and be considered from inception. Quality flows through all the listed areas and beyond because with quality works , comes quality service, which is also achieved through quality teams and quality of process and it leads to quality of life.
I agree with all except;
• Quality problems should be concealed from customers and possibly managers.
REASON: As a project manager transparency of information is important. Clients and stakeholders feedbacks are essential for the success of the project.
• Team members do not produce quality outputs without close supervision.
REASON: All team members know the goal, scope and deadline of the project, which is why I believe they can produce quality output. An example is the iterative approach.
I think quality should be discussed before the start of any project. It’s the quality of the PM’s work that will make the stakeholders consider him in the first place.
Absolutely, considering quality from the project’s inception is crucial. Incorporating quality measures early helps prevent issues downstream, reduces rework, and ensures a more efficient development process. It contributes to overall project success and customer satisfaction.