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 agree that Quality should be considered from the beginning of the project.
Below is my submission!
Project quality management is the process of defining quality standards for the deliverables of a project, as well as the quality assurance measures to guarantee those standards are met. However, quality can be an elusive word.
In project management, quality is simply what the customer or stakeholder needs from the project deliverables. Project quality management can be simply defined as the combination of quality planning, quality assurance and quality control activities. Project managers further define these for their projects through a quality management plan.
In addition to a quality management plan, you’ll need the right project management software. ProjectManager offers the best project planning, scheduling, and tracking tools for effective project quality management.
Conclusively, identify the quality requirements for your project deliverables and how the project needs to be managed. Agree on how this process will be documented and how that information will be delivered. Will you have regular meetings, emails, etc.?
The quality planning section will include these specifics as well as metrics for measuring the quality while managing the project. This should include a quality checklist to collect and organize the marks you need to hit during the project.
1) Qualities should be focused on the customer’s needs: The main goal of a project is for the satisfaction of our customers. The most important aspect of the project is to make sure that the client needs are satisfied, which is the core fundamental aspect of a project
2)Quality should be considered from the beginning of a project: It’s important to consider the quality of a project from the beginning, in that way it will spring up ideas of how so many aspects of the project will be handled, what is expected and what to prevent in order to increase satisfaction of the customer
3)The execution phase of a project is the most critical in order to achieve quality targets : when handling the project, its very important to employ the best resources in its execution in order to bring out the best quality result of the project.
4)Quality issues should be discussed openly to find the corrective actions:
Quality of the project should be discussed openly so as to discover the loopholes that might spring up at the course of its execution and for it to be corrected and solutions to be provided immediately
Finally, when considering the quality of a project, you have to balance cost and time frame needed to actualize the purpose of the project as it is the most important factors to consider while handling a project. Cost and time is seen as the basic factors for the durability and authenticity of a project.
Yes, I think quality should be focused on customer’s needs. After all, the customer is the one who ultimately decides whether or not a product or service is of high quality. If a product or service does not meet the customer’s needs, then it is not of high quality, regardless of how well-made it is.
There are a few reasons why quality should be focused on customer needs. First, customers are the ones who are paying for the product or service. They deserve to get what they pay for, and that means getting a product or service that meets their needs. Second, customers are the ones who are using the product or service. They are the ones who will experience the quality of the product or service firsthand. If the product or service does not meet their needs, they will be unhappy and may not use it again. Third, customers are the ones who are talking about the product or service to their friends and family. If they have a positive experience with a product or service, they are more likely to recommend it to others. Conversely, if they have a negative experience, they are more likely to tell others to avoid it.
In today’s competitive marketplace, businesses cannot afford to ignore customer needs. If they want to succeed, they need to focus on providing products and services that meet the needs of their customers. This means understanding what customers want and need, and then designing and delivering products and services that meet those needs.
I agree with this:
Quality should be considered from the beginning of the project: for quality to be considered genuine it has to start from the beginning of project in the sense that it will help to develop good teamwork and bring out the best out of the project
Module 5 Lesson 5 Discussion Assignment
As a Project Manager, here are perspectives on the statements provided about quality:
I agree with this statement: Quality should be focused on the customer’s needs. The ultimate goal of any project is to deliver a product or service that meets or exceeds customer expectations. By aligning the quality objectives with the customer’s needs and preferences, we can ensure customer satisfaction.
For example, let’s consider a software development project where the customer requires a user-friendly interface. To achieve quality in this case, the project team would prioritize usability testing, iterative design improvements, and incorporating user feedback throughout the development process.
I disagree with this statement: Quality is focused internally. While it is essential to have internal quality control processes, the primary focus of quality management should be on meeting customer requirements. Internal quality assurance measures, such as inspections, testing, and process improvements, should ultimately contribute to delivering a high-quality product or service that satisfies the customer.
For instance, in a manufacturing project, the internal quality control team may conduct regular inspections and audits to ensure compliance with quality standards. However, the ultimate goal is to produce a product that meets customer specifications and expectations.
I agree with this statement: Quality should be considered from the beginning of the project. Quality should be ingrained in every phase of a project, starting from its inception. By considering quality requirements from the beginning, project teams can plan and implement processes that facilitate the achievement of quality objectives.
For instance, in a construction project, considering quality from the beginning would involve designing and selecting materials that meet the desired quality standards, conducting proper inspections at each construction stage, and ensuring compliance with building codes and regulations.
I partially agree with this statement: The execution phase of a project is the most critical to achieve quality targets. While the execution phase plays a significant role in achieving quality, it is not the sole critical phase. Quality needs to be monitored and controlled throughout the project lifecycle, from initiation to closure. Each phase presents unique opportunities and challenges to address quality concerns.
For example, in a software development project, the execution phase is crucial as it involves coding, testing, and bug fixing. However, neglecting quality considerations during the earlier phases, such as requirements gathering and design, can lead to fundamental flaws that are difficult to rectify during execution.
I agree with this statement: Quality issues should be discussed openly to find corrective actions. Open and transparent communication about quality issues is vital for effective problem-solving. When quality problems arise, discussing them openly allows the project team to identify root causes, brainstorm solutions, and implement corrective actions promptly.
For instance, in a manufacturing project where defective products are being produced, discussing the quality issues openly would mean involving relevant stakeholders, such as production operators, quality control personnel, and engineers, to collectively identify the causes of defects and develop strategies to prevent recurrence.
I strongly disagree with this statement: Quality problems should be hidden from customers and possibly also managers. Transparency is essential in addressing quality problems. Hiding quality issues from customers or managers can lead to severe consequences, including customer dissatisfaction, reputational damage, and potential legal liabilities. It is crucial to openly communicate quality concerns to the relevant stakeholders and work collaboratively to find solutions.
For example, if a software product has critical security vulnerabilities, it would be unethical and irresponsible to hide such issues from customers. Instead, the project team should proactively inform the customers, outline the steps being taken to address the problems, and provide regular updates on progress.
I agree with this statement: People are keen on producing quality outputs. Generally, individuals have a natural inclination to produce quality work. However, it is crucial to provide a supportive work environment, clear expectations, adequate training, and suitable tools and resources to enable team members to deliver high-quality outputs consistently.
For instance, in a marketing project, team members may be motivated to produce quality content and campaigns that resonate with the target audience. By fostering a culture of quality and empowering team members, organizations can harness their natural inclination towards quality.
I disagree with this statement: Team members do not produce quality outputs without close supervision. While some level of supervision may be necessary, it is not true that team members cannot produce quality outputs without constant oversight. Effective project management involves empowering and trusting team members to take ownership of their work and deliver quality results independently.
For example, in a research project, team members may be responsible for conducting experiments, analyzing data, and producing research reports. With the right guidance, training, and periodic reviews, team members can be entrusted to produce high-quality outputs without the need for continuous close supervision.
In summary, I believe that as a Project Manager, quality should be customer-focused, considered from the beginning, openly discussed, and achieved through a combination of team motivation and suitable management practices. Open communication, transparency, and empowering team members play key roles in ensuring the delivery of high-quality outputs that meet customer expectations.
I agree with the following statements
1) Quality should be focused on customers needs: customers needs and satisfaction should be the focus of any project. Customers are fundamental to organizations.
2) Quality should be considered from the beginning of the project: this gives a clear view and understanding of what is expected, prevent issues and bring excellent output
3) Quality issues should be discussed openly to find corrective actions: this will spring up ideas and bring about solutions to whatever challenge being faced
4) People are keen on producing quality outputs: people take pride in producing quality and quality stands the taste of time. When you are known for quality, much publicity is not even needed for your product to be known
Paul-Okonko Chiamaka
Quality should be considered from the beginning of the project and also at all times, it should be focused on the customer’s needs.
An internal focus on Quality is necessarily upholding customer Satisfaction with utmost importance. also, quality issues should be discussed openly to find corrective actions.
I personally do not believe quality problems should be hidden from customers. if a proper job is done there wont be a need to hide at all
Seeing that people are keen on producing quality outputs, it should be at the hall make of every projects KPI
I agree with the Quality should be considered from the beginning of the project, because it is very essential in considering a better and productive output in delivering. And again Team members do not produce quality outputs without close supervision, yes it is very obtainable because most of teammate time render eye- services, and as such its better a close supervision be carryout for a quality output to be achieved.
“What is quality”
Statements about quality I agree with;
1. Quality should prioritize the customer’s needs.
2. Quality is an internal focus.
3. Quality should be considered from the project’s inception.
4. The execution phase of a project is crucial for achieving quality goals.
5. Quality issues should be openly discussed to identify corrective actions.
6. Individuals are enthusiastic about producing high-quality outcomes.
In addition quality is related to cost. For example a football shoe produced by an international company may be costly but you expect it to be highly durable, comfortable and perform exceptionally well as compared to one produced by a local cobbler using less costly materials.
So for me Quality is defined as a good or service that is fit for use in accordance with its cost of production.
The quality constraint is one of the three triangle constraints (time, cost, and quality). This should be specified from the start of the project through collaboration with stakeholders. Quality management should also be planned and managed during the project’s implementation.