Chapter 10.1: The concept of quality Flashcards
(11 cards)
What’s the basic idea behind quality in a project?
It’s all about meeting performance requirements. A “high-quality” project satisfies the needs of stakeholders, meets expectations, and avoids causing harm elsewhere.
What’s the modern way of thinking about quality?
Instead of just inspecting for defects after the fact, we now aim to prevent defects before they happen by building quality into our processes.
What can happen if teams chase deadlines too hard?
You get rework, stressed teams, and “quality meltdowns.” Cutting corners to save time or money often leads to poor outcomes in the long run.
What real-world example shows the cost of poor quality?
The Challenger disaster (1986): ignoring defect risks in rocket seals led to an explosion that killed 7 astronauts—proof that rushing at the expense of quality is dangerous.
What’s an example of a project with high quality despite high cost?
The London Tower Bridge – It took longer and cost way more than planned, but it’s a long-lasting success that’s still functional and admired over 100 years later.
So, what is quality, really?
It’s more than just ticking off specs. Quality means fitness for purpose—the deliverable works well for what it’s meant to do, is reliable, and satisfies customer expectations.
What does “fitness for purpose” cover?
Everything from performance and safety to ease of handling, environmental impact, and logistical support.
Is quality the same as luxury?
Nope! High grade doesn’t always mean high quality. For example, low-grade coal is perfect for a power plant if it meets the specific need—quality is about suitability, not fanciness.
What’s the deal with “absence of defects”?
It’s part of quality—but not the whole story. A product can be flawless but still fail to meet the customer’s bigger needs like cost, speed, or usability.
What’s “good enough quality”?
It means meeting the most important requirements well, even if not every single spec is perfect. The goal is to be practical—good quality, done on time, within budget.
Who’s responsible for quality in a project?
Everyone. Each team member contributes by knowing what’s expected, being willing and able to deliver, measuring how well they’re doing, and fixing things when needed.
