Chapter 5

IS630

Project Plan1. Introduction2. Project Definition Overview3. Changes Since Project Definition Was Approved4. Staffing Plan5. Development Environment6. High-Level Schedule7. Deliverables and Milestones8. Functional Requirements9. Technical Requirements10.Decision Support System (DSS) Plan11.Quality Assurance (QA) Plan12.Communications Plan13.Deployment Plan14.Operations Plan15.Training Plan16.Risk Management Plan17.Measurement Plan18.Client Acceptance Criteria19.Project Plan Approval

Staffing Plan1. Introduction2. General Information

Info regarding the project such as name of the project, the client, the project manager, and the project start and end dates

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

4. Staffing Profile show the people resources required for the project including required hours per

week and duration of tenure 5. Organization Chart6. Outside Resource Profile

details information on client and vendor representatives; and consultants or contractors assigned to project

7. 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 AssessmentMilestone/Objective Title Source # Skill Level /Special

Requirements

Milestone # 1 Project Manager Internal

Technical Lead Internal 1

Business Analyst Internal 1

Milestone #2 User Interface Designer

Internal

DBA Internal 1

QA Engineer Internal 2

Software Engineer Internal 4

Staffing Profile Calendar (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 Project Manager 1 – Full time

Quality Assurance

1 – Half time

Software Engineer

4 – Full time

How hard, how long, and how many

Outside Resource ProfileCalendar (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

Project Manager

1 – Full time

Quality Assurance

1 – Half time

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

Development Environment1 Introduction2 Development Environment for In-House Project Development Team

2.1 Platform2.2 Operating System (and Version)2.3 Development Tools (editors, compilers, debuggers)2.4 Design Tools2.5 Unit Test Tools2.6 Other Equipment or Tools

3 Development Environment for Client Developers or Quality Assurance

4 Development Environment for Consultants and Contractors5 Development Environment for Vendors6 Special Instructions7 Roles and Responsibilities

Functional Requirements1. Introduction2. Features3. Performance4. Speed5. Ease of Use6. Use Cases

6.1. Define Different Actors 6.2. Interaction with Product6.3. Workflow Diagrams6.4. Alternative Workflows

7. Usability7.1. User Interface7.2. Look and Feel

8. Legal Requirements8.1. Regulatory Requirements8.2. Security8.3. Privacy

9. Decision Support Requirements (most of the system do not need this)9.1. Data Requirements9.2. User Requirements9.3. User Interface

10. Access Requirements10.1. Remote (VPN, Internet, etc.)10.2. Local

11. Backup Requirements

Technical Requirements1. Introduction

2.Network Requirements2.1. Hardware

2.2. Software

3.Server Requirements3.1. Hardware

3.2. Software

4.Workstation Requirements4.1. Hardware

4.2. Software

Technical Requirements5.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

Technical Requirements13. Stability

14. Extensibility

15. Flexibility

16. Portability

17. Security17.1. Authentication

17.2. Monitoring

Technical Requirements18. Decision Support

18.1. Logging

18.2. Data Collection

18.3. Data Storage (Database)

18.4. Reporting Mechanism

19. Systems Monitoring19.1. Monitoring Mechanism

19.2. Reporting and Alert System

20. Backup Technical Requirements

QA Plan 1. Introduction

1.1. Project Overview1.2. Project Scope1.3. Testing1.4. Completion Criteria1.5. Schedule

2. Test Matrix2.1. QA Methodologies2.2. Test Summary Report

3. Test Plan3.1. Activities3.2. Resources

4. Traceability Matrix5. Test Cases6. Test Scripts7. Defect Reports8. Quality Risk Assessment9. Performance & Stability Test Plan

Communication Plan

1 Introduction2 List of Steering Committee and Stakeholder

Groups and Members Who need to be included

3 Formal Communication Schedule/Plan Major meeting details

4 Informal Communication Plan How else communications are done

5 Communication Rules What is considered “Correct” manners such as format,

waiting time, language, etc.

Deployment Plan1. Introduction

1.1. General Information2. Network Deployment

2.1. Network Setup2.2. Network Test

3. Server Deployment3.1. Directory Structure3.2. Deployment Steps

4. Workstation Deployment4.1. Directory Structure4.2. Deployment Steps

5. Database Deployment5.1. Directory Structure5.2. Deployment Steps

Deployment Plan6. Database Access7. Data Conversion8. Security9. For Software Project

9.1. CD Mastering and Duplication9.2. Artwork and Packaging9.3. Printing9.4. Assembly9.5. Distribution9.6. Shipping

10. Deployment Schedule of Events and Timelines11. Roles and Responsibilities12. Verification and Test13. Acceptance Criteria14. Project Hand-Off

Operations Plan1. Introduction2. Operations Document

2.1. Network and System Diagrams2.2. Technical Specifications for All Hardware and Software Components 2.3. Interoperability Specification2.4. Network Specification2.5. Security2.6. Decision Support2.7. Required Regular Maintenance 2.8. Bug Fix Releases2.9. Product Update Mechanism and Process2.10. System Monitoring

2.10.1. Error Logging 2.10.2. Error Severity2.10.3. Escalation and Notification

2.11. Change Control Process2.12. List of Related Documents2.13. Service or Maintenance Contracts

2.13.1. Contract Details2.13.2. Contact Information 2.13.3. Renewal Date

2.14. Scheduled System Downtime2.15. Escalation Process2.16. Roles and Responsibilities

Operations Plan3. System Administrator Guide

3.1. Network and System Diagrams3.2. Technical and Functional Specifications for All Hardware and Software

Components3.3. Server Hardware and Software Installation and Setup Guide3.4. Required Regular Maintenance Procedures3.5. Monitoring and Reporting System

3.5.1. Process3.5.2. Error Detection Method3.5.3. Error Codes3.5.4. Escalation Procedures

3.6. Troubleshooting 3.6.1. Criteria3.6.2. Procedures

3.7. Restart and Recovery Procedures3.7.1. For Each Part of the System3.7.2. Processes Launched at Startup

3.8. Backup and Restore Procedures3.9. Scheduled Processes and Scripts

3.9.1. Manual Reports or Processes3.9.2. Activity Log

Operations Plan4. User Guide

4.1. Description of the Functionality and Features4.2. Client Hardware and Software Installation and Setup Instructions

4.2.1. Step-by-Step Instructions4.2.2. Screenshots

4.3. Step-by -Step Instructions on How to Use Each Feature or Component4.4. Customizing Views4.5. How to Print Reports4.6. How to Submit Defect Reports4.7. How to Contact Technical and Customer Support4.8. How to Use Knowledgebase4.9. How to Use Help4.10. Accessibility4.11. Troubleshooting4.12. Who to Contact4.13. How to Manually Process Order, Shipment and Delivery

5. Technical Support Guide6. Customer Support Guide7. Release Notes

Training Plan1. Introduction

1.1. General Information2. Purpose / Goal3. Objectives4. Scope5. Assumptions6. Training Requirements7. Training Strategy

7.1. Training Resources7.2. Hardware Environment to Be Used7.3. Software Environment to Be Used

8. Dependencies, Constraints, and Limitations9. Types of Training Manuals Required and Number of Each

Training Plan10. Course Description (For Each Course Define):

10.1. Course Outline10.2. Target Audience10.3. Goals and Objectives10.4. Content10.5. Learning Methods and Activities10.6. Attendee Prerequisites10.7. Training Resources10.8. Training Environment10.9. Training Materials10.10. Training Evaluation10.11. Certification

11. Constraints and Risks12. Roles and Responsibilities13. Training Schedule14. Training Log

Risk Management Plan1. Introduction2.Risks Identified During Planning Phase3.The Risk Identification and Evaluation Process

3.1. Identify3.2. Evaluate3.3. Analyze3.4. Risk Action Plan

4.Prioritization Process5.Management of Risks

5.1. Risk Log5.2. Risk Status Reporting

6.Roles and Responsibilities

Measurement Plan

1. Introduction2.Overview of Measurement Plan

2.1. Requirements2.2. Scope

3.Measurement Criteria4.Description of How Each Objective Will Be

Measured4.1. Objective 14.2. 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 Processes1. Introduction

Describe the purpose of the document2. 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 Process4. Technical Processes 5. Client Processes – used by the clients6. Vendor Processes7. Organizational Processes -- how to sick leave, hand off

build, get engineers to answer a questions, etc 8. Defect Tracking Process

Project Processes9. Decision Support System (DSS) Process10. Status Report Process

Document the process for status reporting.11. Monitoring and Reporting12. 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 Procedures14. Project Documentation Process

define the update and communication process for every project document.

15. Roles and Responsibilities15.1. Process Owner

16. Project Approach Approval

Change Control Process1. Introduction2. Change Control Process

2.1. Description Overview and Process Flowchart2.2. Planning Phase2.3. Design Phase2.4. Development Phase2.5. Integration Phase2.6. Deployment Phase2.7. Post-Deployment Phase

3. Bug Change Control Process4. Appeal Process for Change Request Denials5. Roles and Responsibilities

5.1. Process Owner5.2. Change Control Board

Technical Processes1. Introduction

1.1. General Information2. The Build Process

2.1. Build Schedule2.2. Time Builds Are Kicked Off2.3. Approximate Completion Time2.4. Who Kicks Off the Build (If It Is Not Automated)2.5. Who Is Responsible for Ensuring the Build Is Done2.6. Who Is Responsible for Fixing Problems That "Break" The Build2.7. Which Builds Are Given to QA for Testing

3. Source Control ProcessThe 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. VersioningThe process should define the versioning method and who is responsible for tracking the current version.

5. Configuration ManagementThe 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 Responsibilities6.1. Process Owner

Defect Tracking Process

1. Introduction1.1. General Information

2. Definition of Defect2.1. Defect/Bug2.2. Enhancement2.3. New Feature

3. Who Can Submit Defects4. How to Complete a Defect Report5. Defect Process6. How to Reopen a Defect Report If the Defect Is Not Fixed7. How to Appeal a Decision to Defer or Close a Defect Report8. Roles and Responsibilities

8.1. Process Owner

Monitoring and Reporting Process1. Introduction

1.1. General Information2. Status report3. Error Categorization and Definition

2.1. Level 1 2.2. Level 2 2.3. Level 3 2.4. Level 4

4. Process for Each Type of Error3.1. Level 1 3.2. Level 2 3.3. Level 3 3.4. Level

45. Alerts

4.1. E-mail4.2. Pager

6. Storage and Backup7. Reporting 8. Analysis9. Roles and Responsibilities

8.1. Process Owner

Escalation Procedures

1. Introduction1.1. General Information

2. Escalation PathLevel Definition Expected Response Response delay allowed

3. NotificationContact Info

4. Roles and Responsibilities4.1. Process Owner