Chapter 5
IS630
Project Plan
1. Introduction
2. Project Definition Overview
3. Changes Since Project Definition Was Approved
4. Staffing Plan
5. Development Environment
6. High-Level Schedule
7. Deliverables and Milestones
8. Functional Requirements
9. Technical Requirements
10. Decision Support System (DSS) Plan
11. Quality Assurance (QA) Plan
12. Communications Plan
13. Deployment Plan
14. Operations Plan
15. Training Plan
16. Risk Management Plan
17. Measurement Plan
18. Client Acceptance Criteria
19. Project Plan Approval
Staffing Plan
1.
2.
Introduction
General Information

3.
Info regarding the project such as name of the project, the client, the project
manager, and the project start and end dates
Skills Assessment

4.
describe the types of personnel/project roles required to complete the project
milestones from planning through post-deployment. Include the timeline/duration,
title, source, and project role and skill level
Staffing Profile

5.
6.
show the people resources required for the project including required hours per
week and duration of tenure
Organization Chart
Outside Resource Profile

7.
details information on client and vendor representatives; and consultants or
contractors assigned to project
Project Roles and Responsibilities

This is where the roles and responsibilities for each team member, client
representative and vendor representative are described in detail. It is important
that this section is very clearly defined and understandable to everyone on the
project team. You should also list the document owner in this section
Skills Assessment
Milestone/Objective
Title
Source
Milestone # 1
Project Manager
Internal
Technical Lead
Internal
1
Business Analyst
Internal
1
User Interface
Designer
Internal
DBA
Internal
1
QA Engineer
Internal
2
Software Engineer
Internal
4
Milestone #2
#
Skill Level /Special
Requirements
Staffing Profile
Calendar
Title
(month or quarter)
(personnel category)
Resource Name Level of
Commitment
(utilization rate)
Period #1
Period #2
Project Manager
1 – Full time
Technical Lead
1 – Quarter time
Project Manager
1 – Full time
Quality
Assurance
1 – Half time
Software
Engineer
4 – Full time
How hard, how long, and how many
Outside Resource Profile
Calendar
Title
(month or quarter)
(personnel
category)
May-July
Project
Manager
1 – Full time
Technical
Lead
1 – Quarter time
Project
Manager
1 – Full time
Quality
Assurance
1 – Half time
August October
Resource
Name
Company
Level of Commitment
(utilization rate)
Project Roles and Responsibilities
Resource
Name
Title
Project Role
Project Manager
Manager and owner for
development and
delivery of product
There is also a RACI model used at HP
Responsibilities
Development Environment
1 Introduction
2 Development Environment for In-House Project
Development Team
2.1
2.2
2.3
2.4
2.5
2.6
Platform
Operating System (and Version)
Development Tools (editors, compilers, debuggers)
Design Tools
Unit Test Tools
Other Equipment or Tools
3 Development Environment for Client Developers or Quality
Assurance
4 Development Environment for Consultants and Contractors
5 Development Environment for Vendors
6 Special Instructions
7 Roles and Responsibilities
1.
2.
3.
4.
5.
6.
Functional Requirements
Introduction
Features
Performance
Speed
Ease of Use
Use Cases
6.1.
6.2.
6.3.
6.4.
Define Different Actors
Interaction with Product
Workflow Diagrams
Alternative Workflows
7. Usability
7.1. User Interface
7.2. Look and Feel
8. Legal Requirements
8.1. Regulatory Requirements
8.2. Security
8.3. Privacy
9. Decision Support Requirements (most of the system do not need this)
9.1. Data Requirements
9.2. User Requirements
9.3. User Interface
10. Access Requirements
10.1. Remote (VPN, Internet, etc.)
10.2. Local
11. Backup Requirements
Technical Requirements
1. Introduction
2. Network Requirements
2.1.
2.2.
Hardware
Software
3. Server Requirements
3.1.
3.2.
Hardware
Software
4. Workstation Requirements
4.1.
4.2.
Hardware
Software
Technical Requirements
5. Database Requirements
5.1.
5.2.
Hardware
Software
6. Error Handling
7. Error Logging, Reporting, Monitoring
8. Redundancy
9. Capacity
10. Reliability
11. Interoperability
12. Scalability
Technical Requirements
13.
14.
15.
16.
17.
Stability
Extensibility
Flexibility
Portability
Security
17.1.
17.2.
Authentication
Monitoring
Technical Requirements
18.
Decision Support
18.1.
18.2.
18.3.
18.4.
19.
Systems Monitoring
19.1.
19.2.
20.
Logging
Data Collection
Data Storage (Database)
Reporting Mechanism
Monitoring Mechanism
Reporting and Alert System
Backup Technical Requirements
QA Plan
1. Introduction
1.1.
1.2.
1.3.
1.4.
1.5.
Project Overview
Project Scope
Testing
Completion Criteria
Schedule
2. Test Matrix
2.1. QA Methodologies
2.2. Test Summary Report
3. Test Plan
3.1. Activities
3.2. Resources
4.
5.
6.
7.
8.
9.
Traceability Matrix
Test Cases
Test Scripts
Defect Reports
Quality Risk Assessment
Performance & Stability Test Plan
Communication Plan
1
2
Introduction
List of Steering Committee and Stakeholder
Groups and Members

3
Who need to be included
Formal Communication Schedule/Plan

4
Major meeting details
Informal Communication Plan

5
How else communications are done
Communication Rules

What is considered “Correct” manners such as format,
waiting time, language, etc.
Deployment Plan
1. Introduction
1.1. General Information
2. Network Deployment
2.1. Network Setup
2.2. Network Test
3. Server Deployment
3.1. Directory Structure
3.2. Deployment Steps
4. Workstation Deployment
4.1. Directory Structure
4.2. Deployment Steps
5. Database Deployment
5.1. Directory Structure
5.2. Deployment Steps
Deployment Plan
6.
7.
8.
9.
Database Access
Data Conversion
Security
For Software Project
9.1.
9.2.
9.3.
9.4.
9.5.
9.6.
CD Mastering and Duplication
Artwork and Packaging
Printing
Assembly
Distribution
Shipping
10.
Deployment Schedule of Events and Timelines
11.Roles and Responsibilities
12.
Verification and Test
13.
Acceptance Criteria
14.
Project Hand-Off
Operations Plan
1. Introduction
2. Operations Document
2.1.
2.2.
2.3.
2.4.
2.5.
2.6.
2.7.
2.8.
2.9.
2.10.
Network and System Diagrams
Technical Specifications for All Hardware and Software Components
Interoperability Specification
Network Specification
Security
Decision Support
Required Regular Maintenance
Bug Fix Releases
Product Update Mechanism and Process
System Monitoring
2.10.1.
2.10.2.
2.10.3.
Error Logging
Error Severity
Escalation and Notification
2.11. Change Control Process
2.12. List of Related Documents
2.13. Service or Maintenance Contracts
2.13.1.
2.13.2.
2.13.3.
Contract Details
Contact Information
Renewal Date
2.14. Scheduled System Downtime
2.15. Escalation Process
2.16. Roles and Responsibilities
Operations Plan
3. System Administrator Guide
3.1. Network and System Diagrams
3.2. Technical and Functional Specifications for All Hardware and Software
Components
3.3. Server Hardware and Software Installation and Setup Guide
3.4. Required Regular Maintenance Procedures
3.5. Monitoring and Reporting System
3.5.1.
3.5.2.
3.5.3.
3.5.4.
Process
Error Detection Method
Error Codes
Escalation Procedures
3.6. Troubleshooting
3.6.1.
3.6.2.
Criteria
Procedures
3.7. Restart and Recovery Procedures
3.7.1.
3.7.2.
For Each Part of the System
Processes Launched at Startup
3.8. Backup and Restore Procedures
3.9. Scheduled Processes and Scripts
3.9.1.
3.9.2.
Manual Reports or Processes
Activity Log
Operations Plan
4. User Guide
4.1. Description of the Functionality and Features
4.2. Client Hardware and Software Installation and Setup Instructions
4.2.1.
4.2.2.
Step-by-Step Instructions
Screenshots
4.3. Step-by -Step Instructions on How to Use Each Feature or Component
4.4. Customizing Views
4.5. How to Print Reports
4.6. How to Submit Defect Reports
4.7. How to Contact Technical and Customer Support
4.8. How to Use Knowledgebase
4.9. How to Use Help
4.10.Accessibility
4.11. Troubleshooting
4.12.Who to Contact
4.13.How to Manually Process Order, Shipment and Delivery
5. Technical Support Guide
6. Customer Support Guide
7. Release Notes
Training Plan
1. Introduction
1.1. General Information
2. Purpose / Goal
3. Objectives
4. Scope
5. Assumptions
6. Training Requirements
7. Training Strategy
7.1. Training Resources
7.2. Hardware Environment to Be Used
7.3. Software Environment to Be Used
8. Dependencies, Constraints, and Limitations
9. Types of Training Manuals Required and Number of Each
Training Plan
10.
Course Description (For Each Course Define):
10.1.
10.2.
10.3.
10.4.
10.5.
10.6.
10.7.
10.8.
10.9.
10.10.
10.11.
Course Outline
Target Audience
Goals and Objectives
Content
Learning Methods and Activities
Attendee Prerequisites
Training Resources
Training Environment
Training Materials
Training Evaluation
Certification
11.Constraints and Risks
12.
Roles and Responsibilities
13.
Training Schedule
14.
Training Log
Risk Management Plan
1. Introduction
2. Risks Identified During Planning Phase
3. The Risk Identification and Evaluation Process
3.1.
3.2.
3.3.
3.4.
Identify
Evaluate
Analyze
Risk Action Plan
4. Prioritization Process
5. Management of Risks
5.1.
5.2.
Risk Log
Risk Status Reporting
6. Roles and Responsibilities
Measurement Plan
1. Introduction
2. Overview of Measurement Plan
2.1.
2.2.
Requirements
Scope
3. Measurement Criteria
4. Description of How Each Objective Will Be
Measured
4.1.
4.2.
Objective 1
Objective 2
5. Roles and Responsibilities
Project Approach
 It is a document define the
processes/methodologies of a project
•
•
•
•
UML (OO)
Agile
Evolutionary Prototyping
Data driven
Project Processes
1. Introduction
Describe the purpose of the document
2. Project Lifecycle
The project lifecycle describes the six distinct phases in the
life of the project. In this section of the project approach
the lifecycle will be described exactly as it pertains to this
particular project.
3. Change Control Process
4. Technical Processes
5. Client Processes – used by the clients
6. Vendor Processes
7. Organizational Processes -- how to sick leave, hand off
build, get engineers to answer a questions, etc
8. Defect Tracking Process
Project Processes
9. Decision Support System (DSS) Process
10.
Status Report Process
Document the process for status reporting.
11.Monitoring and Reporting
12.
Special Processes or Considerations
Note any special processes or considerations not covered in other
sections or documents. Include links or references to documents
where necessary.
13.
Escalation Procedures
14.
Project Documentation Process
define the update and communication process for every project
document.
15.
Roles and Responsibilities
15.1.Process Owner
16.
Project Approach Approval
Change Control Process
1. Introduction
2. Change Control Process
2.1. Description Overview and Process Flowchart
2.2. Planning Phase
2.3. Design Phase
2.4. Development Phase
2.5. Integration Phase
2.6. Deployment Phase
2.7. Post-Deployment Phase
3. Bug Change Control Process
4. Appeal Process for Change Request Denials
5. Roles and Responsibilities
5.1. Process Owner
5.2. Change Control Board
Technical Processes
1. Introduction
1.1. General Information
2. The Build Process
2.1.
2.2.
2.3.
2.4.
2.5.
2.6.
2.7.
Build Schedule
Time Builds Are Kicked Off
Approximate Completion Time
Who Kicks Off the Build (If It Is Not Automated)
Who Is Responsible for Ensuring the Build Is Done
Who Is Responsible for Fixing Problems That "Break" The Build
Which Builds Are Given to QA for Testing
3. Source Control Process
The process should define the source code used, the process for checking in and
checking out code, who is responsible for the source code system ,and
procedures for dealing with problems that require the source code to be restored
or rebuilt.
4. Versioning
The process should define the versioning method and who is responsible for
tracking the current version.
5. Configuration Management
The configuration management process should be defined—who owns it, who
uses it, and the process for using the CM system for building the final products.
6. Roles and Responsibilities
6.1. Process Owner
Defect Tracking Process
1. Introduction
1.1. General Information
2. Definition of Defect
2.1. Defect/Bug
2.2. Enhancement
2.3. New Feature
3.
4.
5.
6.
7.
8.
Who Can Submit Defects
How to Complete a Defect Report
Defect Process
How to Reopen a Defect Report If the Defect Is Not Fixed
How to Appeal a Decision to Defer or Close a Defect Report
Roles and Responsibilities
8.1. Process Owner
Monitoring and Reporting Process
1. Introduction
1.1. General Information
2. Status report
3. Error Categorization and Definition
2.1. Level 1
2.2. Level 2
2.3. Level 3
2.4. Level 4
3.3. Level 3
3.4. Level 4
4. Process for Each Type of Error
3.1. Level 1
3.2. Level 2
5. Alerts
4.1. E-mail
4.2. Pager
6.
7.
8.
9.
Storage and Backup
Reporting
Analysis
Roles and Responsibilities
8.1. Process Owner
Escalation Procedures
1. Introduction
1.1. General Information
2. Escalation Path
Level
Definition
Expected Response
Response delay allowed
3. Notification
Contact Info
4. Roles and Responsibilities
4.1. Process Owner