Defect Management Process

Views:
 
     
 

Presentation Description

Defect Management and Prevention Process according CMMI level 3 Specification

Comments

By: jperinbaraj (97 month(s) ago)

thank you

By: majc509 (109 month(s) ago)

Is there a way of getting a copy of this presentation (Defect Management Process) in a powerpoint format? Appreciate it if you could - thanks - majc509@aol.com

By: lajad3 (115 month(s) ago)

Many thanks Tapas. Rgds YA.

By: lajad3 (115 month(s) ago)

Hi Clareta, Could you assist me with the these slides (in a downloadable format) on defects management process. I am putting together a presentation on the appraoch to identifying and mitigating process defects. Regards Yemi. adenugajames@yahoo.co.uk.

Presentation Transcript

Slide 1: 

Presented by Tapas Pattanaik Clareta Labs Ph# 9776003666 Defect Management Process

Introduction : 

Introduction Defect Prevention is a process of improving quality and productivity by preventing the injection of defects into a software work product. Definition: “…an activity of continuous institutionalized learning during which common causes of errors in work products are systematically identified and process changes eliminating those causes are made.” [Eickelmann]

Agenda : 

Agenda Purpose Introduction Goal and purpose of Defect Management process Implementation plan Assign Responsibility Train People Monitor and Control Q & A

Slide 4: 

Objectives Course Objective To enable participants understand and apply defect prevention concepts Defect Prevention Objectives Identify and analyze the causes of defects& Reduction in number of defect categories Reduction in the extent of defect escape between phases Reduction in frequency of common defects

Purpose : 

Purpose Software Defects are expensive. Defects are inevitable and we can only minimize the number and impact on our projects. For addressing the defects a Defect Management Process[DMP] should be in effect.

Slide 6: 

Today's session is divided into two main Sections

Goals of DMP : 

Goals of DMP The foremost goal is to prevent the Defect, and where its not possible Goal is to quick detection and minimize the impact. The process should be Risk driven. Should be integrated with Software Development process and continuous effort should be made to improve the process. Most defects are caused due process which should be checked.

Defect Management Process : 

Defect Management Process Management Reporting

Defect Prevention : 

Defect Prevention It is virtually impossible to eliminate the defects altogether. Testers/Developers should get strategies for quick detection of defects and minimize the risk. Assess the critical risks associated with the system and identify the defects there off[Most Likely and Greater impact haves the highest priority] Defect Management Process

Deliverable Baseline : 

Deliverable Baseline When a Predefined milestone is reached then Product is Baselined and further development work continues from one stage to another. A deliverable is subject to Configuration Management once it is baselined. A program should be considered baselined when developers pass it on for integration testing. Defect Management Process

Defect Discovery : 

Defect Discovery A defect is said to be discovered when it is brought to the attention of the developers and acknowledged to be valid one. A defect discovery team should comprise of respectable and knowledgeable individuals and should be lead by a Facilitator. Defect Management Process

Defect Resolution Process : 

Defect Resolution Process Defect Management Process

Process Improvement : 

Process Improvement Developers should think in the following way: “While the defect itself may not be a big deal, the fact that there was a defect is a big deal.” or “If this defect could have gotten this far into the process before it was captured, what other defects may be present that have not been discovered.” Efforts should be made to analyze the process that originated the defect to understand what caused the defect. Defect Management Process

Implementing the Process : 

Implementing the Process

Define Critical Metrics : 

Define Critical Metrics Identify Senior Management Sponsors Educate Senior Management Critical Metrics Joint Definition Session:

Identify Critical Risks : 

Identify Critical Risks Are the risks which negatively impact the Critical Metrics set The risk profile should heavily influence the priorities in the Defect Management Plan. Some of the few Risks may be as follows: Stable mature technology vs. new technology Centralized system vs. distributed system Technical platform Large integrated system vs. small stand-alone system Tight target dates Limited budget

Objectives of Defect Prevention : 

Objectives of Defect Prevention Establish practice of Root Cause Analysis within projects for Analysis of Identified Defects Identify critical processes as part of root cause analysis Set goals for improving critical process (shift mean and narrow variation) Reduce most frequent type of defects such as “ not following coding guidelines” Analyze opportunities for improvement by conducting escape analysis. Use defect distribution data to drive process improvement activities Spread lessons learnt - Team Meetings, SEPG, Process Database

Effect of Software Error : 

Effect of Software Error Unreasonable added cost Lost time and effort Inconvenience and annoyance Death Could these incidences of software errors been prevented? YES!

Slide 19: 

Product and Process Defects Artifacts created during the life cycle of the project. Complete set of activities needed to transform user requirements to a product. Process Defects are related to tasks/activities: Non-adherence to standards Poor Documentation Schedule overrun Training related Product Defect are related to requirements : Functional and Non-Functional Defect Prevention Defect Removal/ Elimination Product defect is always a result of Process Defect Process defect is like a potential carrier of disease

Types of Errors : 

Types of Errors

Slide 21: 

Causal Analysis Cycle

Slide 22: 

Root Cause Analysis /Fish Bone Diagram [Ishikawa]

Identify Process Improvements : 

Identify Process Improvements The challenge is to choose the techniques that best address the risk profile and critical metrics defined in the earlier steps. As much as possible, this step should build upon existing methodology, procedures and past experiences. Few areas which needs a strict Vigil during Process Improvement: Documented Process Deliverable Definitions: Defect Reporting System:

Developing Plan and Piloting DMP : 

Developing Plan and Piloting DMP Projects may choose to implement the process, but initially only projects designated as “pilot projects” will receive support and be a fair test of the approach. Criteria for selecting pilot projects should include: Management Approval and Support Receptivity of Project Team Small Project Duration High Project Risk Project s in Early Phase

SEI-CMM checklist for Defect Prevention : 

SEI-CMM checklist for Defect Prevention

Lessons Learnt : 

Lessons Learnt

Any Questions? : 

Any Questions?

Thank You : 

Thank You

authorStream Live Help