| Task: Hand-Off from Development to QA |
| |
Purpose
| To prove the code quality and ensure there are no outstanding critical issues with basic functionality of the system. |
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
| Outputs |
|
Main Description
| When the Developer is finished with coding as per the requirements, it is the Developer's responsibility to hand over the
code to QA for testing purposes. This is a "must" for every in-house development project. |
Steps
|
Developer demonstrates application to QA
| When Dev is ready to deliver the code to QA for testing, there should be a session/meeting between Dev, QA, BA and PM. This
is a Dev’s responsibility and the purpose of that session is, Dev to give a high-level demo on functionality (new) in an
environment similar to QA env. This cannot be in a local env on a developer's machine. |
QA confirms development hand-off
| Upon successful demonstration, QA confirms the hand-off from development 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
|
|