Hello!

In this module,
we will introduce
2
you to the
concept of Defect
4 Management.
So, let’s get
started.
4

Defect Management
1

Learn what a defect is and how to detect a defect in your project

3 Plan defect prevention and planning

Learn about the defect management life cycle

 Overview and Objectives

At the end of this module, you will be able to:

– Define defects
– Identify the common sources of defects
– Explain the relationship between defect and SDLC phases
– Identify types of defects
– List the role and responsibilities of a Defect Prevention
Coordinator
– Explain the Defect Management Life Cycle
– Define Quantitative Project Management
– Explain the C2.0 defect tracking flow
– Identify the steps to perform a causal analysis and resolution
– Explain the different types of metrics

2
 What is Defect?

2 According to Crosby (Quality Is Free), a defect can be defined as a failure to conform

to requirements, whether or not the requirements have been articulated or specified.

4 The word defective is defined as an entire unit that fails to meet the acceptance
criteria, regardless of the number of defects within the unit. A unit would also be
known as defective if there were one or more defects.

1 Reference Image

3
 Examples of Defect

Defect Example 1:
Note to GD: The pop up for Non-functional requirements are
element 2 is provided on the missed
next slide.

Defect Example 2:
User interface is incorrect

2
Defect Example 3:
Coding standards are not adhered

Let us look at a Defect Example 4:

few examples of Exception and error handling is not
defects. implemented
1
Click each example to know more.

4
 Examples of Defect (Cont.)

Pop Up Header Pop Up Content

Defect Example 1: Defects may arise when non-functional requirements
Non-functional requirement are missed are missed. Such defects include:
• Performance issues
• Compatibility issues, which are not addressed
explicitly in the requirements document.
Defect Example 2: Defects may arise when user interface details are
User interface is incorrect addressed incorrectly in the design document.
Defect Example 3: Defects can be a result of inadequate comments in
Coding standards are not adhered the code.
Example:
• While coding in Java, blank space should not be
used between a method name and its opening
parenthesis.
• Consistency should be maintained in the font
styles for UI standards.
Defect Example 4: Defects can be the result of exceptions that occur in
Exception and error handling method is the number format while importing files.
not implemented

5
 Defect Detection by Appraisal Tasks

Stage Detection
2 Review WPs Detection Process

Requirement BRD, SRS Requirement Review

Architecture Architecture Architecture Review
Design HLD, LLD, DB Design Review
Coding Code Code Review
Unit Testing Code, Unit Test Cases UTC Review, Unit Testing
Integration Testing Code, Integration Test Cases ITC Review, IT Testing
System Testing Code, System Test Cases STC Review, ST Testing

Refer : https://c20search.cognizant.com/Process%20Space/inc/Docs/DeliveryMgmt/QGDM-DEFCAU.pdf

Next, we move
on to an
understanding
of Defect
1 Detection.
 Common Sources of Defects

2 Inadequate Process
Human Errors Environmental
Adherence

Click each source of defect to know more .

Note to GD: The pop up for

element 2 is provided on the
Don’t you want to next slide.
know about the
1 sources of defects?
 Common Sources of Defects (Contd.)

Pop Up Header Pop Up Content

Human Errors Examples of Human Errors:
• Omission
• Ignorance
• Typography
• Knowledge Information
• Assumption
• Oversight
• Misunderstanding
Inadequate Process Adherence Missing process steps in the life cycle injects defects,
such as:
• Requirement understanding validation
• Change tracking
• Impact analysis using requirement traceability
matrix
Environmental Examples of Environmental Errors:
• Incorrect environment setting
• Connectivity issue

8
 Defect and SDLC Phases
What are
SDLC phases? 1. Tha
Requireme
nts Be
7.
User 2. rela
1 Acceptanc Analysis and
e Testing
und
Software 2a
Development
Life Cycle
6.
(SDLC ) 3.
Integration
Design
Testing

5.
4.
Unit
3 Coding
Great! Testing

2
 Relationship between Defect and SDLC Phases

Let’s now
understand the
relationship
between 2
defects and the
SDLC phases.

Defect Injection Defect Detection

1
 Defect Injection and Defect Detection

Re-do the table

1
PD Name % Injection % detection

Requirement 8.80% 4.00%

Design 22.53% 14.00%

Coding 40.74% 23.00%

Unit Testing 13.11% 17.00%

Integration Testing 3.86% 4.50%

System Testing 10.87% 35.00%

User Acceptance Testing   2.50%

Example: The defect density of Java as per Organization Level Benchmark (OLBM) is 0.13
defects/Function Point (FP). Defect density is the count of defect per unit size of the
2 application developed. So for a Java based project with a project size
Defect Injection
of 1000
Defect FP, the total
Detection
predicted defect count will be 1000 multiplied by 0.13, which is equal to 130 defects. This will
be distributed across phases or process disciplines as per the percentage injection rate in the
given table. Projects need to plan for defect prevention by considering corresponding defect
type and causes from practice or historical data from similar past projects.
 Types of Defect

There are two types of defects that you can face while working on a project. They are
classified as:
2 • Defect Type by Severity in C2.0
• Defect Type by Priority in C2.0

Wondering how
many kinds of
defects you
might face in
your project?
1
 Defect Type by Severity in C2.0

Superficial 1 Minor Major

Major defects can be
Superficial defects are Minor defects are moderate in categorized as annoying, very
mild where symptoms nature where the outputs are serious, extreme, intolerable,
offend us aesthetically. misleading or redundant. catastrophic and infectious in
Example: Typos, errors in Example: Screen layout issues, nature.
documentation, GUI default value missing for the fields Example: Images, missing
image colors, and so on. required, misleading error graphics which hinders
messages, and so on. functionality, incorrect
functionality implemented,
and so on.

Click MORE INFO on the

Major defect type box to
2
know more.
 Defect Type by Severity

Superficial 1 Minor Major

Major
Superficial defects are Major defects can be categorize
Minor defects are moderate in as annoying, very serious,
mild where symptoms
Annoying • Causes dehumanizing system behavior.
nature where the outputs are
offend us aesthetically. extreme, intolerable, catastroph
misleading or redundant.
account. and infectious in nature.
Very in
Example: Typos, errors Example: Screen layout issues,
documentation, Serious
GUI Example: Images, missing graph
• Instead of losing your paycheck, the system credits it to another
default value missing for the fields which hinders functionality,
image colors, and so on. required, misleading error
• Problem is not limited to a few users.
Extreme incorrect functionality
messages, and so on. implemented, and so on.
• Long term, irrecoverable corruption of database.
Intolerable
Click on MORE
INFO on the Major
Catastroph
fails.
ic defect type box to
• Decision to shut down is taken out of our hands and the system
know more about it.
• Corrupts other systems even though it does not fail itself.
Infectious
Close

2
 Defect Type by Priority in C2.0

High 1 Medium Low

High priority defects Medium priority defects can be Low priority defects can
should be resolved resolved during the normal course be repaired after fixing
immediately and requires of development. other serious defects.
high attention. Example: Font used for displaying Example: Superficial
Example: Incorrect an output does not match defects such as typo
functionality customer requirements. errors in
implementation. documentation.

Click MORE
INFO on each of
the defect type box
2 to know more about
them.
 Defect Type by Priority in C2.0

High 1 Medium Low

High
Defect need to be Defect need to be resolved in the
has been repaired. Defects have low
Resolve
resolved immediately and priority or can be
• Further development and testing cannot occur until the defect
normal course of development
Immediately
requires high attention. activities. deferred.
Example: Incorrect Example: Font used for displaying Example: Superficial
impairing development, testing, and system use.
functionality Give High defects such as typo
an output does not match
• The defect must be resolved as soon as possible since it is
implementation. Attention customer requirements. errors in
documentation.
Close

Click on MORE
INFO on each of
the defect type box
2 to know more about
them.
 Defect Type by Priority in C2.0

High 1 Medium Low

Medium
is created.
Normal development activities. It can wait until a new build or version
Queue • The defect should be resolved in the normal course of

Close

Click on MORE
INFO on each of
the defect type box
2 to know more about
them.
 them.
to know more about 2
the defect type box
INFO on each of
Click on MORE
Close
• The defect repair can be put off indefinitely. It can be
Defer
resolved in a future major system revision or not resolved at
all.
• The defect is an irritant that should be repaired but only after Low Priority
more serious defects have been fixed.
Low
Low Medium 1 High
Defect Type by Priority in C2.0
Drag and drop the correct options in each of the boxes. Click Submit when you’re
done.

Inadequate Process
Human Errors Environmental Errors
Adherence

You know that the three Submit

common sources of defects
1 are human errors,
inadequate process
adherence, and
environmental errors.
That’s correct!
• Omission and assumption are examples of human
errors.
• Missing a step in the life cycle such as gaps in
requirement understanding cause defects due to
inadequate process adherence.
• Incorrect environment setting and connectivity
issues are examples of environmental errors.

Not quite right.

• Omission and assumption are examples of human
errors.
• Missing a step in the life cycle such as gaps in
requirement understanding cause defects due to
inadequate process adherence.
• Incorrect environment setting and connectivity
issues are examples of environmental errors.
 Defect Prediction and Prevention Planning

Reference I
3

Activities Work Products Tools and Templates

Click Click Click

Let’s now move Here Here Here

on to Defect
Prediction and
Click each element to know more.
Prevention
Planning.

1
At the beginning of any project, the
total defects generated during
development can be predicted. This is
known as Defect Prediction and Note to GD: T
2 Prevention Planning. shown is pro
next s
 Defect Prediction and Prevention Planning (Cont.)

Strategy Description
Activities • Predict defect count based on technology, defect density benchmark, effort, or
project size.
• Predict life cycle stage wise defect count.
• Plan for prevention of these defects considering similar past projects and top
practice repeat defect types.
• Identify actions to prevent it.
• Identify the DP coordinator of the project.
• Set up tool for defect tracking.
Work Product • Defect Prevention Plan
• Defect tracked in tool
• Defect data
• Defect causal analysis
• DP meeting within team
Tools and Techniques • DP Plan
• Process Performance Model (PPM)
• C2.0 or eTracker
• Control chart
For more on tools and templates, go to:
https://c20search.cognizant.com/Process%20Space/default.aspx
Process  Delivery Process  Project Delivery Management Work Products
 Role and Responsibilities of a Defect Prevention Coordinator

2 The Defect Prevention Coordinator:

 Identifies the top defects of a respective
practice and that of the organization.
 Plans the defect prevention activities at the
Wondering who is start of the project. 
responsible for  Identifies the project’s top critical defects
prevention of defects using standard techniques such as
arising out of the Hypothesis Testing/Pareto.
development process?  Maintains and periodically updates Defect
1a and Problem Prevention Plan.
e
s  Determines frequency of  DP activities.
3  Conducts DP meeting within the team
involving  key stake holders as needed.
 Performs root cause analysis of defects at a
1 defined frequency.
 Role and Responsibilities of a Defect Prevention Coordinator (Cont.)

 Identifies or proposes action items based on root cause analysis.

 Monitors the status of action items or taking preventive measures to track issues to
closure.
 Facilitates the team to arrive at corrective and preventive actions and proposes action
items based on the root cause analysis.
 Ensures implementation of these preventive actions.
 Validates the effectiveness of action using Hypothesis test.
 Updates the process workflow if any based on the actions taken.
 defect
? Defect Management Life Cycle
ulated
le?
1.
3 Predict Defect

2.
5.
What-If Analysis
Improvement
& Plan
Validation
Prevention
Defect
Management
4 Life Cycle

4.
3.
Defect Causal Collect Defect
Analysis & Sub
and related data
Process
& Monitor Sub
assignable causal
analysis
Process 2
 Predict Defect
Predict Defect call out te
2 • Go to https://c20searc
and then perform the
1. 1. On the C2.0 hom
Predict 2. On the Process m
Defect
3. On the Delivery P
Management an
2. • The DP Plan template
5. What-If
Improvemen Analysis & PPM of a project. It he
t Validation Plan o Monitor the proje
Defect Prevention
Management o Avoid plan deviati
Life Cycle

4.
Defect 3.
Causal Collect
Analysis & Defect and
Sub Process related data
assignable & Monitor
causal Sub Process
analysis
 Predict Defect (cont.)

1.
1 Predict
Predict
Defect
Defect

2.
5.
Improvem
Improvem
What-If
Analysis
Analysis &
& 3
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 On the same slide
as previous. Predict Defect (cont.)

1.
Predict
Predict
Defect
Defect

5.
2. 2
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 On the same slide
as previous. Predict Defect (cont.)

3
2

1.
Predict
Predict
Defect
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 On the same slide
as previous. Predict Defect (cont.)

1.
Predict
Predict
Defect
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 On the same slide
as previous. Predict Defect (cont.)

3
4

1.
Predict
Predict 2 5
Defect
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 On the same slide
as previous. Predict Defect (cont.)

3
4

1.
2
Predict
Predict
Defect
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 What-If Analysis and Plan Prevention
What-If Analysis & Plan
2 • The organization or Pr
o Manage a projec
1. o Set appropriate b
Predict
Defect
• A What-If Analysis tem

2.
5. What-If
Improvemen Analysis &
t Validation Plan
Defect Prevention
Management
Life Cycle

4.
Defect 3.
Causal Collect • A defect prevention p
Analysis & Defect and
Sub Process related data defects in practice.
1 assignable & Monitor
causal Sub Process
analysis
 Note to GD: The pop up for
element 4 is provided on
What-If Analysis and Plan Prevention (cont.) the next slide.

2 What is Quantitative Project Management?

To manage a project quantitatively,

• Set project goals based on
• OLBM
2
• PLBM
• Past performance
• Set reasonable goals
• Use the Process Performance Model
1 1.
1.
Predict
Predict
Refer : https://c20search.cognizant.com/Process%20Space/inc/docs/DeliveryMgmt 3
Defect

2.
5.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect
Management
Management
Preventio
Preventio
n
n
4
Life Cycle

4.
4. 3.
3.
Click the book icon to know more about the OLBM and PLBM.
Defect
Defect Collect
Collect
Causal
Causal Defect
Defect
Analysis & and
Sub related
Process
Process data
data &&
assignable Monitor
 What-If Analysis and Plan Prevention(cont.)
Reference Image

What is Quantitative Project Management?

To manage a project quantitatively,
• Set project goals based on
• OLBM
OLBM and PLBM
• PLBM
OLBM or organizational level benchmarks contain all metrics
• Pastbenchmarks
performance
considering all projects of the organization.
• Set reasonable
PLBM orgoals
practice level benchmarks are derived from
performance data of all projects in a practice.
• Use the Process Performance Model
1.
1. Each practice of the organization must have its own PLBM.
Refer : https://c20search.cognizant.com/Process%20Space/inc/docs/DeliveryMgmt
Predict
Predict
Defect

2.
Close
5.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect Preventio
Preventio
Management
Management n
n
Life Cycle
Note to GD: As mentioned, this will Click the book icon to know more about the OLBM and PLBM.
4.
4. 3.
3.
be aDefect
pop
Defect up for the
Collect previous page
Collect
Causal
Causal Defect
Defect
when the
Analysis &
Sub
learner andclicks the book
related
Process
Process
assignable icon.
data
data &
Monitor
&
 On the same slide
as previous.
What-If Analysis and Plan Prevention (cont.)

2 Process Performance Model

3
• The PPM helps to:
o Predict future perform
o Measure reasonablen
5 • Includes the following essen
o Controllable X’s
o Connection to sub pro
o At least one statistical
o Sub processes selecte
management and not
process.
1.
1.
Predict
Predict
Defect
7
2.
5.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect Preventio
Preventio
Management
Management n
n
Life Cycle

4.
4. 3.
3.
Defect
Defect Collect
Collect
Causal
Causal Defect
Defect
Analysis & and
Sub related
Process
Process data
data &&
assignable Monitor
 On the same slide
as previous. What-If Analysis and Plan Prevention (cont.)

1.
Predict
Predict
Defect
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 On the same slide
as previous. What-If Analysis and Plan Prevention (cont.)

5 6

2 3

1.
Predict
Predict
Defect
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 On the same slide
as previous. What-If Analysis and Plan Prevention (cont.)

3 4

1.
Predict
Predict
Defect
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable Monitor
 Collect Defect Data and Monitor Sub Process

2 Collect data & monitor su

• The defect tracking fun
1. users to:
Predict o Create and,
Defect
o Track defects
• Sub process performan
5.
2. charts.
What-If
Improvemen Analysis &
t Validation Plan
Defect Prevention
Management
Life Cycle

4.
Defect 3.
Causal Collect
Analysis & Defect and
Sub Process related data
1 assignable & Monitor
causal Sub Process
analysis
 To track def
https://cognizant2
Collect Defect Data and Monitor Sub Process (cont.) /MS/MashUp/Pag
.
1 On this page
C2.0 Defect Tracking Flow: Track Defects Work>Track
Track

header,
Defects.

1.
1.
Predict
Predict
Defect

2.
5.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect Preventio
Preventio
Management
Management n
n
Life Cycle

4.
4. 3.
3.
Defect
Defect Collect
Collect
Causal
Causal Defect
Defect
Analysis & and
Sub related
Process
Process data
data &&
assignable Monitor
 Collect Defect Data and Monitor Sub Process (cont.)
ew/Testing
under
rd Details,
atory
en click

1.
1.
Predict
Predict
Defect
3
2.
5.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect Preventio
Preventio
Management
Management n
n
Life Cycle

4.
4. 3.
3.
Note to GD: Elements on
Defect
Defect
Causal
Causal
Collect
Collect
Defect
Defect
this page will be played out
Analysis & and
Sub related in the last page itself in
Process
Process data
data &&
assignable Monitor continuation.
 To view defect details,
Collect Defect Data and Monitor Sub Process (cont.)
list of Review/Testi
Records, click on th
C2.0 Defect Tracking Flow: View Defect Details required defect, and t
view the details under
Defect Details sectio

1 2

1.
1.
Predict
Predict
Defect

2.
5.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect Preventio
Preventio
Management
Management n
n
Life Cycle

4.
4. 3.
3.
Note to GD: Elements on
Defect
Defect
Causal
Causal
Collect
Collect
Defect
Defect
this page will be played out
Analysis & and
Sub related in the last page itself in
Process
Process data
data &&
assignable Monitor continuation.
 Collect Defect Data and Monitor Sub Process (cont.)

C2.0 Defect Tracking Flow: Enter ResolutionYou

Defect
canDetails
now view the
defect created and
assigned to you in
1 your workspace.

1.
1.
Predict
Predict
Defect

2.
5.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect Preventio
Preventio
Management
Management n
n
Life Cycle

4.
4. 3.
3.
Note to GD: Elements on
Defect
Defect
Causal
Causal
Collect
Collect
Defect
Defect
this page will be played out
Analysis & and
Sub related in the last page itself in
Process
Process data
data &&
assignable Monitor continuation.
 Collect Defect Data and Monitor Sub Process (cont.)

Monitor Sub Process

XMR Chart – Code Review Defect Density

Code Review Defect Density - Module level

To monitor sub process performance:
6 1
• Statistically monitor the critical sub process
U C L=4.895

PPM, used to predict the probability of mee

Individual V alue

_
2
X=1.465
project goal(y).
• Use suitable control charts.
0 2 2

2 -2
1 3 5 7 9 11 13 15 17 19
LC L=-1.965

• Initially monitor project performance using

O bser vation

4.8 1
1 limits.
3.6
U C L=4.214
• Compute trial control limits after 10 data po
M oving Range

2.4
__
• Revisit control limits after 25 data points or
M R=1.290
1.2
any change in the process.
• Monitor process stability and take necessar
0.0 2 LC L=0
1 3 5 7 9 11 13 15 17 19
O bser vation

actions to remove special cause.

1.
1.
Predict
Predict
Defect Test for Stability
Test of Stability - Individual Chart

5.
4 2. Rule no. Rule Voilation ( Yes/No) Remark
5. What-If
What-If 1 One or more points outside of the control limits
Improvem Analysis & 2 Seven successive points on the same side of the centerline
ent Plan 3 Seven successive points that increase or decrease
Validation
Validation Preventio
Preventio 4 Non-random patterns such as trends, cycles, or an unusual spread of points within the control limits ( 3 or more)
Defect
n 5 Several points near a warning or control limit. ( 2 or more)
Management
Management n
Test of Stability - Moving Range Chart
Life Cycle

4.
4. 3.
3.
1 One or more points outside of the control limits
Note to GD: Elements on
Defect
Defect
Causal
Causal
Collect
Collect
Defect
Defect
this page will be played out
Analysis & and
Sub related on the last page itself in
Process
Process data
data &&
assignable Monitor continuation.
 Collect Defect Data and Monitor Sub Process (cont.)

Control Charts
• Used to distinguish between process variation resulting from common
causes and variation resulting from special causes.
• Used to graphically represent the variation in a process over time.
• Used to focus attention on detecting and monitoring process variation
over time.

1.
1.
Predict
Predict
Defect

2.
5.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect Preventio
Preventio
Management
Management n
n
Life Cycle

4.
4. 3.
3.
Note to GD: Elements on
Defect
Defect
Causal
Causal
Collect
Collect
Defect
Defect
this page will be played out
Analysis & and
Sub related on the last page itself in
Process
Process data
data &&
assignable Monitor continuation.
 Collect Defect Data and Monitor Sub Process (cont.)

Control Charts: Rules

To detect lack of statistical control, follow the given rules:
• Rule 1: One point should fall outside the  3 Sigma control limits.
• Rule 2: Seven successive points should fall on
the same side of the centerline. R
• Rule 3: Seven successive points should
increase or decrease. U
• Rule 4: Two out of three successive points
should both be on the same side of the
centerline and outside the 2 Sigma zone.
L
• Rule 5: Four out of five successive points E
should both be on the same side of the
1.
1.
Predict
Predict
Defect
centerline and outside the 1 Sigma zone. S
• Rule 6: Other non-random patterns such as
2.
5.
5. What-If
What-If trends, cycles, or an unusual spread of points
Improvem Analysis &
ent Plan should remain within the control limits.
Validation
Validation Defect Preventio
Preventio
Management
Management n
n
Life Cycle

4.
4. 3.
3.
Note to GD: Elements on
Defect
Defect
Causal
Causal
Collect
Collect
Defect
Defect
this page will be played out
Analysis & and
Sub related on the last page itself in
Process
Process data
data &&
assignable Monitor continuation.
 Causal Analysis and Resolution

2 Defect causal analysis & s

analysis pop up:
1. • To identify the root caus
Predict
Defect
statistical techniques:
o Pareto analysis
o Fishbone analysis
2. o Why-Why analysi
5. What-If
Improvemen Analysis &
t Validation Plan
Defect Prevention
Management
Life Cycle

4.
Defect 3.
Causal Collect
Analysis & Defect and
Sub Process related data
1 assignable & Monitor
causal Sub Process
analysis
 Causal Analysis and Resolution (cont.)
Causal ana
Resolution
process to im
quality and pr
preventing the
of defects int
2

1. Reference Images for Goals and Tools

Predict
Defect

2.
2.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect
Defect Preventio
Preventio
Management n
Life Cycle

4.
4. 3.
3.
Let us learn about
Defect
Causal
Collect
Defect
them in detail. 6 1
Analysis & and
Sub
Sub related
related
Process data &
assignable
assignable Monitor
Monitor
causal
causal Sub
Sub
 Causal Analysis and Resolution (cont.)

Goals

Goal 1: Determine Causes

of Defects

Goal 2: Address Causes of

Defects

1.
Predict
Click each tab to learn more.
Defect

2.
2.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect
Defect Preventio
Preventio
Management n
Life Cycle

4.
4.
Defect
3.
3.
Collect
Note to GD: The chart which is
Causal
Analysis &
Defect
and to branch out from these goals
Sub
Sub related
related
Process
assignable
assignable
data &
Monitor
Monitor
is given on the next slide.
causal
causal Sub
Sub
 Note to GD: Audio andCausal Analysis and Resolution (cont.)
treatment for this given in last
slide.
Goals Defects & Problem
2

3 Select defect data

for analysis
Goal 1: Determine Causes
of Defects

Goal 2: Address Causes of 5

Defects

1.
6 Implement Action
Predict Proposals
Defect

2.
2.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect
Defect Preventio
Preventio
Management n
Life Cycle OID
Note4.4. to GD: Please 3.
recreate
chart
3.
as per styleCollect
Defect
Causal
conventions
Defect
7 Action & Improv
Analysis &
followed
Sub
Sub elsewhereand
related
related in the Proposals
Process data &
assignable
assignable
causal
causal
course.
Monitor
Monitor
Sub
Sub
 Causal Analysis and Resolution: Determine Causes of Defects

1 Step 1: Select the defects and problems for analysis

2 Defects 3 Problems
• Defects reported by the • Project management problem reports
customer. requiring corrective action.
• Defects reported by end • Process capability problems.
users.
• Defects found in peer • Process duration measurements.
reviews.
• Defects found in testing. • Earned value measurements by
1.
process (e.g., cost performance index).
•
Predict
Defect Resource throughput, utilization, or
2.
2.
response time measurements.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect
Defect Preventio
Preventio
Management n
Life Cycle

4.
4. 3.
3.
Defect Collect
Causal Defect
Analysis & and
Sub
Sub related
related
Process data &
assignable
assignable Monitor
Monitor
causal
causal Sub
Sub
 Causal Analysis and Resolution: Determine Causes of Defects (Cont.)

1 Step 2: Determine which defects and problems will be analyzed further

Process Capability
Pareto Analysis
Analysis
1.
Predict
Click each tab to learn more.
Defect

2.
2.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect
Defect Preventio
Preventio
Management n
Life Cycle

4.
4. 3.
3.
Defect Collect
Causal Defect
Analysis & and
Sub
Sub related
related
Process data &
assignable
assignable Monitor
Monitor
causal
causal Sub
Sub
 Causal Analysis and Resolution: Determine Causes of Defects (Cont.)

Step 2: Determine which defects and problems will be analyzed further

Pop Up Header Pop Up Content
2. Determine which defects and problems will be analyzed further
Pareto Analysis •Used to identify vitals defects having maximum
occurrence.
•Defects are further analyzed to know their root causes.

Process Capability •Conducted to identify the defect metrics which a

Analysis project needs to control.
•Defect metrics are identified and analyzed
Process using the
Capability
ParetoProcess
AnalysisPerformance Model or PPM.
Analysis
1.
Predict
Predict
Defect
Click each tab to learn more.
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
Management n
Life
Life Cycle
Cycle

4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable
assignable Monitor
Monitor
causal Sub
analysis Process
 Causal Analysis and Resolution: Address Causes of Defects

1 Step 3: Perform causal analysis and propose actions

1 2 3

Click each image to learn more.

1.
Predict
Predict
Defect
Defect

2.
5.
What-If
Improvem
Improvem Analysis
Analysis &
&
ent Plan
Validation Defect
Defect Preventio
n
Management
Life
Life Cycle
Cycle 2 Click the Causal analysis
icon to learn more.
template
4. 3.
Defect Collect
Causal
Causal Defect
Defect
Analysis
Analysis &
& and
and
Sub related
Process data &
assignable
assignable Monitor
Monitor
causal Sub
analysis Process
1

Pareto Analysis
• Is based on the classic 80/20 rule.
• Helps to observe the frequency of occurrence of defect types and problems.
• Helps to prioritize defect type or problem for further analysis.
• Depicts the frequency distribution of defects against
different defect types in ascending order.
• Helps in identifying the largest and least contributing
defect type.

—X axis = Defect Types

—Y axis = Count of Defect
—Trend line = Cumulative defects across different
defect types

Close
2

Fishbone Analysis
Determine which defects and problems will be analyzed further
•Also called the Cause and Effect diagram.
• Used to visualize, clarify, link, identify and classify possible causes for a
defect type or problem.
• Helps identify causes for defect types and problems in an orderly way.
• Is a highly qualitative technique that requires involvement from team for brainstorming the
causes.
• Causes can be classified as:
o Man
o Machine
o Method
o Materials
o Mother Nature Next
 Note to GD: Please recreate chart as
per style conventions followed
elsewhere in the course.
2

Fishbone Analysis
Determine which(Cont.)
defects and problems will be analyzed further
Lack of Functionality Understanding • Main bones = Major causes
─ Indicate lack of functionality and
Functionality of code not design aspect understanding
considered
• Peripheral bones = Sub causes
Incorrect/ ─ These contribute to the main
Missing Logic causes
Lack of Program
knowledge

Missed out in analysis

Lack of Design Aspect Understanding
Close
3

Why Why Analysis

Determine which defects and problems will be analyzed further
•Used to determine the root cause of a problem.

•Used to drill down from a macro level cause to micro level cause contributors.

Defect /
Failure Type Why 1 Why2 Why 3 Why 4 Root Cause
Incorrect / Lack of Understanding Lack of understanding of  Lack of proper Lack of proper
Missing Logic of design aspects functionality analysis of analysis of
requirements and requirements
understanding the and
functionality understanding
the functionality

Close
 Causal Analysis and Resolution: Address Causes of Defects (Cont.)

oal
Y 2
et G
me
3 u e s to Predict Overall Defect
X val
ry Density (y)
Va
Predicted Defect Density (y)
7 higher than project goal

Sub process goal not Sub process not

4 met capable

6 10
5 11
Probability to meet Perform Causal analysis Verify Code Review sub process
Code review Defect Resolution capable of meeting the goal
density Sub process not stable
9
1. Code Review Defect Density - Module level
6 1

Predict U C L=4.895
Indiv idual Va lue

Defect 2

0 2 2
_
X=1.465

2. -2 LC L=-1.965

8
1 3 5 7 9 11 13 15 17 19

5. O bser v ation

What-If
4.8 1

U C L=4.214

prov
Moving Range

3.6

Analysis
Analysis
2.4

ent
__
1.2 M R=1.290

dati
on
on
Defect
Manageme
&
& Plan
Plan
Preventi
0.0
1 3 5 7 9
2

11
O bser v ation
13 15 17 19
LC L=0

1
on
4. nt Life Cycle
3.
on
Statistically monitor code
3.
Defect
Causal
Collect
Collect Review Defect Density
Defect
Analysis
and
&
& Sub
Sub
Process
related
related
data &
Quantitative Project Management: Process
assigna
assigna Monitor
 Causal Analysis and Resolution: Address Causes of Defects (Cont.)

1 Step 4: Implement selected action proposals

Some examples of action proposals are: 2

• Provide training to deal with common
problems and techniques for preventing
2 them.
• Change a process so that error-prone
steps do not occur.
• Automate all or part of a process.
• Reorder process activities.
• Add process steps to prevent defects, such
1.
as task kickoff meetings to review
Predict
Defect
common defects and actions to prevent
5.
2.
What-If
them.
prov
Analysis
Analysis
ent
&
& Plan
Plan
dati Defect Preventi
on
on Manageme on
on
4. nt Life Cycle
3.
3.
Defect Collect
Causal Collect
Defect
Analysis
and
&
& Sub
Sub related
related
Process
data &
assigna
assigna Monitor
 Improvement Validation

2 Improvement Validation p
• To ensure process stabil
1. process performance.
Predict • To validate improvemen
Defect
performance, use Hypot

2.
5. What-If
Improvemen Analysis &
t Validation Plan
Defect Prevention
Management
Life Cycle

4.
Defect 3.
Causal Collect
Analysis & Defect and
Sub Process related data
1 assignable & Monitor
causal Sub Process
analysis
 Improvement Validation (cont.) Note to GD: Click on image
and click Reset Picture to
get the actual resolutions.
Statistically Manage Sub Process Performance Do not re-create these. Use
the same charts.
1 Process Capability
1
To manage sub process performance:
 Calculate capability using Z or CP/ Cpk (only
process).
2  Perform Causal Analysis and Resolution if th
process is not capable of meeting sub proc
goal (Z <3).
 Statistically validate the process improveme
 Revisit the process performance model base
on actual x values.
 Calibrate the PPM at the project closure.
Causal Analysis & Resolution
1.
Predict
Defect

2.
2.
5.
Improvem
What-If
What-If
Analysis &
3
ent Plan
Validation
Validation Defect
Defect Preventio
Preventio
Management n
Life Cycle

4.
4. 3.
3.
Defect Collect
Causal Defect
Analysis & and
Sub
Sub related
related
Process data &
assignable
assignable Monitor
Monitor
causal
causal Sub
Sub
 Improvement Validation (cont.)

1
4

2
1.
Predict
Defect

2.
2.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect
Defect Preventio
Preventio
Management n
Life Cycle

4.
4. 3.
3.
Defect Collect
Causal Defect
Analysis & and
Sub
Sub related
related
Process data &
assignable
assignable Monitor
Monitor
causal
causal Sub
Sub
 Improvement Validation (cont.)

Evaluate the effect of changes on project performance

Once the changed process is deployed across the project, check the effect of
1 the changes.
This is to ensure that the process change has corrected the problem and
improved performance.

2
1.
Predict
Defect

2.
2.
5. What-If
What-If
Improvem Analysis &
ent Plan
Validation
Validation Defect
Defect Preventio
Preventio
Management n
Life Cycle

4.
4. 3.
3.
Defect Collect
Causal Defect
Analysis & and
Sub
Sub related
related
Process data &
assignable
assignable Monitor
Monitor
causal
causal Sub
Sub
 What is the
significance of
When should you
How can you adhering to the
view the Defect
check for Process
Why are Prediction Model
variations performance
statistical worksheet?
between Model?
tools used? When should
predicted and
you use the
actual defects?
2 C2.0 defect
tracking flow? Note to G
to be sho
Submit bu
Collect Defect and
Predict Defect
What-If Analysis & related data & Defect Causal Improvement the next
Plan Prevention Monitor Sub Analysis Validation the corre
2a Process Submit
Drag and drop the correct sentences in each of the boxes. Click Submit when you’re done.

You have learned that

the defect management
life cycle includes five
1 stages and uses several Improvement Validation

statistical tools for Defect Causal Analysis

Collect
Collect Defect
Defect Data
Data &
&
Monitor Sub
Sub process
effective project
Monitor
What-If process
What-If
Analysis
Predict
management. 1a Defect
66
 What is the
significance of
When should you
How can you adhering to the
view the Defect
check for Process
Why are Prediction Model
variations performance
statistical Note to GD: The OST to be shown if worksheet?
between Model?
tools used? When should
predicted andthe learner chooses the wrong answer
you use the
actual defects? is provided in the speaker note.
2 C2.0 defect
tracking flow?
That’s correct!
Collect Defect and
view the Defect
What-If Analysis
• &The Defect Prediction
related data & Model worksheet
Defect Causal Improvement
is used to predict defects.
Predict
Model •
Plan Prevention The Process Performance Model must be followed to manageValidation
a project
Monitor Sub Analysis
quantitatively and prevent defects.
2a Process
• The C2.0 defect tracking flow is used to collect defect data for further analysis. Submit
cance of • Relevant statistical tools must be used to conduct a causal analysis.
ocess • Variations between predicted and actual defects must be checked to validate
el? Drag and drop the correct sentences in each of the boxes. Click Submit when
improvements in process performance.
you’re done.
use the
Close
ng flow?

l tools used?
You have learned that
the defect management
k for
n predicted life cycle includes five
?
1 stages and uses several Improvement Validation

statistical tools for Defect Causal Analysis

Collect
Collect Defect
Defect Data
Data &
&
Monitor Sub
Sub process
effective project
Monitor
What-If process
What-If
Analysis
Predict
management. 1a Defect
67
 What is Defect Metrics?

3a
Defect metrics are procedures through which defects data of a project are measured and
represented.

This is where you

need to learn about
After all the prediction Defect Metrics.
and planning, how do
2a
I measure or calculate
defects? Defect
2 Metrics?
What is that
all about?
3

1 1
 Note to GD: The pop up for
Types of Metrics element 4 is provided on the next
1 2 slides.
Defect Removal Defect Density by
Defect Leakage Review Efficiency Efficiency Effort /Size(Un-
Weighted)

Defect Density by Delivered Defect Density

Residual Defect Density
Effort /Size(Weighted) by Effort /Size
by Effort /Size

For more information on metrics, go to

https://c20search/Process%20Space/inc/Docs/DeliveryMgmt/QGDM-METRICS.pdf

Click each defect

metric to view its
description.
2
 Types of Metrics (Cont.)
Pop up header Pop up text
• Indicates the review/testing process.
• Calculates defects attributed to a particular stage, but detected in the subsequent
Defect stage.
• Calculated as:
Leakage Sum((Number of defects attributed to a stage but only captured in subsequent
stages) / (Total number of defects captured in that stage + Total Number of defects
attributed to a stage but only captured in subsequent stages)) *100

• Indicates the efficiency of the review process.

• Calculated as:
Review (Number of Review defects) / (Total number of Review + Testing Defects [including
Efficiency customer reported test defects]

Note: HIGHER THE REVIEW EFFICIENCY, LOWER THE DEFECT LEAKAGE.

• Indicates the efficiency of defect removal by Internal Review and Testing process.
Defect • Calculated as:
Removal (Total number of Pre-shipment Defects)/ (Total number of Pre-shipment Defects +
Total number of post-shipment Defects + Total number of Post production Defects)
Efficiency *100
 Types of Metrics (Cont.)
Pop up header Pop up text

Defect Density by
Effort/Size • Indicates the number of defects per actual effort spent/size of the project.
(Un-Weighted)

• Indicates the number of defects per actual effort spent/size of project considering
Defect Density the weight age of defects.
by Effort/Size • Calculated as:
(Weighted) Overall Defect density = (No. of major defects + (minor defect/2) + (superficial
defect/10))/Total overall actual effort spent

• Indicates the external number of defects per effort spent/per size of the project.
Delivered Defect
• Calculated as:
Density by Effort/Size
No. of defects after shipment (including production) / Total effort

• Indicates the number of post production defects per effort spent/per size of project.
Residual Defect Density • Calculated as:
by Effort /Size
Total Post-production defects / Total actual effort spent
Drag and drop the correct metrics for each of the descriptions given below.
Click Submit when you’re done.

Indicates the external number of defects per effort spent/per size

of the project.

Calculates defects attributed to a particular stage, but detected in

the subsequent stage.

Indicates the efficiency of defect removal by Internal Review and

Testing process.

Indicates the number of post production defects per effort

spent/per size of project.

1 Submit
You have learned that you can calculate defects at different stages using
different metrics. Let us check your understanding on how well you can
identify defect metrics.
That’s correct!
• Delivered Defect Density by Effort/Size helps to indicate the external number of
defects per effort spent/per size of the project.
• Defect Leakage helps calculate defects attributed to a particular stage, but
detected in the subsequent stage.
• Defect Removal Efficiency helps to indicate the efficiency of defect removal by
Internal Review and Testing process.
• Residual Defect Density by Effort /Size helps to indicate the number of post
production defects per effort spent/per size of project.

Not quite right.

• Delivered Defect Density by Effort/Size helps to indicate the external number
of defects per effort spent/per size of the project.
• Defect Leakage helps calculate defects attributed to a particular stage, but
detected in the subsequent stage.
• Defect Removal Efficiency helps to indicate the efficiency of defect removal by
Internal Review and Testing process.
• Residual Defect Density by Effort /Size helps to indicate the number of post
production defects per effort spent/per size of project.
 Impact of Defects on Project Performance
Case Study

2 • A Java based project has an initial predicted defect count of 450.

• During the Defect Prevention Plan development, defects got distributed across
Requirement, Analysis, Design, Coding and other stages and a prevention plan was
identified.
• 20 defects leaked during requirements to system testing, 15 defects leaked during
design to system testing and 70 defects leaked during coding to system testing.
• Total count of pre-shipment defects detected before delivery was 525 and post
shipment defect count is 100.

1
 Impact of Defects on Project Performance (Cont.)

2 Here’s how:
– Any defect leakage to a subsequent life
cycle stage increases re-work effort.
– Any defect post fix undergoes another
round of testing, increasing testing effort.

Therefore, defects impact the following:

– Overall defect density of the project and
other defect related metrics like DRE,
DDD etc.
– Overall actual effort spent in the project
by increasing effort variation.
– Project productivity in terms of size and
effort. 1
– Cost of quality, since rework and appraisal
effort is more.
– Project schedule.
 Scenario

2
1
Scenario Solution
N
Click each component to learn more.

d
 Scenario
Pop-up for Scenario
Rohan is a project manager for a maintenance project, running in steady state.
He is focused on team performance and delivering zero defect product to customer.
To achieve this, he continuously monitors his project goals.
Recently he revised his project goals based on actual project data. He fixed his new goals as a
small improvement over his current performance.
The Defect Injection Rate goal was fixed at 0.052 defects/PH. Rohan's team worked on a
minor enhancement for 274 hours.
Before delivery he noted with satisfaction that only five defects
were injected in the request. Two of them were caught in reviews
and three in testing. He was particularly happy because he was a
little bit tight on the schedule for this request. After delivery, he is
shocked to find the customer report six defects in the acceptance
testing.

How can you help Rohan avoid such issues in future?

Close
 Scenario
Pop-up for Solution

As per estimates, the estimated defects is 0.052 * 274 =14 defects.

In reviews and testing, Rohan's team was able to detect only five defects.
Rohan would have noticed this had he used the Defect Prediction model.
In this case, Rohan would have analyzed why less defects were detected.
Was it because of really good code or bad review/testing.
Also, he would have realized that inefficient review/testing was the
problem and that one more round of review/testing can prevent AT
defects.

To summarize,
• Rohan should have applied the Defect Prediction Model
• Had he done so, he would have noticed the deviation in
estimated vs. actual defects and would have acted on it.

Close
 Quiz
Interactivity: MCQ (Multiple Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
1. Which of the following phases in the project lifecycle are prone to defect injection?  
1. Requirement  
2. User Acceptance Testing  
3. Design  
4. Coding
Answers: 1, 3 and 4 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Quiz
Interactivity: MCQ (Single Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
2. Which of the following is a high priority defect?  
1. Symptoms causing dehumanizing system behavior.  
2. Misleading or redundant outputs.  
3. Symptoms requiring all further development and testing to be stopped till defect is repaired.  
4. Symptoms where defect can be resolved in a major system revision in the future.
Answers: 3 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Check if this can be changed
Quiz from MCQ to sequencing.
Interactivity: MCQ (Single Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
3. Which of the following is the correct sequence of steps in the Defect Management Life Cycle?  
1. Predict Defect> Collect Defect Data> What-If Analysis> Improvement Validation>Causal Analysis  
2. Predict Defect> What-If Analysis> Collect Defect Data> Causal Analysis> Improvement Validation  
3. Collect Defect Data> What-If Analysis> Predict Defect> Causal Analysis> Improvement Validation  
4. Causal Analysis> Collect Defect Data> What-If Analysis> Improvement Validation> Predict Defect
Answers: 2 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Quiz
Interactivity: MCQ (Multiple Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
4. The responsibility of the defect coordinator is to:  
1. Perform root cause analysis of defects at a defined frequency.  
2. Devise tools and methods to avoid defects early in the process.  
3. Identify projects’ top critical defects using standard techniques such as Hypothesis/Pareto.  
4. Ensure implementation of preventive actions.
Answers: 1, 3 and 4 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Check if this can be changed
Quiz from MCQ to sequencing.
Interactivity: MCQ (Single Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
5. Which of the following is the correct flow of tasks for defect tracking in C2.0?  
1. Create Defects> Add or Edit Review and Testing Records> View Defect Details> Enter Resolution Details  
2. Create Defects> View Defect Details> Enter Resolution Details> Add or Edit Review and Testing Records  
3. View Defect Details> Create Defects> Add or Edit Review and Testing Records> Enter Resolution Details  
4. View Defect Details> Enter Resolution Details> Create Defects> Add or Edit Review and Testing Records
Answers: 1 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Quiz
Interactivity: MCQ (Single Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
6. One of the goals of Causal Analysis and Resolution is to:  
1. Implement prevention planning strategies.  
2. Detect defects early in the project life cycle.  
3. Address causes of defects.  
4. Use defect metrics to track defects.
Answers: 3 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Quiz
Interactivity: MCQ (Single Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
7. Which of the following statistical tool is also known as the “Cause and Effect” diagram?  
1. Pareto  
2. Fishbone  
3. WHY WHY  
4. Control Chart
Answers: 2 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Quiz
Interactivity: MCQ (Single Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
8. Which of the given statistical tools contain a trend line to display the cumulative defects across different defect  
types?
1. Fishbone  
2. Control Chart  
3. Pareto  
4. WHY WHY
Answers: 3 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Quiz
Interactivity: MCQ (Multiple Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
9. Which of the following is an ingredient of the Prediction Model for Defect Density?  
1. Controllable Xs  
2. Statistically monitored Xs  
3. Sub process connection  
4. Micro level cause contributors
Answers: 1,2 and 3 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Quiz
Interactivity: MCQ (Multiple Select)
Objective Mapping: Bloom’s Level: Knowledge  
Choose the correct answer from the options below and click Submit.
10. Which of the following criteria are required to statistically manage sub process performance?  
1. Perform a what-if analysis to achieve the desired goal.  
2. Statistically monitor the critical sub processes in PPM, used to predict the probability of meeting project goal(y).  
3. Use suitable control charts.  
4. Monitor process stability and take necessary actions to remove special cause.
Answers: 2, 3 and 4 Remediation:  
Correct Feedback: That is correct. Click Next to continue.  
Incorrect Feedback: 1. That is incorrect. Click Reset to try again.
(Attempt/Options)  
2. That is incorrect. The correct answer is displayed for you. Click Next to
continue.
 
Prompt Text:  
Notes to Developer:  
File Names of the grabs / bitmaps / media files to be used  
 Your Score: <<70% and above >>

Great Job!
You passed with flying colors.
You are all set to manage risks in your next project.

Your Score: <<0 – 60%>>

Sorry!
You need to get a score of 70% and above to pass the quiz.
You can visit the course again to manage risks better in your next project.
 Summary Note to GD: Populate the
Here’s a brief summary text within the
recap of what blackboard.
we have learned
in this module. 1

– A defect is a failure to conform to requirement and meet acceptance criteria of customers.

– Defects can be classified based on common sources and types.
– The DP Coordinator is responsible for preventing defects arising out of the development
process.
– The five steps in the defect management life cycle are:
• Predict defect
• Conduct a what-if analysis and plan prevention
• Collect defect data and monitor sub-processes
• Conduct a causal analysis, and
• Validate improvement in process change.
– The PPM helps to ensure quantitative project management.
– The C2.0 defect tracking flow includes tracking and viewing defects and then entering
resolution details.
– A CAR is used to identify and address causes of defects.
– CAR uses statistical tools such as Pareto Analysis, Fishbone Analysis and 5 WHY analysis to
achieve its goals.
– Defects can be calculated at different stages using defect metrics.
 Reference

Sl No. Name of the training Code Contents

Defects upload &
1 How do I track defects using C2 BQTLD8 tracking in SWB

How can I Upload Defects in bulk to Bulk upload of

2 the Cognizant 2.0 Application BQTLE3 defects

Guidelines on How to Access eLearning Materials in ELM

1. https://compass.learning.cognizant.com The Enterprise Learning Management (ELM) page

appears.
2. Enter the details, as required.
3. Click [Sign In]. The Self-Service page appears.
4. Click Browse Catalog. The Browse Catalog page appears.
5. Click Process and Quality. The Learning Catalog>>Process and Quality page appears.
6. Click Cognizant 2.0. The Learning Catalog>>Process and Quality>>Cognizant 2.0 page
appears.
7. Check out the relevant course from the list provided.

91
 Contact US

For more information

or clarification on
defect management,
reach out to us.

ODAG Team
[email protected]

92
 Congratulations

Congratulations!

You have successfully

completed the module on
Defect Management.