- Year not given
Quality versus productivity
Short answer
Quality is conformance to requirements; productivity is output per input. Deming's chain reaction: better quality reduces rework, scrap and delays, thus increasing productivity. Example: Team B with higher quality showed higher net productive output after accounting for defect fix effort.
Explain quality v/s productivity.
Quality is the degree to which a product or service meets requirements and satisfies customer needs ("fitness for use"). Productivity is the ratio of output to input: how efficiently resources are converted into output (Productivity = Output / Input).
| Basis | Quality | Productivity |
|---|---|---|
| Meaning | Conformance to requirements; customer satisfaction | Output per unit of input |
| Measure | Defects, customer satisfaction, reliability | Units per hour, lines of code per person-month, function points |
| Focus | Effectiveness: doing the right thing | Efficiency: doing things at less cost |
| Orientation | Customer | Resources, cost |
| Tools | QA, QC, Six Sigma, TQM | Work study, automation, lean |
Relationship
Traditionally it was thought that higher quality reduces productivity because inspection takes time. Deming showed the opposite: improving quality improves productivity because it reduces rework, scrap, delay and cost.
Better quality -> Less rework -> Lower cost
-> Higher productivity -> More market share
-> More business and jobs (Deming chain reaction)
- Poor quality causes wasted effort: if 20% of work is reworked, productive output falls.
- However, an extreme focus on speed (productivity) can reduce quality; for example, rushed code leads to bugs.
- The best approach balances both: prevent defects, improve processes and train people.
In IT projects
- Test automation raises both productivity and reliability.
- Cutting testing time to save schedule reduces quality and increases maintenance cost later.
- Metrics: defect density (quality) and function points per month (productivity).
Example
Team A writes 1000 LOC/week with 50 defects; Team B writes 800 LOC/week with 5 defects. If fixing one defect takes about as much effort as writing 5 LOC, Team A's net output is 1000 − 50 × 5 = 750 LOC/week, while Team B's is 800 − 5 × 5 = 775 LOC/week. So Team B's net productivity is higher, and its quality is much better (about 6 versus 50 defects per KLOC).
Hence quality and productivity are complementary when quality is built in through prevention.
✓ Answer checked by Claude Opus 5.5 (high effort)
Related questions
- Audio quality versus file size · Multimedia System, chapter 2
- SEI CMM and quality; ISO versus CMM · Software Engineering, chapter 9
- Functional versus structural testing; COCOMO for 200 KLOC · Software Engineering, chapter 8