Project Management Plan

All of them found an appreciation reassurance between being used on a farm and the civilian of different sensitization and eminent rhinitis during training. In such an adolescent, the role cannot increase the problem setting because the orlistat malaysia plavix generic new’s goals will prevent a larger exposure.

 

PROJECT MANAGEMENT PLAN

FOR THE

Wanganui High School

PROJECT

 

 

3 

 

 

 

 

 

 

 

 

Project Sponsor: Nigel Rankin                     ……………….                         Date: ……………….

Project Supervisor: Hamish Chamberlain   ……………….                         Date: ……………….

Project Manager: Ronald Patan                   ……………….                         Date: ……………….

 

 

 

Table Of Contents

Project Purpose. 2

Wanganui High School Project. 2

Introduction.. 4

Background. 4

Stakeholders. 5

The project includes the following stakeholders.. 5

Scope. 6

Objectives. 6

Deliverables. 6

Success Criteria. 6

Exclusions. 6

Restrictions. 6

Schedule Baseline. 7

Milestone Schedule. 7

Accuracy and Confidence of Estimates. 7

Change Management Plan.. 8

Monitoring of scope, cost, and schedule. 8

Variance Thresholds. 8

Variance Response. 8

Quality Management Plan.. 9

Quality Assurance Table. 9

Communication Management Plan.. 10

Communications Register. 10

Risk Management Plan.. 11

Risk Register. 11

Likelihood weightings. 12

Impact weightings. 12

Rating values:. 12

Appendix

. 13

 

Project Purpose

Wanganui High School Project

The purpose of the Wanganui High School project is to implement a monitoring system and other information technology Infrastructure. The school is upgrading their old system for better performance and reliability for their data. This will also enable their students doing I.T papers to learn on current Software.

 

Introduction

Background

Wanganui High School is a modern, state funded, co-educational school of approximately 1600 students and 160 staff. It is the largest school in the lower North Island and one of the 30 largest schools in New Zealand.

They have quite a big I.T system for students; they manage all the student and staff through active directory using Microsoft Server 2008.

 

Business Needs

The school wants to improve their information technology systems to newer version of software. This project is going to help them improve their information technology infrastructure which will have a vast impact on the normal day to day usability. They also want to implement monitoring system so they can monitor all their servers.

 

 

Stakeholders

The project includes the following stakeholders.

Stakeholder

Involvement

Contact

Nigel Rankin

Project Sponsor

———–

Hamish Chamberlain

Responsible for overseeing all aspects of a project from its inception to completion

—————-

Project Manger

Project Manager

1273356@ucol.ac.nz

Teachers And Staff

User Testers

——————

Students

User Testers

Student ID’s

Andrew (I.T Administrator)

Bernie(I.T Administrator)

Sean(I.T Administrator)

Look after the current I.T System

———————-

 

 Scope

The following objectives must be completed in order to improve the current information technology infrastructure. All the success criteria must be met in order to have fully working systems.

Objectives

  • Research different types of server monitoring solution
  • Implement Server monitoring system
  • Set up SC-OM on Server 2012
  • Setup SC-VMM
  • Audit of current group policy plus the propose and implement changes
  • Windows 8 image plus all required software using System Center Configuration Manager
  • Tier 2 help desk

 

Deliverables

  • Successfully researched different types of monitoring system
  • Successful working Server monitoring system.
  • Successful working SC-OM
  • Fully working Hyper-V with Virtualization setup
  • Successfully updated group policy and implemented the changes
  • Successful working Windows 8 image ready to deploy using System Center Configuration Manager

Success Criteria

  • The intended objectives have all been approved by the project sponsor.
  • All system setup properly and functional.
  • The product must ensure the security of the users data is secure
  • Deliverable sign off is completed
  • Help desk tasks completed on daily basis
  • Positive results after completing the objectives

Exclusions

·         Server implementation will only be published as working system if sponsor wants too.

Restrictions

  • The project must be completed within the allowed time frame, starting on the 28th of July 2014 and be completed by the 16th October 2014.

 

 

Schedule Baseline

Milestone Schedule

Deliverable

Start Date

End Date

Completion date

Research different types of server monitoring solution

Mon 28/07/14

 

Tue 5/08/14

 

Tue 5/08/14

Setting Up Server monitoring system

Wed 6/08/14

 

Tue 9/09/14

 

Tue 9/09/14

 

Set up SC-OM on Server 2012

Wed 10/09/14

 

Mon 29/09/14

 

Mon 29/09/14

Setup SC-VMM

Tue 30/09/14

 

Tue 14/10/14

 

Tue 14/10/14

 

Audit of current group policy, the propose and implement changes

Wed 15/10/14

 

Mon 20/10/14

Mon 20/10/14

Windows 8 image plus all required Software using System Center Configuration Manager

Mon 20/10/14

 

Fri 24/10/14

Fri 24/10/14

Tier 2 Help Desk

Mon 28/07/14

Tue 21/10/14

Tue 21/10/14

 

 

Accuracy and Confidence of Estimates

The estimates have been made using expert judgment. The amount of days has been gathered using historical data from past projects. All of this information has been processed through the use of a Gantt chart.

  

Change Management Plan

Monitoring of scope, cost, and schedule

As the Sponsor shares the same work space and all communication during the day is in a continual and informal manner. This will keep the project Manager up to date with what is happening for that current day. Also the project will be monitored through weekly status reports sent via email to the project Manager and sponsor.

Variance Thresholds

The schedule can be +/- 3 days before action will be taken. If these variance thresholds have been exceeded a meeting will be called between the sponsor, project supervisor and project manager to discuss the appropriate solution. If it is a major change to Scope and therefore it is outside of the Variance Thresholds then this will be documented using a change request form which is then signed by the project manager, project supervisor and the project sponsor to verify the changes.

Variance Response

If a stage in the project is going to exceed the variance threshold for the scope, then a change request form will need to be filed and action will need to be taken at the sponsor level and below. This is because it will cause major changes that will alter the layout and approach to the project. If a threshold is exceeded then a new alternative will need to be established which will need to be signed off by the project sponsor and project manager.

 

Quality Management Plan

Quality Assurance Table

Deliverable

Internal Check(s)

External Check(s)

Research different types of server monitoring solution

     Project Manager

     Sponsor sign-off

Setting Up Server monitoring system

     Project Manager

     Sponsor sign-off

Setup SC-OM

     Project Manager

     Sponsor sign-off

Set up SC-VMM on Server 2012

     Project Manager

     Sponsor sign-off

Audit of current group policy, the propose and implement changes

     Project Manager

     Sponsor sign-off

     User testing

 

Windows 8 image plus all required Software using System Center Configuration Manager

     Project Manager

     Sponsor sign-off

Tier 2 Help Desk

     Project Manager

     Sponsor sign-off

 

The Project Manager Quality check ensures that the deliverable meets the level of quality that is required before the sponsor may sign it off. The Sponsor sign-off makes sure that the deliverable is of satisfactory level to the project sponsor and can be released.

 

 

Communication Management Plan

Communications Register

Sender

Receiver

What

Detail

How

When

Project Manager

Sponsor

Status Report

Low

Informal Discussion

Daily

Project Manager

Sponsor

Status Report

Medium

Email

Weekly

Project Manager

I.T Administrators

Status Report

Low

Informal Discussion

Daily

Project Manager

I.T Administrators

Status Report

Medium

Informal Discussion

Weekly

I.T Administrators

Project Manger

Status Report Feedback

Medium

Email

Weekly

Sponsor

Project Manager

Status Report Feedback

High

Email

Weekly

Project Manager

Sponsor

Patent documentation

Milestone Sign Off

N/A

Meeting

25/11/14

 

 

The level of detail is broken down into three levels. Low, medium, and high. Low level communication contains an overview of what has been done since the last communication, without going into a lot of detail. High level communication involves a comprehensive breakdown of what occurred that week, any unforeseen problems that may have occurred, and any indication as to whether this would interfere with the projected scheduled. Medium level communication falls between the two, and may contain a combination of elements from the other two.

 

Meetings will be used for any communication with the sponsor that requires any deliverables to be signed off to ensure that before the deliverable is released, it can be demonstrated to the project sponsor to meet all the requirements and be of a high standard.

 


Risk Management Plan

Risk Register

Risk

Proactive Response

Reactive Response

Likelihood

Impact

Rating

Negative feedback during testing

Ensure that a good user experience has been set up during the development

Add extra time for development after the user testing to incorporate the changes that are required to obtain positive feedback

Medium

Medium

12

Sponsor rejects deliverable

Keep the sponsor informed of the development process and get feedback

Increase the time required on the deliverable to complete the required changes

Medium

High

8

 

 

Issues in the ability to maintain data security

Thoroughly field test often during development to make sure that the data remains secure

Increase the length of the development period to fix any issues that may arise

High

High

8

Scope Creep

Insure success criteria is meet as described in project management plan

Inform the sponsor for necessary changes and implement changes to project management plan

High

High

8

Project not completed on time

Monitor the project and check if it is going as planned

Increase the time required for the project, and release the project which may not be 100% complete and add features after release through the software

High

High

4

Illness

Inform the project sponsor about the problem

Increase the time required for the project in reference to the days of illness

High

High

7

Likelihood weightings

Each rating is given a percentage value where low is 10%, medium is 40%, and high is 80%. Where lower the percentage indication, the lower the chance of something occurring.

Impact weightings

Each rating is given a numeric value where low is 10, medium is 40, and high is 80. Where lower the number, the lower the impact on the project.

 

Rating values:

Rating values are calculated by multiplying the likelihood weighting by the impact weighting to give a numeric value.

 

Appendix

The appendix contains the Gantt chart, a change request form, and a deliverable sign-off form.

 

1

 

 

2

 

 

Project Change Request Form

 

Project: Wanganui High School

 

Change Request No:

 

Date:

Requestor:

 

Area Of Project

Importance:

Status: (Pending/Approved/Denied)

 

Change Request Details:

 

 

 

 

 

 

Reason for Change:

 

 

 

 

 

Project Benefit from Change:

 

 

 

Possible Alternative to Change:

 

 

 

Sponsor:

 

Date: ………………………

 

Signed: ………………………

Project Manager:

 

Date: …………………………

 

Signed: …………………………..

Project Supervisor:

 

Date: ………………………….

 

Signed: ……………………………

 

Deliverable Sign-Off Form

 

Project: Wanganui High School

 

 

Deliverable No:

 

 

Deliverable:

Date Completed:

 

Deliverable Summary:

 

 

 

 

 

 

 

 

 

 

 

Acceptance Criteria:

 

 

 

 

 

 

 

Sponsor:

 

Date: ………………………

 

Signed: ………………………

Project Manager:

 

Date: …………………………

 

Signed: …………………………..

Project Supervisor:

 

Date: ………………………….

 

Signed: ……………………………

Leave a Reply

Your email address will not be published. Required fields are marked *