Quality Flashcards
What is Quality and Grade
Quality: The degree to which a set of inherent characteristics fulfill requirements.
Grade: Grade is a category used to label different products or services that compete to meet the same needs of the end user.
Ex: Quality= Flip phone makes calls. Grade= Iphone has lots of features user likes(camera, video calling, touch screen more apps)
User desirability: Low desire= low grade, high desire= high grade.
How is project impacted if requirements are not gathered well.
Impact on: Cost
Poor requirements gathering leads to scope creep, rework, or misaligned deliverables. This increases costs due to additional resources, changes, or corrective actions that weren’t originally accounted for.
How is project impacted if requirements are not gathered well.
Impact on: Schedule
Inadequately defined requirements can lead to delays. Tasks may need to be revisited, causing the project to overrun its timeline due to rework, additional analysis, or the need for more stakeholder input.
How is project impacted if requirements are not gathered well.
Impact on: Quality Planning
- Poor requirements gathering impacts the ability to plan for quality properly.
- If the product or service requirements are unclear, it becomes difficult to ensure that the deliverables meet the expected standards, which affects the overall quality planning of the project.
- Identify Quality Standards:
This step involves determining which quality standards are relevant to the project and deliverables.
Standards can be derived from stakeholder requirements, industry standards, regulations, or the organization’s internal policies.
In the context of the question, if requirements are not well gathered, it becomes difficult to identify which quality standards apply because the project lacks a clear understanding of what the customer expects.
ID Quality Standards relevant to project(Standards derived from Sh reqs, Regulations, Org policies). If reqs not well gathered becomes difficult to ID which quality standards to apply, because project lacks clear understanding of what custome expects(Unclear Reqs) - Define Quality Objectives:
* Quality objectives are specific, measurable goals related to the quality of the product or process.
- These goals should align with the project scope and the customer’s needs.
* Without well-gathered requirements, the objectives may be ambiguous, leading to misalignment between what the customer wants and what is delivered. - Determine Metrics for Quality:
* This step involves identifying how quality will be measured, such as through key performance indicators (KPIs) or specific quality criteria (e.g., performance, durability, or compliance).
* If requirements are poorly defined, selecting relevant metrics becomes difficult because the team may not know what the deliverable needs to meet in terms of performance or functionality. - Develop Quality Control Measures:
* These measures focus on controlling the processes used to deliver the project to ensure they meet the defined quality standards. This includes setting up processes for inspection, testing, and validation.
* Inadequate requirements gathering can lead to control measures that don’t address the real needs of the customer, leading to ineffective quality control. - Develop Quality Assurance Processes:
* Quality assurance focuses on ensuring that the quality control processes are being followed properly throughout the project lifecycle.
* Poorly defined requirements could result in the wrong assurance processes, making it harder to guarantee the project is on track to deliver a high-quality outcome. - Document the Quality Management Plan:
* The quality management plan is part of the overall project management plan and outlines how the project will achieve its quality objectives. It details the standards, processes, tools, and techniques that will be used to ensure quality.
* In the scenario described, the lack of well-gathered requirements directly impacts the quality planning document, leading to a poorly structured or incomplete plan, which then negatively affects cost, schedule, and quality.
How It Ties into the Question: In the given scenario, if the requirements are not well gathered, the following impacts will occur:
* Cost (A): The project may need to spend additional resources on reworking deliverables, conducting additional quality control checks, and correcting errors caused by misunderstandings.
* Schedule (C): Time will be lost due to unclear or changing requirements, causing delays in completing deliverables as the team tries to meet the customer’s evolving expectations.
* Quality Planning (E): Without clear requirements, it becomes impossible to effectively plan for quality because the project team won’t have a solid foundation for defining what constitutes an acceptable deliverable. This compromises the overall quality of the project output and increases the risk of customer dissatisfaction.
How is project impacted if requirements are not gathered well.
Impact on: Quality Assurance vs Quality Planning
- Quality Assurance (B) refers to activities that ensure the quality processes are followed.
- It’s Quality Assurance (B) refers to activities that ensure the quality processes are followed. It’s less directly impacted by poor requirements gathering since it’s about compliance with established quality processes
But Greatly Affects Quality Planning: since they use the requirements as the basis for all the activities in quality planning. Lack of requirements will create a poorly structured plan.
What are quality metrics and how do they pertain to the deliverables?
Quality metrics are a description of a project or product attribute and how to measure it, hence it would be able to identify whether the customer would be satisfied with the deliverable as the metrics are clear and objective.
Who are the 3 Quality Pioneers?
Philip Crosby, Joseph Juran, Edward Demings
Edwards Deming: Plan-Do-Check, Continuous Improvement and Quality culture driven by mgmt, father of quality
* analyzing and improving processes.
* To improve the performance of everyone,
Juran: Trilogy(QP, QA, QC) quality should be planned for not just inspected in, Pareto(80/20)
Crosby: zero defects(Crosby=Cross(X=Zero)) Do it right first time (DIRFT), cost of quality
Revise
Who created Plan Do Check?
William Edwards
Revise more detail
Who made the analyzing and improving processes for Continuous Improvement?
* To improve the performance of everyone,
Deming
Revise
Who pioneered the need for organizations to meet customer expectations
Juran: By planning for quality we made sure requirements from customer were met throughout project lifecycle.
Who is the Father of Quality who created the Plan Do Check(PDCA) Cycle?
Deming
What is the PDCA Cycle?
- Plan: Identify areas of improvement, establish goals, create plans.
- Do: Put plan into action on small scale and collect data
- Check: Analyze data to determine effectiveness of modifications done.
- Act: Based on results, take necessary actions, such as standardizing successful improvements or revising plans.
how did Juran help with Continuous improvement in Quality?
Using the Juran Trilogy a 3 step continous improvement strategy. To help know and exceed customer expectations.
How did Crosby contribute to Continous improvement?
W/ his zero defect concept. In order to get optimal results org should strive for error free performance. With the following principles.
* Prevention: Prevent flaws is more important than fixing them.
* Quality Free: Investing in quality upfront saves money over dealing w/ the consequences of poor quality.
* Continous Improvement: Encourage culture of continous improvement thorughout org.
How did Deming contribute to Continous improvement
Emphasized systematic approach to CI. Pushed implementation of quality management concept that includes everyone in the org.
* Org can get long term success by focusing on long term progress rather than short term benefits. PDCA cycle gives fw for CI.
