QUALITY IMPROVEMENT GUIDELINE DOCUMENT

Objective:
Increase the value of DPL by making customers happy.

Summary:
This is a high-level guideline document that will be used to serve the following purposes

A. improve the quality

B. streamline the standard QA process
C. Train QA resources to practice the defined process
D. Adherence to the QA process across the company
E. Identify areas in other processes to improve them

Areas to Cover:
This guideline will cover the following two areas;

A. Quality delivery as sprint deliverable item

B. Production defect management

Execution Plan:
All the above objectives will be achieved step by step by defining the quarterly goals of each team to
improve their quality by up to 99%.

Phases:

I. Process Defining Phase

II. Training Phase
III. Execution Phase
IV. Compliance Phase
V. Process Handover Phase
VI. Integration with the nGAGE system
VII. Quality Evaluation via nGAGE Reports

I. Process Defining Phase

II. Training Phase
a. Objective
b. Expectation
i. Working Software
1. New Feature Should Work
2. Existing Features Should Work
ii. Minimal Time to Perform UAT
iii. No UAT/PROD Bugs
c. Synchronization with Scrum ceremonies for requirement understanding
d. Give training to the TFS/Jira
e. Test Cases writing
 i.
III. Execution Phase

Sprint Deliverable Items

a. Test case writing consideration

i. Understand and identify the scope of PBI
ii. Perform impact analysis and identify test coverage
iii. Understand the acceptance criteria of PBI
iv. Environment/Precondition
v. Input value
vi. Output value/message
vii. Where to check it

b. Test cases writing Steps

i. Test Case ID
ii. Test Description
iii. Assumptions and Pre-Conditions
iv. Test Data
v. Steps to be Executed
vi. Expected Result – Where to check it
vii. Actual Result and Post-Conditions
viii. Pass/Fail

c. Perform the test steps.

i. Verify the test results as per the defined expected result

ii. If the test is passed:

1. Mark the test case as passed.

2. Stop the test.

3. Add/update relevant information to the test case and PBI

4. Process completed.

iii. If the test is failed:

1. Mark the test case as failed.

2. Add defect with steps to reproduce, support images, video, content, etc.

3. Log the bug and assign the sprint and the team.

4. Add/update relevant information to the test case and PBI

5. Assign back the PBI to the developer

6. Process completed.
 iv. Manual test case execution
v. Automated test case execution
vi. Creation of a package/build via code
vii. Monitor and control deployment on the QA environment
viii. Performance Characterization
d. Manual report generation and extraction
i. Share reports with team
ii. Share reports with management
iii. Share reports with clients

Production Defect Management

A. Production Defect Fixing Process:

1. LOGGING
2. INVESTIGATION
1. Problem definition
2. Problem Nature
3. Impact
4. History
5. Trigger event
6. Scope
7. Impacted modules
8. Frequency/Recency/Volume
9. Supporting logs:
10. Support information:
11. Support documents

3. INVESTIGATION REVIEW
4. QA SCOPE REVIEW
5. DEVELOPMENT
6. DEVELOPMENT REVIEW
7. QA
8. PACKAGE RELEASE
9. CODE MERGING
10. RCA of a code bug and take necessary action to overcome the bug

IV. Compliance Phase

V. Process Handover Phase
VI. System generated report and its Integration with nGAGE
VII. Quality Evaluation via Monthly Reports