1. Chapter 5
IS630

2. 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

3. Staffing Plan 1. Introduction General Information Skills Assessment
Info regarding the project such as name of the project, the client, the project manager, and the project start and end dates
Skills Assessment
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
show the people resources required for the project including required hours per week and duration of tenure
5. Organization Chart
Outside Resource Profile
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

4. Skills Assessment Milestone/Objective Title Source #
Skill Level /Special Requirements
Milestone # 1
Project Manager
Internal
Technical Lead 1
Business Analyst
Milestone #2
User Interface Designer
DBA
QA Engineer 2
Software Engineer 4

5. Staffing Profile How hard, how long, and how many Calendar Title
(month or quarter)
Title
(personnel category)
Resource Name
Level of Commitment
(utilization rate)
Period #1
Project Manager
1 – Full time
Technical Lead
1 – Quarter time
Period #2
Quality Assurance
1 – Half time
Software Engineer
4 – Full time
How hard, how long, and how many

6. Outside Resource Profile
Calendar
(month or quarter)
Title
(personnel category)
Resource Name
Company
Level of Commitment
(utilization rate)
May-July
Project Manager
1 – Full time
Technical Lead
1 – Quarter time
August - October
Quality Assurance
1 – Half time

7. Project Roles and Responsibilities
Resource Name
Title
Project Role
Responsibilities
Project Manager
Manager and owner for development and delivery of product
There is also a RACI model used at HP

8. Development Environment
1 Introduction
2 Development Environment for In-House Project Development Team
2.1 Platform
2.2 Operating System (and Version)
2.3 Development Tools (editors, compilers, debuggers)
2.4 Design Tools
2.5 Unit Test Tools
2.6 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

9. Functional Requirements
1. Introduction
2. Features
3. Performance
4. Speed
5. Ease of Use
6. Use Cases
6.1. Define Different Actors
6.2. Interaction with Product
6.3. Workflow Diagrams
6.4. 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

10. Technical Requirements
1. Introduction
2. Network Requirements
2.1. Hardware
2.2. Software
3. Server Requirements
3.1. Hardware
3.2. Software
4. Workstation Requirements
4.1. Hardware
4.2. Software

11. Technical Requirements
5. Database Requirements
5.1. Hardware
5.2. Software
6. Error Handling
7. Error Logging, Reporting, Monitoring
8. Redundancy
9. Capacity
10. Reliability
11. Interoperability
12. Scalability

12. Technical Requirements
13. Stability
14. Extensibility
15. Flexibility
16. Portability
17. Security
17.1. Authentication
17.2. Monitoring

13. Technical Requirements
18. Decision Support
18.1. Logging
18.2. Data Collection
18.3. Data Storage (Database)
18.4. Reporting Mechanism
19. Systems Monitoring
19.1. Monitoring Mechanism
19.2. Reporting and Alert System
20. Backup Technical Requirements

14. QA Plan 1. Introduction 2. Test Matrix 3. Test Plan
1.1. Project Overview
1.2. Project Scope
1.3. Testing
1.4. Completion Criteria
1.5. Schedule
2. Test Matrix
2.1. QA Methodologies
2.2. Test Summary Report
3. Test Plan
3.1. Activities
3.2. Resources
4. Traceability Matrix
5. Test Cases
6. Test Scripts
7. Defect Reports
8. Quality Risk Assessment
9. Performance & Stability Test Plan

15. Communication Plan 1 Introduction
List of Steering Committee and Stakeholder Groups and Members
Who need to be included
Formal Communication Schedule/Plan
Major meeting details
Informal Communication Plan
How else communications are done
Communication Rules
What is considered “Correct” manners such as format, waiting time, language, etc.

16. 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

17. Deployment Plan 6. Database Access 7. Data Conversion 8. Security
9. For Software Project
9.1. CD Mastering and Duplication
9.2. Artwork and Packaging
9.3. Printing
9.4. Assembly
9.5. Distribution
9.6. Shipping
10. Deployment Schedule of Events and Timelines
11. Roles and Responsibilities
12. Verification and Test
13. Acceptance Criteria
14. Project Hand-Off

18. Operations Plan 1. Introduction 2. Operations Document
2.1. Network and System Diagrams
2.2. Technical Specifications for All Hardware and Software Components
2.3. Interoperability Specification
2.4. Network Specification
2.5. Security
2.6. Decision Support
2.7. Required Regular Maintenance
2.8. Bug Fix Releases
2.9. Product Update Mechanism and Process
2.10. System Monitoring
Error Logging
Error Severity
Escalation and Notification
2.11. Change Control Process
2.12. List of Related Documents
2.13. Service or Maintenance Contracts
Contract Details
Contact Information
Renewal Date
2.14. Scheduled System Downtime
2.15. Escalation Process
2.16. Roles and Responsibilities

19. 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
Process
Error Detection Method
Error Codes
Escalation Procedures
3.6. Troubleshooting
Criteria
Procedures
3.7. Restart and Recovery Procedures
For Each Part of the System
Processes Launched at Startup
3.8. Backup and Restore Procedures
3.9. Scheduled Processes and Scripts
Manual Reports or Processes
Activity Log

20. Operations Plan 4. User Guide 5. Technical Support Guide
4.1. Description of the Functionality and Features
4.2. Client Hardware and Software Installation and Setup Instructions
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

21. 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

22. Training Plan 10. Course Description (For Each Course Define):
10.1. Course Outline
10.2. Target Audience
10.3. Goals and Objectives
10.4. Content
10.5. Learning Methods and Activities
10.6. Attendee Prerequisites
10.7. Training Resources
10.8. Training Environment
10.9. Training Materials
Training Evaluation
Certification
11. Constraints and Risks
12. Roles and Responsibilities
13. Training Schedule
14. Training Log

23. Risk Management Plan 1. Introduction
2. Risks Identified During Planning Phase
3. The Risk Identification and Evaluation Process
3.1. Identify
3.2. Evaluate
3.3. Analyze
3.4. Risk Action Plan
4. Prioritization Process
5. Management of Risks
5.1. Risk Log
5.2. Risk Status Reporting
6. Roles and Responsibilities

24. Measurement Plan 1. Introduction 2. Overview of Measurement Plan
2.1. Requirements
2.2. Scope
3. Measurement Criteria
4. Description of How Each Objective Will Be Measured
4.1. Objective 1
4.2. Objective 2
5. Roles and Responsibilities

25. Project Approach
It is a document define the processes/methodologies of a project
UML (OO)
Agile
Evolutionary Prototyping
Data driven

26. 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

27. 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

28. 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

29. Technical Processes 1. Introduction 1.1. General Information
2. The Build Process
2.1. Build Schedule
2.2. Time Builds Are Kicked Off
2.3. Approximate Completion Time
2.4. Who Kicks Off the Build (If It Is Not Automated)
2.5. Who Is Responsible for Ensuring the Build Is Done
2.6. Who Is Responsible for Fixing Problems That "Break" The Build
2.7. 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

30. 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. Who Can Submit Defects
4. How to Complete a Defect Report
5. Defect Process
6. How to Reopen a Defect Report If the Defect Is Not Fixed
7. How to Appeal a Decision to Defer or Close a Defect Report
8. Roles and Responsibilities
8.1. Process Owner

31. Monitoring and Reporting Process
1. Introduction
1.1. General Information
2. Status report
3. Error Categorization and Definition
2.1. Level Level Level Level 4
4. Process for Each Type of Error
3.1. Level Level Level Level 4
5. Alerts
4.1.
4.2. Pager
6. Storage and Backup
7. Reporting
8. Analysis
9. Roles and Responsibilities
8.1. Process Owner

32. 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