QA Activities and Deliverables within the Delivery Lifecycle

Each of the five phases of Project Delivery Lifecycle will incorporate QA activities and deliverables that off-set the risks of common project problems. This summary of the Project Delivery Lifecycle incorporates a high-level list of the QA activities and deliverables associated with each phase.

Assessment Phase

Assessment process consists of market research and a series of structured workshops that and the client teams participate in to discuss and analyze the project objectives and develop a strategic plan for the effort. The products of these meetings, combined with market research, form the basis for the final output of the assessment: a tactical plan for realizing specific business and project objectives.

v QA Deliverables

QA Editor submits revised and approved deliverable documents

Planning Phase

In the Planning phase, the team defines specific system requirements and develops strategies around the information architecture (static content and information flows) and the business functions that will be addressed.

QA Activities

Establishing Standards and Procedures: QA records the set requirements

Planning (Test Matrix): QA develops a test matrix QA confirms that all set

requirements are testable and coincide with the project objectives

Auditing Against Standards and Procedures: QA editor edits the

documents and confirms that they meet the objectives and the quality

standards for documents

Establishing Completion Criteria: QA records the completion criteria for

the current phase

QA Deliverables

QA submits an initial test matrix

QA Editor submits revised and approved deliverable documents

Design Phase

During the Design phase, the team identifies all of the necessary system components based on the requirements identified during the Assessment and Planning phases. The team then creates detailed design specifications for each component and for the associated physical data requirements.

QA Activities

Auditing Standards and Procedures: QA confirms that all designs meet the set requirements and notes any discrepancies. Additionally, QA identifies any conflicts or discrepancies between the final design of the system and the initial proposal for the system and confirms that an acceptable resolution has been reached between the project team and the client.

Planning (QA Plan, QA Test Plan):

· QA begins developing the QA Plan

· QA revised the test matrix to reflect any changes and/or additions to the system

QA Deliverables

QA presents the initial QA test plan

QA submits a revision of the test matrix

Development Phase

During the Development phase, the team constructs the components specified during the Design Phase

QA Activities

Planning (Test Cases): Using the test matrix, QA develops a set of test cases for all deliverable functionality for the current phase

Prepare for Quality Assurance Testing:

· QA confirms that all test cases have been written according to the guidelines set in the QA test plan

· Quality Assurance works closely with the Configuration Management group to prepare a test environment

QA Deliverables

QA submits a set of Test Cases

QA Environment is set up

Implementation Phase

In the Implementation phase, the team focuses on testing and review of all aspects of the system. The team will also develop system documentation and a training or market test plan in preparation for system launch.

QA Activities

¨ QA Testing: QA executes all test cases in the QA testing cycle

QA Deliverables

¨ Test Results

¨ Defect Reports