| Task: Hand-Off from Requirements to QA |
| |
 |
| During the Execution Phase of the Project, QA will require the knowledge gained through BA’s efforts. Business Analyst will transfer the knowledge by doing the walkthrough of BRD’s and any other corresponding artifacts. |
| Disciplines: Quality Management Discipline |
|
Purpose
| QA to have clear understanding of the requirements before test case development begins. |
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
| Outputs |
|
Main Description
The QA Lead will review all artifacts completed to date by the lead Business Analyst for the project. Business Analyst
will do a walkthrough of the finalized requirements.
Any questions or "gaps" should be discussed and addressed before QA’s acceptance.
|
Steps
|
Review RMM artifacts
The BA will submit artifacts (BRD, other requirements, etc.) to QA for review.
A meeting will be scheduled between QA and the BA. The purpose of the meeting is, BA to walkthrough the finalized
requirements and answer any questions from QA. QA will look at the requirements, both Functional and Non-Functional, and
both business and technical requirements, with an eye toward testability. “Can these requirements be tested?” |
Confirm Requirements handoff to QA
QA confirms a successful handoff of requirements from BA to QA.
|
|
Version and Release
Unified Life Cycle (ULC): 5.1, November 3, 2014
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014
|
|