Introduction to Quality Gate Review Checklist

I. Objectives
- To verify objectives of project stages/milestones/processses against project target and plan
- To evaluate project performance against project target and plan
II. How to use

1. Work flow

Quality Gate Review

Project QA

Customize Quality
Lead

Gate Review Assign & Train

Checklist
Assigned QA

Conduct Stage/
Summarize Report Quality Get confirmation
Milestone Evaluate Project Log issues to Follow-up
Quality Gate Gate Review on issues and
Accomplishment Performance PMS (Process_Correction)
Review Result Result corrective actions
Verification

2.2 Steps
Step 1 Develop Quality Gate Review Checklist

Project QA Lead customizes Quality Gate Review Checklist specific for the project based on customer requirement, WO, QA Plan and the standard Quality
Gate Review Checklist. This activity shall be conducted within 15 days from the Project Start Date.

- Mark N/A for items that are approved to be waiver for the project. Reason for N/A must be recorded in column "Observation" and correspondent
tailoring/deviation must be recorded in FI and be reviewed and approved by authorized persons in accordance with Guideline_Process Tailoring prior to
the implementation.

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 1/15

 Note: It is recommended to insert additional checked items at BOTTOM of the checklist. Other checklists could be combined with the Quality gate review
checklist to verify specific items of the stage/phase/steps.

Step 2 Conduct Stage/Milestone Accomplishment Verification

Project QA verifies accomplishment of the defined stages/milestones/processes using the checklist in sheet "Milestone Verification", then mark 'OK', 'NOK',
or 'NA'
- 'OK' means that the item content is in the project work, mandatory requested for checking, and is satisfied

- 'NOK' means that the item content is in the project work, mandatory requested for checking, and is
NOT satisfied

- 'N/A' means that the item content is out of the project work, therefore it does not need checking

- Record your detail observations/comments in 'Observation' column

Step 3 Evaluate Project Performance

Project QA evaluates performance of the defined stages/milestones/processes using the sheet "Performance Evaluation".

Step 4 Summarize Quality Gate Review Result

Project QA summarizes result of quality gate review, identify issues and suggestions using the sheet "Quality Gate Summary Report".
Step 5 Report Quality Gate Review Result

Project QA sends Quality Gate Review Result to Project QA Lead, SM, PM and other relevant persons to get confirmation on issues and corrective actions.
If there is a conflict of opinion, escalate the issue to Project QA Lead, QA Lead for resolution.

Step 6 Follow up

Project QA logs issues detected into PMS and follow up the issues & corrective actions to closure in accordance with Process_Correction and
Process_Prevention. Escalate to appropriate QA Leader, QA Manager when the issues not resolvable with the responsible people or when the issues are
pending more than 1 week from the deadline.

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 2/15

III. Guideline for Project Performance Evaluation

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 3/15

1. Purpose
Purpose of the document is to provide guidance and template for Project Performance Analysis Report. The
report is usually prepared by PM and QA at the end of critical steps/phases/stages to thoroughly evaluate
project performance at the current step/phase/stage before making decision of moving to next
steps/phases/stages or not and define necessary actions to be taken later on. It describes project performance
in a quantitatively manner using pre-defined metrics.

2. Guideline
Normally, a project performance analysis report contains four main parts as following:
- Header of report
- Quality evaluation
- Cost evaluation
- Delivery evaluation
- Conclusion
- Suggestions
2.1 Header of Report
This part provide brief information of project and the report
2.2 Quality Evaluation
Target Value: the information could be gotten from PM. It is normally recorded in standards supplied by
Customer or Work Order, Project Plan

Actual Values: the information is gotten from PM, or gotten from project records (DMS or equivalent - Defect)

Analysis:

1) Comparing actual performance against target for quality related metrics (defect rate, number of
defects found, % of defect detected, leakage, etc), you can evaluate whether the project performance
reaches the target or not. If deviation between the actual performance and the target >10% (this
threshold could be customized by projects), causal analysis/explanation is required.

Serious If actual value is better than or equal to the target.

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 4/15

 actual value is worse than the target but there is no impact to the next step/phase/stage.
Medium
For example: actual project size is lower than planned.
If it’s actual value is worse than the target and it will affect to next step/phase/stage
Cosmetic
quality.
2) Identify common defect type and location using Pareto chart
3) Analyze root causes of defects, then identify the most common defect causes => determine
action/solution to be taken for next period.

2.3 Cost Evaluation
Target Value: the information could be gotten from PM. It is normally recorded in standards supplied by
Customer or Work Order, Project Plan
Actual Values: the information is gotten from PM, or gotten from project records (Effort Efficiency, Effort
Effectiveness, Productivity, Effort distribution, etc).
Analysis:

Comparing actual performance against target, you can evaluate whether the project performance
reaches the target or not. If deviation between the actual performance and the target >10% (this
threshold could be customized by projects), causal analysis/explanation is required.
Serious If actual value is better than or equal to the target.
Actual value is worse than the target but there is no impact to the next step/phase/stage.
Medium
For example: actual project size is lower than planned.

Cosmetic If it’s actual value is worse than the target and it will affect to next step/phase/stage quality.

2.4 Delivery Evaluation
Target Value: the information could be gotten from PM. It is normally recorded in standards supplied by
Customer or Work Order, Project Plan

Actual Values: the information is gotten from PM, or gotten from project records (Project schedule - Delivery)

Analysis:

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 5/15

 Comparing actual performance against target for schedule related metrics (Timeliness, schedule
deviation, etc), you can evaluate whether the target is satisfied and the project performance reaches the
target or not. If deviation between the actual performance and the target >10% (this threshold could be
customized by projects), causal analysis/explanation is required.

Serious If actual value is better than or equal to the target.

Actual value is worse than the target but there is no impact to the next step/phase/stage.
Medium
For example: actual project size is lower than planned.

Cosmetic If it’s actual value is worse than the target and it will affect to next step/phase/stage quality.

2.5 Conclusion

Basing on evaluation result on project performance in term of Q-C-D, the author has to make a conclusion on
project performance in the report period. The project performance could be summarized in "Traffic Light
Reporting" format to provide quick snapshots to the reader on the project status and drive the readers to pay-
attention on important issues.

2.6 Suggestions
Basing on project performance evaluation result, the author has suggestions to the project. Action/solution is
mandatorily required if evaluation result is "Not pass"

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 6/15

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 7/15
10e-CL/PM/HDCV/FSOFT v2/3 Internal use 8/15
10e-CL/PM/HDCV/FSOFT v2/3 Internal use 9/15
 Quality Gate Review Report
Project Code Report Date <dd-mmm-yy>
<Basic design of Batch 1 from
Conducted by Report Period
10-Mar-2010 to 02-Apr-2010>

1. Conclusion
<Summarize conclusions get from Milestone Verification & Performance Evaluation here>
a. Stage/Milestone Accomplishment
[x] Satisfied [] Un-Satisfied [] Other
Enter rationale to derive to the conclusion "Not Achieved" or "Other"

b. Project Performance
Quality Cost Delivery

2. Issues & Suggestions

<List issues together with your suggestions. It is mandate for "Un-Satisfied" of Stage/Milestone Accomplishment or Project Performance highlighted in RED >

Raised
No Project Code Customer PM AM QA Issue Description Cause Impact
Week

<Add more row if needed>

Note: Manadatory to fill

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 10/15

 Action requested by Target Actual
Severity PIC Status Actual Date Note
QA Deadline Action

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 11/15

 Verification of Stage/Milestone Accomplishment
Project Code 0 Report Date <dd-mmm-yy>
<Basic design of Batch 1 from
Conducted by 0 Report Period
10-Mar-2010 to 02-Apr-2010>

ID Check Item Assessment Observation Reference

Have objectives/exit criteria of the
stage/milestone/process completely satisfied
and obtained approval of appropriate
person?

Criteria #1

Criteria #2

Criteria #3
Are work products of the
stage/milestone/process completed?

Work product #1

Work product #2

Work product #3

Does the next plan of processes, resource,

effort, schedule, quality ensure good quality
of its outputs?

Is quality of inputs of the next

stage/milestone/process good enough to
ensure good quality of work product of the
next stage/milestone/process?

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 12/15

 Project Performance Evaluation Report
Project Code 0 Report Date <dd-mmm-yy>

Conducted by 0 Report Period <Basic design of Batch 1 from 10-Mar-2010 to 02-Apr-2010>

1. Quality Evaluation
1.1 Metrics

No. Metric Unit Target Actual Deviation Remark

1 <Unit test Defect Rate> <Wdef/KLOC>

2

1.2 Defect Analysis

<Insert "Defect Distribution by Type" & Defect Ditribution by Module" Charts here. Data can be
extracted from DMS databse>
<Type all descriptions about the chart into this part>
800
- Defect type having the biggest number of defect is……<Coding 700
logic>..., most of which belong to ..<medium> severity. 600
500
- Following ..<coding logic> is …<business logic>…. 400
….etc…. 300 Fatal
200
Serious
100
Medium
0
ic t r) Cosmetic
ic
ar
d
r it
y
su
e
en ssin
g er in
g ce
log log d eg i s m i the Oth n d r fa
s g n t cu O e
es in sta e in esig
n
Do ure
m y( sta r Int
usin Cod ing as D t alit d er se
B d ab a on n U
Co Dat Fe cti isu
- n m
ta Fu Re
q
Da

1.3 Defect Cause Analysis

<Insert Pareto Charts of Defect Cause here. Data can be extracted from DMS databse>
- The metric …<Unit test Defect Rate>…does not reach/reaches
committed Quality target. The deviation is ….<40%>…..
The main reasons for this are:
+ Process: …<Unit Test Case is not well modified to suit with JUnit &
this project specific business>......
+ Humance Resource:….<7/10 team members are newbie with Unit
Test & with Java>…….
+ Project Management:......<Training class about Unit Test for newbie
was not conducted>......
+ Others: .....<Business of customer's system is very complex to create
10e-CL/PM/HDCV/FSOFT v2/3 Internal use 13/15
good Unit Test Case while system documents that customer supplied
did not contain enough information for development>....
 this project specific business>......
+ Humance Resource:….<7/10 team members are newbie with Unit
Test & with Java>…….
+ Project Management:......<Training class about Unit Test for newbie
was not conducted>......
+ Others: .....<Business of customer's system is very complex to create
good Unit Test Case while system documents that customer supplied
did not contain enough information for development>....
< Type evaluation - root cause for metrics that have been filled
avbove>

2. Cost Evaluation
2.1 Cost Metrics

No. Metric Unit Target Actual Deviation Remark

1 #DIV/0!
2 #DIV/0!

2.2 Effort distribution (could be referred to FI/Effort)

2.3 Analysis
<Enter analysis here>

3. Delivery Evaluation
3.1 Delivery Metrics

No. Metric Unit Target Actual Deviation Remark

1
2
3.2 Deliverable status (could be referred to Project schedule)

1st Committed Last Committed

No. Deliverable Actual Delivery Date Remark
Delivery Date Delivery Date

1
2
3

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 14/15

 3.3 Analysis
<Enter analysis here>

4. Conclusion

Quality Cost Delivery

<Enter the conclusion here>

5. Suggestion
<List issues together with your suggestions>

No. Issue Request for Action Request to Due Date

1
2

10e-CL/PM/HDCV/FSOFT v2/3 Internal use 15/15