The cost to fix a defect increases as it gets closer to the Customer.
🤝 During Requirements: It costs very little to check, prototype and review requirements before we program them.
🤝 During Solution and Design: It costs relatively little to review and change a design.
🤝 During Development: It costs a bit more in time and effort to redo an item if it gets this far and there’s a defect. We may need to re-look at the requirements and design too, and re-code the solution.
🤝 During Testing: If we catch a defect during Testing, we may have to redo it in Development, or even go through the process from requirements again.
❌ But once a defect gets to a customer, we have the added cost of bad customer reviews, impacts to our brand or reputation, PLUS the time taken to review the customer complaints and address them, PLUS the waste of something we created that may have to be completely redone.
➡️ What else would you add to the Cost of Quality?
See more Project Management Picture Concepts:
- How The Cost of Quality Increases On Your Project
- How to Measure Business Value for Your Project (NPV, ROI and more!)
- Scrum Roles & Responsibilities
- The Change Control Process in Project Management
- Prototypes in a Waterfall or Agile Project
- Agile Estimating Techniques – Planning Poker and More
- Good versus Bad Project Management
- Benchmarking: How To Do It
- Project Management Office (PMO) Types
- Project Benefit Types – Tangible and Intangible
You can see what people are saying about David McLachlan here: REVIEWS
Navigate to Free Project Management and Leadership Articles through the links on the right (or at the bottom if on Mobile)
