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 essence of project management is quality from the planning to execution and delivery quality should be the focal point.
And quality is a continuous process even as far as communication, innovation, adaptability etc with both clients and team members even on the deliverables.
To the learnwithdexa.com webmaster, Thanks for the well-researched and well-written post!
I believe i can agree and relate to most of them.
Quality in Project management should be considered from the beginning of the project. This implies that quality is a key factor to be considered in every stage of the project from planning to execution and it should also be well discussed among stakeholders and project team so as for it to be prioritized. Quality goods or services sells itself however, every project manager’s goal should be the successful delivery of a quality job. Projects with quality background, helps eases Project manager’s feedbacks to other stakeholders in the project. It also makes accounting easier.
Quality in project management is mainly about meeting the customer’s needs, planning for quality from the very start, and creating a culture where issues are discussed openly so they can be fixed quickly. While execution matters, quality is not just an execution stage activity. It is something the team builds into every phase of the project.
Quality should be looked at base on the need of the customer, but I was looking at it from another angle what about if a customer required the Best quality but the cost to finance to attain that by the customer is not readily available what happen at that instance.
It will always be proper that quality is considered at the onset of the project because this will guide the the project to expected logical conclusion.
I agree with the following options:
(1) Quality should be focused on customer’s needs: l think in project,there must be standards,specifications,time fram for delivery and grade that a customer wants,which he openly states from the start,so during negotiations with the company,if they are able to strike a balance with these needs and the cost to deliver them,then,the project manager and his team is obligated to deliver the agreed output
(2) Quality should be considered from the beginning of the project: if quality is considered from the beginning,it will serve as a template or compass for team members all through the period of executing the project
I agree with 1. Quality should prioritise customers’ needs. Yes, a project’s execution and outcome can be considered quality when it meets customers’ needs and makes them satisfied.
Also, I agree with 3 (Quality should be considered from the project’s inception). Before taking on a project, quality should be considered, rather than waiting until it is almost or has been completed before checking if it is of sound quality. This guides the entire project, saving money, energy, and other resources.
Number 4 (The execution phase of a project is crucial for achieving quality goals) is also crucial. Being the actual stage where a project is carried out is essential. How every team member does their job will determine the project’s final outcome.
I agree with 5 (Quality issues should be openly discussed to identify corrective actions) as well.
Marcelina Eke
In project management, quality refers to how well the project deliverables meet the requirements, standards, and expectations of stakeholders.
It means delivering a product, service, or result that is:
Fit for purpose .
Free from defects or errors, and
Aligned with agreed standards or specifications.
Quality in project delivery isn’t just about perfection , it’s about meeting or exceeding what was promised while ensuring consistency, functionality, and customer satisfaction.
To me, quality in project work means delivering results that genuinely meet users’ needs and expectations. It’s not just about following a plan but making sure the final outcome adds real value and works well for the people it is meant for. In agile or iterative projects, quality improves because the team works in small steps, tests ideas early, and uses feedback to make continuous improvements. For example, when planning an event or outreach activity, we often start with a draft, share it for feedback, and make adjustments before finalizing it. This step-by-step improvement helps prevent big mistakes and ensures the outcome is smooth, effective, and aligned with what users actually want. So, for me, quality comes from continuous learning, good communication, and the willingness to keep improving at every stage of the project.