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 don’t think quality issues should be hidden from customers or mangers. People value transparency and it increases loyalty and understanding. You could even get great ideas from your customer base; that’s why organisations now a-days do beta.
I also don’t think people are keen on producing quality products. It’s easier to do substandard work and the natural thing is to want to take the easy way out. It takes a lot more effort and deliberateness to achieve quality.
Depending on the kind of team and project, supervision is key but doesn’t have to be 24-hour project surveillance. There are people that value trust and feel even more motivated to work at their best when you show them you trust their abilities and let them be.
Quality is should be the most important aspect of any project, so this should be emphasised and taken care of at every stage of the project.
The Quality of q product should not be hidden from the consumers
Quality to me is satisfying customers need at any point in time. It maybe difficult to achieve 100% since needs differ and one product can never satisfy different customers equally.
However quality must be well defined at the start of the project and all team members must indicate full understanding of what is required.
Quality should also be focused internally because it’s like a great covering on the company. It can go a long way to determine how long a company lasts in business.
I also believe people ae keen on producing quality outputs, and team members can produce quality without close supervision if they were carried along from the start.
Teamlead
Team 2
“Team members do not produce quality output without close supervision” is very true.
Most times, in order to cut cost and remain leftovers for the team members, quality is ignored and this leads to failure of projects most times.
But with a close supervision and a detribalized PM, the project can meet it’s quality requirements without cutting corners
Quality should be focused on customer’s needs.
The execution phase of a project indeed plays a critical role in achieving quality goals. This phase involves putting the project plan into action, implementing the tasks, and completing deliverables. By focusing on quality during the execution phase, organizations can ensure that the project outcomes meet or exceed the desired standards. Here are some key reasons why the execution phase is crucial for achieving quality goals:
1. Adherence to project specifications: During execution, it is essential to follow the project specifications and requirements diligently. This involves ensuring that the project team members understand the objectives, scope, and quality expectations. By strictly adhering to these specifications, organizations can avoid deviations that could compromise the quality of the final deliverables.
2. Effective project monitoring and control: The execution phase allows for continuous monitoring and control of project activities. Regular progress assessments, quality checks, and performance evaluations enable early detection of any deviations or issues that may affect the quality of the project. Prompt corrective actions can then be taken to address these concerns and ensure that the project stays on track to achieve its quality goals.
3. Collaboration and communication: Collaboration and effective communication among team members, stakeholders, and relevant parties are crucial during the execution phase. Clear communication channels facilitate the exchange of information, identification of potential quality risks, and coordination of efforts. By promoting collaboration and open dialogue, organizations can address quality-related challenges in a timely manner and make necessary adjustments to maintain high standards.
4. Quality assurance and quality control: The execution phase is when quality assurance and quality control activities are implemented. Quality assurance involves establishing processes, methodologies, and standards to ensure that the project is executed in a consistent and controlled manner. Quality control involves conducting inspections, tests, and reviews to verify that the deliverables meet the defined quality criteria. These activities help identify and rectify any quality issues promptly.
5. Stakeholder involvement and feedback: The execution phase provides an opportunity for stakeholders to be actively involved and provide feedback. Engaging stakeholders throughout the project execution allows for their input on quality-related matters. This involvement ensures that the project aligns with their expectations and enables adjustments to be made if necessary to achieve the desired quality outcomes.
In summary, the execution phase of a project is crucial for achieving quality goals as it involves adhering to project specifications, monitoring and controlling project activities, fostering collaboration and communication, implementing quality assurance and control measures, and incorporating stakeholder involvement. By focusing on quality during this phase, organizations can maximize their chances of delivering a successful project that meets the desired standards.
My views on what quality is and those statements I concur with;
*Quality should be tailored towards customers needs.
*Quality should be considered from the beginning of the project.
*The execution phase of a project is the most critical to achieve quality target as the sayings goes if the foundation is faulty what can the righteous do?
*Quality issues should be discussed openly to find corrective actions.
*Team members do not produce quality outputs without close supervision.
I think the success is of a project is measured by the quality of outputs or deliverables. To achieve this, quality should be considered right from the inception of the project to the end.
Clare Marie Ukaegbu
Cohort 7
Group 3
In project management, quality is simply what the customer or what the stakeholders need from the deliverables. Project quality management can be simply defined as the combination of quality planning, quality assurance and quality control activities.
In my own opinion, Quality should be considered from the beginning of the project.
Because quality is not about ensuring your project gets done on time and within budget. It’s about ensuring you create the right product. One of your stakeholders will receive well.
When it comes to quality, it means doing what you promised to do and doing it on time. Making sure you avoid making too many mistakes and keeping your project on track, means making sure you are always creating the correct result.
It is well known that quality is essential, but its use in everyday life differs from its use in project management. To accomplish the other goals of your stakeholders, such as meeting their schedule and budget, you need to understand the acceptable quality levels.
Since meeting customer’s need is very important, quality out the project output should be taken serious
In the context of project quality, it is important to meet the customer’s needs while not “gold plating” the deliverables with expensive features that add little or no value to the customer. The Project Management Institute defines quality as “the degree to which a set of inherent characteristics fulfills requirements.” While it is important not to gold plate the deliverables, it is also important not to simply meet the bare minimum of requirements as specified in the project contract. Kenneth Rose, author of “Project Quality Management: Why, What and How,” describes a simple set of statements related to project specifications:
If you don’t meet the specifications, you are in breach.
If you want to complete the current contract, meet the contract specifications.
If you want to win the next contract, meet or exceed the customer’s expectations.
Exceeding the minimum requirements is important so the customer is satisfied. However, this must be done in a way that exceeding the project requirements adds value to the customer and not adding features that won’t benefit them.
The execution phase of a project is crucial for achieving quality goals. For me, this is the foundation for achieving a quality project at the end. This is where every parameter for executing the project is put in place without compromise.
Quality should be considered from the beginning of the project.