Work effort identifying information, document history, & referen

Work Effort Information

Work Effort Name:
Program Name: (if any)
Technical Project Manager:
Project Test Manager:
Local Quality Manager:
T-Code:
PRJ-Code:
Estimated Release Date:
IT Sponsoring Area:
Local Test Manager:
ormation, document history, & references
Electronic Location of this Test Strategy / Master Test Plan
Project Work Plan (MS Project)
Business Requirements
Project Architecture Document
Defect Management Process
 Key Milestones
Key Milestones Planned Start Planned Completion
Detailed Business Requirements
Planning Analysis and Design
Prepare Test Strategy/Master Test Plan
Prepare Test Cases
Finalize the Test Strategy
Testing
Roll Out 1
Roll Out 2
Final Roll Out
Issues and Closing
QA Sign off with Test Results Summary
Test Summary (Summary of Test Results)
Vendor Support Ends On
s
Duration (Months) Task Owner
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
 Scope - Functional/Non Functional
In Scope Out Of Scope
Sl. No Description Sl. No
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 10
11 11
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
20 20
It can sometime be important to explain the extent of testing. If you need to specify that, please briefly describe it over he
tional/Non Functional
Out Of Scope
Description

eed to specify that, please briefly describe it over here.

 Scope - Functional/Non Functional
Sl. No
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Scope - Functional/Non Functional
Description
 Resources and Skillsets
Sl. No Questions
1 Who is on the test team
2 Who is available to test
3 What testing skills are needed for each component (or functional area) to be tested
4
5
6
7
8
9
10
s
Response

ea) to be tested
 Topic
Overview of
product/enhancement

Resources/Skillsets needed

Stakeholders

Electronic Locations of
documents

Test Environments

Scope

Phases of testing

Deliverables

Key Milestones (Timeframes)

Risk

Defect Process

Test Data
 Sub Topic

Product/feature overview
Outlining the product/enhancement
Identify the type of testing to be conducted
List the features and testing (what to test and how to) in a tabular format
Software Testing approach- how do you see the testing being conducted

Are the resources identified and available

What are the required skillsets
List the resources with skillsets

List the key contacts for the required functions

Availability and locations of the key contacts

List the documents needed

List the electronic location (share point/lan path) where the respective documents are
stored

Define the typical test environment

Is there a requirement for any special environment

What do we need to test (Detailed)

What is out of scope of testing

Will the testing be divided into various phases

What are the different phases in which the testing should be divided
will there be a release plan involved
What attribute/component are in scope of each phases of testing (Tabular
Presentation)

Identify the deliverables of the project

Identify the phases for each deliverable
Success factor/Entry-Exit crieteria

Mention the timelines for each phase

mention the start date and the end date for each phase
Mention the person in charge for the success of each phase

Identify and define the software/hardware risks involved

define the risk prone areas and the impact
Define the risk mitigation and contingency pkan

Whats the process for reporting defects

Do we have a defect reporting tool
Who can report a defect

What data shall bbe used in testing

Do we need/have access to production data