© Mahindra Satyam 2009 Defect Management and Prevention QMS Training

2 © Mahindra Satyam 2009 Objective To examine work products and identify defects and to ensure that the identified defects are fixed

3 © Mahindra Satyam 2009 Objective  To track defects to closure  To analyze the defects to identify root causes  To take necessary action to prevent recurrence of defects

4 © Mahindra Satyam 2009 Process Defect Management Defect Prevention in Projects Defect Prevention at Organization Level

5 © Mahindra Satyam 2009 Defect Management Identify Defects Assign Defects for Correction Defect Analysis and Correction Verify Defect Correction

6 © Mahindra Satyam 2009 Identify Defects  Defects are identified through – Reviews – Inspections – Testing  The identified defects are recorded in – Quantify, or – Defect Tracking Form, or – Review Reports

7 © Mahindra Satyam 2009 Assign Defects for Correction  PL assigns each defect to team member – typically the author of the work product  The assignee is responsible for analyzing and correcting the defect

8 © Mahindra Satyam 2009 Defect Analysis and Correction  Reproduce the defect to confirm it as a defect  Analyze the defect to identify the source i.e. work product which contains this defect – Defect originated in the work product under correction, or – a work product from earlier phase – e.g. a code defect may be because of a faulty design  List all the work products that need to be changed to resolve the defect  Make the correction to all the identified work products

9 © Mahindra Satyam 2009 Defect Analysis and Correction  Record defect resolution and analysis information in Quantify / Defect Tracking Form / Review Report

10 © Mahindra Satyam 2009 Verify Defect Correction  Each defect has to be verified after correction – This verification is recorded in the Defect Tracking Form – Verification for defect identified in testing is done in the subsequent test run – Verification for defect identified in review / inspections is done through follow- up action  A defect once verified is considered closed

11 © Mahindra Satyam 2009 Defect Prevention in Projects Prepare Defect Prevention Plan Conduct Task Kick-off meeting Select defect data for causal analysis Conduct Causal Analysis Implement defect prevention action plan Closure of Defect Prevention Action(s) Communicate DP data to PMG

12 © Mahindra Satyam 2009 Prepare Defect Prevention Plan  PL plans for defect prevention activities within the project while planning the project  This includes: – Identification of causal analysis team – Schedule of Task Kick-off Meetings – Schedule and frequency of causal analysis meetings – Plans for defect prevention actions – Frequency and criteria for evaluation of effectiveness of defect prevention actions

13 © Mahindra Satyam 2009 Conduct Task Kick-off meeting  PL conducts a task kick-off meeting at the beginning of each phase  Task Kick-off meeting shall discuss – Input / deliverables for the phase – Applicable standards, procedures, templates – Inputs from the DP action database and earlier phases of the project regarding common defects, causes and preventive actions applicable to the phase  Outcome of the task kick-off meeting are – Understanding of expectations in terms of deliverables and activities – Understanding of the common defects that occur in the phase – Defect prevention actions to be taken in that phase

14 © Mahindra Satyam 2009 Conduct Task Kick-off meeting  If any suggested DP actions from past projects are selected for implementation, these are to be planned and documented in DP Action Planning Form

15 © Mahindra Satyam 2009 Select Defect Data for Causal Analysis  Select defects for causal analysis – it may not be feasible to analyze each and every defect – select a set of defects that would give maximum benefit – criteria could be type of defects, severity of defects, customer reported defects etc. – Pareto analysis is recommended for selection of defects

16 © Mahindra Satyam 2009 Conduct Causal Analysis  Schedule causal analysis meeting – conduct causal analysis meeting at a time when it can benefit the project – e.g. For coding phase, conduct causal analysis meeting after a few code reviews have happened. This will allow to plough back the learning in the same phase of the project. – At the same time there should be enough defects to identify patterns and causal analysis be meaningful

17 © Mahindra Satyam 2009 Conduct Causal Analysis  Causal analysis meeting to be attended by all relevant team members  Causes to be identified by those who injected the defects during the brainstorming session of causal analysis  Use Cause & Effect diagrams to do the causal analysis  Try to identify the root cause of the defects  For every cause identified ask “why?” till there is no more an answer, this is probably the root cause  Identify preventive actions  Document the causal analysis and preventive actions in DP Action Planning Form

18 © Mahindra Satyam 2009 Implement Defect Prevention Action Plan  Implement the identified actions – Actions that can not be implemented immediately in the project, are passed on to process management group for incorporation in organization wide DP database

19 © Mahindra Satyam 2009 Closure of Defect Prevention Action(s)  For actions that are implemented, evaluate the effectiveness based on identified criteria – Reduction in defect density – Reduction in particular type of defects – Reduction in rework – Reduction in testing effort  PL updates the DP Action Planning Form – Details of implemented actions, experiences etc. – Actual results of implemented actions

20 © Mahindra Satyam 2009 Communicate DP data to PMT  PL communicates the DP data (DP action planning form) to PMT on an ongoing basis  PL sends this: – After every Causal Analysis Meeting – After Intro / Retro Meetings – After closure and effectiveness evaluation of action implementation

21 © Mahindra Satyam 2009 Defect Prevention at Organization Level Gather DP data from projects Analyze DP Data

22 © Mahindra Satyam 2009 Gather DP Data from Projects  PMG gathers DP data from projects on an ongoing basis  From this PMG identifies the information that needs to be disseminated across organization  This dissemination will be through the Project Knowledge Base available in Qualify  The information can be categorized under – Suggested prevention actions – Successful Prevention actions

23 © Mahindra Satyam 2009 Analyze DP Data  The DP data gathered across the organization is analyzed – to identify the common causes of defects across organization – to take appropriate process improvement actions Successful actions will be studied to identify improvements to organization's standard process

24 © Mahindra Satyam 2009 Objective Met  Defects are tracked to closure  Defects are analyzed to identify root causes  Appropriate actions are taken to prevent recurrence of defects