• Background
• Understanding of inpection
• Steps for delivery inspection

Background

The purpose of delivery inspection guideline is to help the project team with delivery inspection techniques for reducing the number of defects in a program before it goes out the door.

Understanding on Inspection

Incorporating inspections into your software engineering process is not free. They can consume between 5 and 15% of the total project budget. However, Inspections shorten delivery time by reducing the time spent in the integration and system test/debug phases, since a cleaner product is passed into those late-stage quality filters. Better quality in the completed product saves on maintenance time, too. With software inspection you can actually reduce the effort that you have to spend fixing bugs after delivery frees up time that can be used for new development work.

Below diagram provides a fair understanding as to when we should do the delivery inspection in the Software Development Life Cycle.

The following guidelines are to be used for Delivery Inspection.

Steps for Delivery Inspection

Project Team (Intial)

• Create deliverables for delivery from the Software Configuration Library.
• Verify completion of all tests, reviews and updates as per SDP/AMP and Project Schedule.
• Verify that the Acceptance Criteria for the Project related to the deliverable are met.
• Initiate Delivery Inspection by handing over all Quality Records e.g. test cases, test reports, list of open bugs, and review records to SQA.

SQA

• Do Delivery Inspection, for evidence, to demonstrate that:
  • - Defects, Change Requests and Non-Conformances related to the item have been tracked to closure.
  • Tests (if any) have been conducted on the item successfully.
  • All the Contractual obligations have been met.
  • Acceptance Criteria for the Project related to the deliverable are met.
• Refer to “Checklist for Delivery Inspection” for delivery inspection.
• Record deficiencies (if any) in SQA Review Report.
• Initiate action on findings as per “Procedure for handling defects” in the “Review Process”.
• Ensure findings have been resolved by Project Team and approve/close SQA Review Report.

Project Team (At the end)

• Prepare list of items for delivery as per Contract and Dispatch the Deliverables with the list to the client.
• Receive Acknowledgment from Client, if applicable.
• Maintain the SQA Review Report in the Project SCM Library.
• SQA will verify all above said items.