Template Project Plan.doc
Put here the project name
Project Plan
[Note: This document serves as a guideline. Format/ table of
content of this guideline can be modified, as long as contents of
this guideline are covered by the new modified document. In
case the format of this document is altered, the reason of
changes should be documented on separated document. All blue
text is optional. Its value can be changed to any intended value.
Change the color to black if you do.]
Prepared By
Put here full name of document author
Put here issued date
Put here the version number
Page: 3 of 10
Table of Contents
1
Introduction................................................................................3
1.1 Objective.............................................................................3
1.2 Scope..................................................................................3
1.3 Reference...........................................................................3
2
Stakeholder Involvement Plan....................................................3
2.1 Team Involvement Plan......................................................3
3
Risks and Contingencies.............................................................4
4
Project Monitoring and Control..................................................5
4.1 Progress Tracking...............................................................5
4.2 Project Schedule.................................................................5
4.3 Critical Path........................................................................5
4.3.1 Task and Activities.......................................................................5
5
Testing Methodology..................................................................5
5.1 Test Scope...........................................................................5
5.2 Testing Strategy..................................................................6
5.3 Testing Tools......................................................................7
6
Implementation Methodology....................................................7
6.1 Prerequisite........................................................................7
6.2 Data & Environment...........................................................7
7
Assumptions................................................................................ 7
8
Appendices.................................................................................. 8
8.1 Appendix A : Signatures.....................................................8
8.2 Appendix B: Other Documents & Document History..........9
Put here the project name
Project Plan
Version: [Put here the version number]
Page 4 of 10
Introduction
Objective
The objective of this plan is to describe all project-related and organizational
activities for ensuring the quality of the project.
[State the summary of Objective of the project plan]
Scope
This project plan describes the responsibilities, methodology, project quality
milestones and test plan for this project.
[State the scope that covered by the project plan. What activity, time line, deliverables and
responsibilities that covered by this project plan]
Reference
See Appendix B for Reference & Other related documents.
Stakeholder Involvement Plan
The roles and responsibilities involved are to controls the quality of the software and deliverables. The
following lists the roles and responsibilities in [Project Name] project:
Team Involvement Plan
No
1
Name
Role
Project Manager
·
·
·
·
·
·
·
·
·
·
·
·
·
Put here the project name
Responsibilities
Perform project planning
activities
Conduct kick off meeting
and communicate the project's
progress to all relevant stakeholders
Motivate the project team
and have constant personal
drive to achieve the project's
goals
Perform project evaluation
Send Deliverables to Client
Get user acceptance &
feedback from client
Perform production test
run
Log and Analyze Problem
Perform Problem solving
activities
Conduct External & Internal closing meeting
Perform FP Count of Delivered SW
Save all project Defect
Data to Defect Database
·
·
Deliverables
Project Schedule
Project Plan
Project Plan
Version [Put here the version number]
Page 5 of 10
2
Business Analyst
·
·
·
·
·
·
3
3
Database
Administrator
Software Designer
·
·
·
·
·
·
·
·
·
·
·
·
4
Software Tester
·
·
·
·
5
Software Engineer
6
Web Designer
·
·
·
·
·
·
·
·
·
·
·
·
·
Perform and/or Verify SW
Requirements Analysis
Perform requirement gathering
with client
Develop Software Requirement
Specification document
Assessing the adequacy of
requirements
Develop Mini RVM
Perform Design & Test Script
Review
Perform UAT with client
Perform Data Migration
Develop Test Script
Review Test Scenario/Test
Script/Checklist
Perform Code Review, User
Interface & Unit Test Coverage
Review
Perform Product Integration
Perform Self-Integration Test
Review and Verify Test Result
Produce Storage Media
Perform Packaging and
Preservation of copy
Perform unit testing
Perform software testing
activities
Perform Unit Test Coverage
Review
Review and Verify Test Result
Produce Validation Report
Develop the software program
Perform unit testing
Establish Integration Baseline
Perform Virus-Check
Perform & Verify SW
Requirement Analysis
Perform Self-Integration-Test
Perform UI Review
·
·
·
Software Requirement
Specification
Review Report
Test Scenario/Test Script/
Checklist with result
·
Migrated Data
·
·
·
Test Scenario
Review Report
Test Scenario/Test Script/
Checklist with result
Software Architecture
Design
·
·
·
·
·
·
Test Scenario
Test Script
Review Report
Test Scenario/Test Script/
Checklist with result
Validation Report
·
·
·
Source Code
Unit Test Result
Scan Log Report
·
Test Scenario/Test Script/
Checklist with result
Review Report
·
Risks and Contingencies
[Specified all risks to be considered in developing this project]
No
Date
Raised
1
19-Aug-05
Put here the project name
Phase of the
Project
Risks
Resource downtime
(sick, accident, unprecedented leave, etc)
Impact
Delay in project
progress
Mitigation Actions
e.g.
1. Make sure all leave
request should be
submitted 2 weeks
before D-Day.
2. Get together all
team members about
unprecedented
leave…
Project Plan
Version [Put here the version number]
Page 6 of 10
2
3
1 Project Monitoring and Control
The content here should be made in a tabular form for easy reading and understanding. Descriptions should be
added necessarily in the Task column. Frequency of Project Tracking is by time, such as Daily, Weekly, Monthly, By
weekly, Once every 2 months, and so on.
Example:
1.1
Progress Tracking
No
Task
1
Daily Project Tracking which includes :
a. Today's Activity
b. Tomorrow's To Do List
c. Deferred Items
d. Today's Issues
2
3
1.2
Frequenc
y
Daily
Stakeholder
PM, Team
Members
Clients if
necessary
Note: The daily project tracking meeting will be
conducted 5-10 minutes a day for every session.
Each session consists of 5 team members picked
randomly
Weekly Progress Review
End Phase Report
Note: This report includes Defect Prevention
effectiveness review, Schedule Variance report, etc.
Derivative measurements will be performed by the
SQA, but the PM has to make sure all the data is
available.
Weekly
End of
Phase
PM, Team
Members,
Clients
SQA
Project Schedule
1.3 Critical Path
[This section contains the project critical path parameters. It is divided into several sections. This is
planned ahead to ensure that all critical path are covered and addressed in the project]
1.3.1
Task and Activities
[Put here who will be responsible for the task and its milestone of completion]
Task
Put here the project name
PIC
Role
Milestone
Remarks
Project Plan
Version [Put here the version number]
Page 7 of 10
2 Testing Methodology
[Describe the objective of the test plan]
2.1 Test Scope
[Describe the test scope which including items to be tested and items not to be tested.]
2.2
Testing Strategy
All written code will be reviewed and tested multiple times under different aspects.
This chapter explains the different testing approaches in more detail:
System Testing
Objective: To validate the system behavior against the requirements stated
in the SRS
Entry Criteria:
Testing will commence if there is a baselined release from the developers.
Technique: “BlackBox” / functional testing, using test cases; each test case
states some interaction and input, along with the expected result/output.
Completion / Exit Criteria:
o All planned tests have been executed
o All identified defects have been addressed
Related document: System Test Script
(developed and reviewed later, see overall planning).
Unit Testing
Objective: To validate the technical of units (small pieces of the software up
until method level) against its detail design specification.
Entry Criteria:
o Unit testing will be done for every method that is developed within a
program
o Unit testing is done simultaneously with coding
Technique: “White Box” testing with up to method testing precision. May
also enhanced by “GlassBox” test cases, which consider the program logic;
typically to achieve coverage of all statements.
Completion / Exit Criteria:
o All test cases executed with no more errors.
”No error” means, that the actual and expected system behavior is
the same.
o All test cases have been signed off to QA.
o All Automated unit test code has passed execution.
Related document: Unit Test Script (optional), Unit Test Code
(developed and reviewed later, see overall planning).
Performance Testing
Objective: To validate the usability and stability of the application when
under heavy load / access from web.
Entry Criteria:
o Unit testing will be done for every method that is developed within a
program
o Unit testing is done simultaneously with coding
Technique: tool-assisted multiple access of selected application
functionality, using test cases.
Completion / Exit Criteria:
Put here the project name
Project Plan
Version [Put here the version number]
Page 8 of 10
Single Transaction/single user: Successful completion of the test
scripts without any failures and within the expected / required time
allocation (per transaction).
o Multiple transactions / multiple users: Successful completion of the
test scripts without any failures and within acceptable time
allocation..
Related document: Performance Test Script
(developed and reviewed later, see overall planning).
o
[State all other applicable testing types for this project accordingly. These 3 tests are mandatory for
the software development cycle]
2.3 Testing Tools
[State the testing tools for testing of the system]
Implementation Methodology
Prerequisite
[Describe what is needed to be done before the Implementation is performed (e.g. the number of
major errors should be 0, done before a specific date, etc
Also make sure the following items are checked
1. The latest released application is used
2. A Clean database is set up before the data migration is performed (if any)
3. Review of the Data Migration should be defined also
4. Define criteria for a good implementation phase to be able to be accepted by the client
]
Data & Environment
[Describe what is needed done before Implementation, what kind of data must be supplied by the
client / , who will be conducting the Implementation, where will it be done, etc]
Assumptions
[Describe all the assumptions applied to this project plan]
Put here the project name
Project Plan
Version [Put here the version number]
Page 9 of 10
Appendices
Appendix A : Signatures
This document has been reviewed and accepted by the undersigned. Therefore, this
document will be used as the basis for doing further processing. Any addition and/or
modification of this document will be subjected to approval by the undersigned.
Signature
:
Signature of the
approved
Signature
:
Name
Title
Date
:
:
:
Name
Role/Job
Signing Date
Name
Title
Date
:
:
:
Signature
:
Signature of the
approved
Signature
:
Name
Title
Date
:
:
:
Name
Client
Signing Date
Name
Title
Date
:
:
:
Signature
:
Signature
:
Name
Title
Date
:
:
:
Name
Title
Date
:
:
:
Signature
:
Signature
:
Name
Title
Date
:
:
:
Name
Title
Date
:
:
:
Put here the project name
Project Plan
Version [Put here the version number]
Page 10 of 10
Appendix B: Other Documents & Document
History
2.4
Related documentation:
·
Proposal ver x.x
·
Project Schedule ver x.x
·
Project Assect Maintenance
·
Stakeholder Involvement Sheet
·
Risk & Issue List
·
SRS ver x.x
·
Any other supporting documents
[Note: Create hyperlynk for each related documentation]
Document History:
Version
0.1
Date
Put here the project name
Change Reason
Initial Creation
Author
Project Manager
Project Plan
Version: [Put here the version number]
Project Plan
[Note: This document serves as a guideline. Format/ table of
content of this guideline can be modified, as long as contents of
this guideline are covered by the new modified document. In
case the format of this document is altered, the reason of
changes should be documented on separated document. All blue
text is optional. Its value can be changed to any intended value.
Change the color to black if you do.]
Prepared By
Put here full name of document author
Put here issued date
Put here the version number
Page: 3 of 10
Table of Contents
1
Introduction................................................................................3
1.1 Objective.............................................................................3
1.2 Scope..................................................................................3
1.3 Reference...........................................................................3
2
Stakeholder Involvement Plan....................................................3
2.1 Team Involvement Plan......................................................3
3
Risks and Contingencies.............................................................4
4
Project Monitoring and Control..................................................5
4.1 Progress Tracking...............................................................5
4.2 Project Schedule.................................................................5
4.3 Critical Path........................................................................5
4.3.1 Task and Activities.......................................................................5
5
Testing Methodology..................................................................5
5.1 Test Scope...........................................................................5
5.2 Testing Strategy..................................................................6
5.3 Testing Tools......................................................................7
6
Implementation Methodology....................................................7
6.1 Prerequisite........................................................................7
6.2 Data & Environment...........................................................7
7
Assumptions................................................................................ 7
8
Appendices.................................................................................. 8
8.1 Appendix A : Signatures.....................................................8
8.2 Appendix B: Other Documents & Document History..........9
Put here the project name
Project Plan
Version: [Put here the version number]
Page 4 of 10
Introduction
Objective
The objective of this plan is to describe all project-related and organizational
activities for ensuring the quality of the project.
[State the summary of Objective of the project plan]
Scope
This project plan describes the responsibilities, methodology, project quality
milestones and test plan for this project.
[State the scope that covered by the project plan. What activity, time line, deliverables and
responsibilities that covered by this project plan]
Reference
See Appendix B for Reference & Other related documents.
Stakeholder Involvement Plan
The roles and responsibilities involved are to controls the quality of the software and deliverables. The
following lists the roles and responsibilities in [Project Name] project:
Team Involvement Plan
No
1
Name
Role
Project Manager
·
·
·
·
·
·
·
·
·
·
·
·
·
Put here the project name
Responsibilities
Perform project planning
activities
Conduct kick off meeting
and communicate the project's
progress to all relevant stakeholders
Motivate the project team
and have constant personal
drive to achieve the project's
goals
Perform project evaluation
Send Deliverables to Client
Get user acceptance &
feedback from client
Perform production test
run
Log and Analyze Problem
Perform Problem solving
activities
Conduct External & Internal closing meeting
Perform FP Count of Delivered SW
Save all project Defect
Data to Defect Database
·
·
Deliverables
Project Schedule
Project Plan
Project Plan
Version [Put here the version number]
Page 5 of 10
2
Business Analyst
·
·
·
·
·
·
3
3
Database
Administrator
Software Designer
·
·
·
·
·
·
·
·
·
·
·
·
4
Software Tester
·
·
·
·
5
Software Engineer
6
Web Designer
·
·
·
·
·
·
·
·
·
·
·
·
·
Perform and/or Verify SW
Requirements Analysis
Perform requirement gathering
with client
Develop Software Requirement
Specification document
Assessing the adequacy of
requirements
Develop Mini RVM
Perform Design & Test Script
Review
Perform UAT with client
Perform Data Migration
Develop Test Script
Review Test Scenario/Test
Script/Checklist
Perform Code Review, User
Interface & Unit Test Coverage
Review
Perform Product Integration
Perform Self-Integration Test
Review and Verify Test Result
Produce Storage Media
Perform Packaging and
Preservation of copy
Perform unit testing
Perform software testing
activities
Perform Unit Test Coverage
Review
Review and Verify Test Result
Produce Validation Report
Develop the software program
Perform unit testing
Establish Integration Baseline
Perform Virus-Check
Perform & Verify SW
Requirement Analysis
Perform Self-Integration-Test
Perform UI Review
·
·
·
Software Requirement
Specification
Review Report
Test Scenario/Test Script/
Checklist with result
·
Migrated Data
·
·
·
Test Scenario
Review Report
Test Scenario/Test Script/
Checklist with result
Software Architecture
Design
·
·
·
·
·
·
Test Scenario
Test Script
Review Report
Test Scenario/Test Script/
Checklist with result
Validation Report
·
·
·
Source Code
Unit Test Result
Scan Log Report
·
Test Scenario/Test Script/
Checklist with result
Review Report
·
Risks and Contingencies
[Specified all risks to be considered in developing this project]
No
Date
Raised
1
19-Aug-05
Put here the project name
Phase of the
Project
Risks
Resource downtime
(sick, accident, unprecedented leave, etc)
Impact
Delay in project
progress
Mitigation Actions
e.g.
1. Make sure all leave
request should be
submitted 2 weeks
before D-Day.
2. Get together all
team members about
unprecedented
leave…
Project Plan
Version [Put here the version number]
Page 6 of 10
2
3
1 Project Monitoring and Control
The content here should be made in a tabular form for easy reading and understanding. Descriptions should be
added necessarily in the Task column. Frequency of Project Tracking is by time, such as Daily, Weekly, Monthly, By
weekly, Once every 2 months, and so on.
Example:
1.1
Progress Tracking
No
Task
1
Daily Project Tracking which includes :
a. Today's Activity
b. Tomorrow's To Do List
c. Deferred Items
d. Today's Issues
2
3
1.2
Frequenc
y
Daily
Stakeholder
PM, Team
Members
Clients if
necessary
Note: The daily project tracking meeting will be
conducted 5-10 minutes a day for every session.
Each session consists of 5 team members picked
randomly
Weekly Progress Review
End Phase Report
Note: This report includes Defect Prevention
effectiveness review, Schedule Variance report, etc.
Derivative measurements will be performed by the
SQA, but the PM has to make sure all the data is
available.
Weekly
End of
Phase
PM, Team
Members,
Clients
SQA
Project Schedule
1.3 Critical Path
[This section contains the project critical path parameters. It is divided into several sections. This is
planned ahead to ensure that all critical path are covered and addressed in the project]
1.3.1
Task and Activities
[Put here who will be responsible for the task and its milestone of completion]
Task
Put here the project name
PIC
Role
Milestone
Remarks
Project Plan
Version [Put here the version number]
Page 7 of 10
2 Testing Methodology
[Describe the objective of the test plan]
2.1 Test Scope
[Describe the test scope which including items to be tested and items not to be tested.]
2.2
Testing Strategy
All written code will be reviewed and tested multiple times under different aspects.
This chapter explains the different testing approaches in more detail:
System Testing
Objective: To validate the system behavior against the requirements stated
in the SRS
Entry Criteria:
Testing will commence if there is a baselined release from the developers.
Technique: “BlackBox” / functional testing, using test cases; each test case
states some interaction and input, along with the expected result/output.
Completion / Exit Criteria:
o All planned tests have been executed
o All identified defects have been addressed
Related document: System Test Script
(developed and reviewed later, see overall planning).
Unit Testing
Objective: To validate the technical of units (small pieces of the software up
until method level) against its detail design specification.
Entry Criteria:
o Unit testing will be done for every method that is developed within a
program
o Unit testing is done simultaneously with coding
Technique: “White Box” testing with up to method testing precision. May
also enhanced by “GlassBox” test cases, which consider the program logic;
typically to achieve coverage of all statements.
Completion / Exit Criteria:
o All test cases executed with no more errors.
”No error” means, that the actual and expected system behavior is
the same.
o All test cases have been signed off to QA.
o All Automated unit test code has passed execution.
Related document: Unit Test Script (optional), Unit Test Code
(developed and reviewed later, see overall planning).
Performance Testing
Objective: To validate the usability and stability of the application when
under heavy load / access from web.
Entry Criteria:
o Unit testing will be done for every method that is developed within a
program
o Unit testing is done simultaneously with coding
Technique: tool-assisted multiple access of selected application
functionality, using test cases.
Completion / Exit Criteria:
Put here the project name
Project Plan
Version [Put here the version number]
Page 8 of 10
Single Transaction/single user: Successful completion of the test
scripts without any failures and within the expected / required time
allocation (per transaction).
o Multiple transactions / multiple users: Successful completion of the
test scripts without any failures and within acceptable time
allocation..
Related document: Performance Test Script
(developed and reviewed later, see overall planning).
o
[State all other applicable testing types for this project accordingly. These 3 tests are mandatory for
the software development cycle]
2.3 Testing Tools
[State the testing tools for testing of the system]
Implementation Methodology
Prerequisite
[Describe what is needed to be done before the Implementation is performed (e.g. the number of
major errors should be 0, done before a specific date, etc
Also make sure the following items are checked
1. The latest released application is used
2. A Clean database is set up before the data migration is performed (if any)
3. Review of the Data Migration should be defined also
4. Define criteria for a good implementation phase to be able to be accepted by the client
]
Data & Environment
[Describe what is needed done before Implementation, what kind of data must be supplied by the
client / , who will be conducting the Implementation, where will it be done, etc]
Assumptions
[Describe all the assumptions applied to this project plan]
Put here the project name
Project Plan
Version [Put here the version number]
Page 9 of 10
Appendices
Appendix A : Signatures
This document has been reviewed and accepted by the undersigned. Therefore, this
document will be used as the basis for doing further processing. Any addition and/or
modification of this document will be subjected to approval by the undersigned.
Signature
:
Signature of the
approved
Signature
:
Name
Title
Date
:
:
:
Name
Role/Job
Signing Date
Name
Title
Date
:
:
:
Signature
:
Signature of the
approved
Signature
:
Name
Title
Date
:
:
:
Name
Client
Signing Date
Name
Title
Date
:
:
:
Signature
:
Signature
:
Name
Title
Date
:
:
:
Name
Title
Date
:
:
:
Signature
:
Signature
:
Name
Title
Date
:
:
:
Name
Title
Date
:
:
:
Put here the project name
Project Plan
Version [Put here the version number]
Page 10 of 10
Appendix B: Other Documents & Document
History
2.4
Related documentation:
·
Proposal ver x.x
·
Project Schedule ver x.x
·
Project Assect Maintenance
·
Stakeholder Involvement Sheet
·
Risk & Issue List
·
SRS ver x.x
·
Any other supporting documents
[Note: Create hyperlynk for each related documentation]
Document History:
Version
0.1
Date
Put here the project name
Change Reason
Initial Creation
Author
Project Manager
Project Plan
Version: [Put here the version number]