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.
To me, quality should be focused on from the beginning of executing the projects
Quality is focused on the customer need and must be considered from the beginning. Quality is the end result of a process and application. The planning, execution , monitoring of these processes produces desired outcomes which is quality. This is because quality isn’t just external but all encompassing. Eg in constructing a building- the fishing may look enticing and beautiful which maybe referred to as the outcome but if the process was ignored the foundation maybe be weak with beautiful look.
Therefore, quality not just measured on the surface but in consideration of the budget (cost) and time resources.
Quality in Project Management should focus on customer needs, and it should be considered from the beginning of the project. Because quality influences the end result of a Project.
I believe that quality should focus on the customer’s needs and be considered from the start of a project. Waiting until the execution phase is too late , early planning helps prevent issues. I also agree that openly discussing quality problems leads to better solutions and improvement.
However, I disagree that quality should be focused internally or that issues should be hidden. Transparency and customer satisfaction should be priorities. Lastly, I don’t believe close supervision is always needed ,with the right support, team members can deliver quality work independently.
According to the scope of a project, Quality is considered alongside the cost and time. The aim of a project is not just to create the project, it is to satisfy the client or the consumer or stakeholders
Quality is meant to be considered from the beginning of the project through to the end with team members coming together to remind themselves of the project scope and regular supervision and flexibility to achieve the project quality
Quality can be defined as 100 percent standardized of a product or service that it’s achieved by project management .
And to achieve quality with the time and budget we need to plan it from start
It now depends on the ability of the projects manager to be able to control, monitor and supervising the team he or she works with
The manager should be able to use the negotiation skills, control skills, and managing skills for the project to succeed.
Yes, quality is crucial in a project. Here’s why:
*Benefits of quality:*
1. *Customer satisfaction*: High-quality deliverables meet customer expectations.
2. *Reduced rework*: Quality ensures fewer errors, reducing costly rework.
3. *Increased reliability*: Quality products/services perform consistently.
4. *Enhanced reputation*: Delivering quality projects builds trust.
5. *Cost savings*: Quality reduces waste, defects, and long-term costs.
In conclusion,
Prioritizing quality ensures project success, customer satisfaction, and long-term benefits.
Quality in my view, is something that must be embedded throughout the entire project journey, from the beginning to the final outcome. I resonate with all the points shared, as they collectively highlight the importance of aligning internal efforts with external expectations. To truly achieve quality, a project must be shaped by careful planning, driven by purposeful execution, and rooted in a deep understanding of who it’s meant to serve.
I am UKO SAMUEL. Quality is very important and should always be considered before the commencement of any project because it is always what customers or clients look out for in every project.
Quality should prioritize the customer’s needs.
Absolutely. Quality is defined by how well a product or service meets or exceeds customer expectations. If the customer isn’t satisfied, even technically “perfect” work may be considered poor quality.
Quality should be considered from the project’s inception.
Yes. Building quality in from the start avoids costly fixes later. It influences planning, resources, tools, and risk management.
The execution phase of a project is crucial for achieving quality goals.
Agreed. While planning sets the stage, the execution phase determines whether those quality standards are actually met in practice.
Quality issues should be openly discussed to identify corrective actions.
Yes. Transparency promotes problem-solving and continuous improvement. Hiding issues only worsens them.
Individuals are enthusiastic about producing high-quality outcomes.
Often true. With the right motivation, support, and culture, most people take pride in quality work.
I agree with that quality should prioritize the customer’s needs. It should be an internal focus and should be considered from the project’s inception. The execution phase of a project is crucial for achieving quality goals as it is necessary that procedures taken to deliver goods or services to a customer are adding values that will result in quality. Quality issues should be openly discussed to identify corrective actions. Through open discussion, feedback is acquired and the end user gets to state what they consider as a quality product or service.
I agree with; Quality should prioritize the customer’s needs and Quality should be considered from the project’s inception.
The primary aim of processing a good or services, is to consider the end user (customer). Is the product fit for them or not? Would there be a risk occurrence after handing over the product or service?
All the above questions would only be determined at the inception of a project, not during the project or at the completion of the project.