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.
I believe quality should be considered at the initiation stage of a project; customers can be used as yard stick in measuring quality especially in iterative project type, and in other project types well researched consumers or customers’ needs would ensure its quality topics of quality in a project should be open, the project manager should study the team members and know those that might require subtle supervision to ensure quality and if all these are put in place in the execution of a project then quality is ensured
For me, I believe it is crucial to address quality issues and discuss them with the stakeholders to foster responsibility and teamwork. This way everyone feels at ease to share his or her concerns and ideas therefore, people take a collective responsibility to tackle underlying problems and address them. Such an approach ensures that individuals within the team develop confidence in one another, and everyone becomes accountable for the final results.
Another advantage of open discussion of quality issues is learning and process improvement. It allows teams to understand each other and look at the problems from different angles to come up with solutions. This decreases the probability of similar problems resurfacing in the future and guarantees that the team is developing. Further, the communication of transparent quality issues also reflect the organization’s commitment to its customers. When customers observe that their complaints are being entertained and solutions provided to them, it instills confidence and trust in the team which can produce more loyal and satisfied customers. Finally, discussion of quality issues makes it easier for individuals not to shift the blame on others. By applying the problem-solving approach, teams work better and have a good relationship with each other in the project. This aids in fostering a culture of improvement and encourages the team members to come up with quality problems and provide solutions without being penalized.
I agree that quality should be focused on customers need in project management because when the needs of a customer are met, it ensures satisfaction on both the customer and the project manager which will lead to loyalty and repeat business even referrals.
Delivering exactly what a customer needs can be used as a criteria for measuring the success of a project.
I also agree that quality should be discussed openly in project management because it promotes transparency thereby encouraging honesty and clarity amongst team members.
It also helps in identifying issues early thereby reducing the impact on the quality of the project and fostering teamwork and collective solutions.
So by discussing quality issues openly, project teams can identify and address issues early, ensuring delivery of high quality outcomes and promoting continuous improvement.
To me, quality should be considered from the project’s inception this will help build intergrity.
Quality should also priotize the customer’s needs, bearing the customer in mind when executing a project is important.
I also agree that quality issues should be openly discussed to identify corrective actions this will give the project credibility as views of team members and stakeholders will be considered.
I believe that quality should be customer-centric, considered from the project’s inception, and openly discussed to address any issues. I think most team members are motivated to deliver high-quality work, but may need guidance and support. However, I disagree with the idea of hiding quality problems or focusing solely on internal processes. Instead, quality should be integrated throughout the project lifecycle, with transparency and open communication driving continuous improvement. By adopting this approach, project managers can ensure that quality is a core aspect of the project, ultimately leading to better outcomes and increased customer satisfaction.
Going by the definition of quality provided by APM (2019, p. 214): it is of utmost importance that the needs of targeted customers be prioritized when determining the quality of a goods or service. It must be put into consideration at the inception of the project throughout the execution/ production stage since individuals are enthusiastic about producing high-quality outcomes. Quality should not be an internal focus such that problems are concealed from customers and possibly managers. Rather, quality issues should be openly discussed to identify corrective actions. Lastly, team members can and do produce quality outputs without close supervision.
Project quality management is a process that considers how a project should proceed to achieve the desired quality for the project’s deliverables. It requires project managers to continually measure the quality of the activities and processes involved in the project. In project quality management, standards are set ahead of time to measure deliverables against, and action needs to be taken throughout the project to course-correct.
Project quality management’s ultimate goal is to guarantee deliverables that satisfy the needs and expectations of clients, stakeholders, or customers, depending on its end-user.
Most project managers will approach a project wanting to reach the best possible outcome, yet many factors could prevent this from happening. Even with the best team and best tools, a project’s output could fall short of its mark without project quality management measures in place.
Quality means making sure a product or service meets what the customers expect or need. It’s about ensuring it works well and matches what was promised.
Statements on Quality:
Quality should be focused on the customer’s needs.
Yes. Quality is all about making sure we meet what the customers are looking for.
Quality is focused internally.
No. While how we do things inside matters, quality should really be about satisfying our customers.
Quality should be considered from the beginning of the project.
Yes. Thinking about quality from the start helps us make sure we get it right in the end.
The execution phase of a project is the most critical to achieve quality targets.
Yes. This is when we’re actually making or doing the work, so it’s crucial to get quality right here.
Quality issues should be discussed openly to find corrective actions.
Yes. Being open about quality problems helps us fix them properly.
Quality problems should be hidden from customers and possibly also managers.
No. Hiding problems doesn’t solve them; it’s better to be transparent and deal with issues head-on.
People are keen on producing quality outputs.
Yes. Most people want to do good work and meet quality standards.
Team members do not produce quality outputs without close supervision.
No. While supervision helps, many people can produce quality work on their own.
These points help us understand how to manage and maintain quality throughout any project.
I agree with “Quality should be considered from the project’s inception” because, a good project manager wouldn’t like the dent his reputation when it comes to handling projects. Quality may be perceived as UTILITY or QUALITY & UTILITY go hand-in-hand.
The quality of your projects can be a kind of advertisement which may help you get more projects.
A good PM knows what good planning is, and having quality in mind from the beginning of a project should be one of his or her top priorities.
I agree with “Quality should be considered from the project’s inception” because, a good project manager wouldn’t like the dent his reputation when it comes to handling projects. Quality may be perceived as UTILITY or QUALITY & UTILITY ho hand-in-hand.
The quality of your projects can be a kind of advertisement which may help you get more projects.
A good PM knows what good planning is, and having quality in mind from the beginning of a project should be one of his or her top priorities.