Checklist Final Inspection
Checklist Final Inspection
Checklist Final Inspection
I Objective
- To guarantee the quality and integrity of the components to be released
- This activity is applied for all releases to customer (especially mandatory for the ones planned in work
order (WO))
II How to use
Step 1. Quickly study the work flow of final inspection (FI) activities of a QA
START
Plan for FI
Customize FI checklist
(Develop acceptance criteria
& specific items)
Check FI
Pre-conditions
N
Satisfied?
Do FI
FI results
N
Satisfied?
FINISH
Step 4. Fill the comments you find in the 'Note' column if any
Step 5. Make your suggestion based on the comments in Note column and the summary
- PASS if the items with mandatory priority are marked 'OK'
- NOT PASS if at least one of the items with mandatory priority is marked 'NOK'
- OTHER if 02 suggestions above can not be applied. However, the more detailed notes
should be written down
Notes 1. For the items with optional priority, if they are marked 'NOK', the follow-up actions and
deadline should be written down
2. For the release of documents only, if the content update is not more than 20% (based on
updated/ total pages), FI can be skipped
3. For unplanned releases, PM must contact QA at least one day before FI time to get the
commitment
4. In case the release does not pass the final inspection
- QA suggests “STOP the release or NOT” to PM.
- If PM does not agree with this result, QA will get the consultancy and decision from QA
Leader.
- QA Leader is responsible for reviewing the result and giving the final decision “STOP the
release or NOT”.
- PM can deliver only if there is evidence that customer or QA Leader agrees for this case.
- A penalty point is given for each release without the permission
Are acceptance criteria defined clearly for the release? DOC/ SC NOK
Are the evidences, proving team has conducted quality control for the
DOC/ SC OK
deliverables, available?
Pre-conditions
The filled-up review checklist and test report for source code? SC NOK
Do the items listed in the Release note correspond with the actual
DOC/ SC OK
deliverables?
mandatory reviewer?
Does Release note specify Number and details of the sources
DOC/ SC
released and/ or List of accompanying documents?
Have all defects/ issues been closed in the release scope? DOC/ SC
If no, are they listed in Release note
DOC/ SC
with their clear description, action and deadline ?
Has the latest version of anti-virus been used for virus control? DOC/ SC
* Summary
Number of 'OK' items 5
Number of 'NOK' items 2
Number of 'N/A' items 1
* Suggestion
[ ] - Pass
[ ] - Not pass
[ ] - Other
Summary Percentage
Number of 'OK' items 3 75%
Number of 'NOK' items 1 25%
Number of 'N/A' items 0 0%