1. “Sufficient Quality” Presentation by Michael Henderson BSc, GDArts, PMP 25 th July 2013 Recognising when enough is enough.

2. Purpose and Background 25/07/20132 1.Why address this question at all? 2.To understand the nature of negotiation. 3.How to decide what is enough. 4.What tools and techniques exist in support of this? 5.Questions and Answers / discussions Sufficient Quality (Q: Why does a French man only have one egg for breakfast?)

3. 25/07/20133 Sufficient Quality Roles of Stakeholders Typically managing in a single dimension: Sponsor: Controlling Cost. Less is more. Business Owner: Champion of scope. More is more. Test Manager: Champion of Quality. More is more. Typically managing in multiple dimensions: Project Steering Committee Project Manager

4. 25/07/2013Sufficient Quality4 Project Management is like a mixing desk: Sliders - Scope, Quality, Cost, Schedule Each slider impacts on other sliders Some are fixed, and some move in relation to others Project Manager tries to reach the correct blend

5. Relationship Between Cost and Quality 25/07/2013 Sufficient Quality 5 Cost Perfection Quality Sufficiency Logarithmic/Exponential Function 20/80 Rule Pareto Rule

6. Getting closer to the target? 25/07/2013Sufficient Quality6 Quality Cost Perfection Budget Quality Cost Perfection Budget

7. What is enough? Law based answer: When the quality meets the acceptance criteria 25/07/2013Sufficient Quality7 Golden rule answer: When the customer or test manager accepts the quality is sufficient to go live

8. Typical Acceptance Criteria When no high severity defects exist When only a certain number of medium severity defects exist Etc etc 25/07/2013Sufficient Quality8... But what is the definition of “medium”?

9. 25/07/2013Sufficient Quality9 Impact Frequency Severity Cost to resolve Value to resolve Defect Prioritisation

10. Purpose of Prioritisation sessions Not to redefine Acceptance Criteria. To negotiate and reclassify defect severity so that the acceptance criteria are met at the right time. 25/07/2013Sufficient Quality10

11. Typical Prioritisation Team Test Manager (Meeting driver, Cost to test) Project Manager (Negotiation Facilitation) Business Owner/ Business Analysts (Impact) Technical Development Lead (Cost to resolve) 25/07/2013Sufficient Quality11

12. When to conduct Prioritisation Meetings? Introduce the purpose at the beginning of the project. Introduce sessions after first complete pass of test, when all blocking defects are resolved. Frequency. Weekly by default. Or more frequently closer to implementation date. 25/07/2013Sufficient Quality12

13. Finally... A Frenchman only eats one egg for breakfast because... one egg is “Un œuf”! 25/07/2013Sufficient Quality13 Thank you for listening. Let un œuf be un œuf!