Project Charter and Management Plan for Globex Network Upgrade, ITC306

This document presents a Project Charter and Management Plan for the Globex corporate network upgrade project. It outlines the project's purpose, business objectives (developing a common network connecting three branches and upgrading the IT infrastructure), and scope, which includes system functions like intrusion detection, cloud connection, disaster recovery, and system documentation. The plan details the project's budget (no budget, as it is an academic assessment), timeframe, milestones, and deliverables. It also defines project and client resources, technical environment specifications, and a brief version of the project management plan, covering risk management (assumptions, dependencies, constraints, risk assessment, and mitigation) and schedule and budget. The project aims to connect Globex's Albury, Griffith, and Wagga Wagga branches within a common network to improve efficiency. The project is a student assignment for ITC306.

Project Charter and Management Plan
Project Client Organisation:
Contact:
System Name <<To be created by team and client>>
Date of Charter <<Date of this version>>
Document Status Draft / Approved <<delete one>>
Document
Reference
<<FileName.doc>>
Version Number Version 1<<update as necessary, in whole
numbers>>
Prepared by <<Technical Writer>>
Team Members << Names of other team members>>
NOTE THAT THIS CHARTER AND THIS HIGH-
LEVEL PROJECT MANAGEMENT PLAN MAY
BE MODIFIED AS NECESSARY WHEN
DETAILED REQUIREMENTS ARE
ESTABLISHED. AFTER ORIGINAL APPROVAL,
CLIENT AUTHORISATION IS NEEDED FOR ALL
CHANGES.
13338252328187300671.docx 1 of 11

1. Change History
All changes to the Project Charter must be recorded in the Change History, and a new
version of the charter must be approved by the client.
Date Description of
Change
Reason for
Change
Author of
Change
Version No.
dd/mm/06 Initial draft N/A Version 1
Second draft Some
adjustments to
the schedule
Version 2
Final draft Some minor
adjustments in
scope and
budget
Version 3
2. Authorised by:
<<Name of client representative authorising this charter & plan>>
Name: ________________________
Signature: ________________________
Date: ________________________
13338252328187300671.docx 2 of 11

Table of Contents
1. CHANGE HISTORY..............................................................................................................................2
2. AUTHORISED BY:.................................................................................................................................2
3. PART 1. PROJECT CHARTER...........................................................................................................4
3.1. PURPOSE OF THE CHARTER...............................................................................................................4
3.2. PURPOSE OF THE PROJECT................................................................................................................4
3.3. BUSINESS OBJECTIVES OF THE PROJECT..........................................................................................4
3.4. SCOPE OF THE PROJECT....................................................................................................................4
3.5. BUDGET AND TIMEFRAME................................................................................................................5
3.6. PROJECT MILESTONES AND DELIVERABLES.....................................................................................6
3.7. PROJECT RESOURCES........................................................................................................................6
3.8. CLIENT RESOURCES..........................................................................................................................6
3.9. PROJECT TEAM RESOURCES.............................................................................................................6
3.10. TECHNICAL ENVIRONMENT..............................................................................................................7
4. PART 2. PROJECT MANAGEMENT PLAN (AN BRIEF VERSION)...........................................8
4.1. RISK MANAGEMENT.........................................................................................................................8
4.1.1 Assumptions.................................................................................................................................8
4.1.2 Dependencies...............................................................................................................................8
4.2. CONSTRAINTS...................................................................................................................................9
4.3. RISK ASSESSMENT............................................................................................................................9
4.3.1 Risk Rating..................................................................................................................................9
4.3.2 Risk Mitigation............................................................................................................................9
4.4. SCHEDULE AND BUDGET................................................................................................................10
4.4.1 Schedule ( Microsoft Project software compulsory).................................................................10
4.4.2 Budget........................................................................................................................................10
4.5. MONITORING & CONTROLLING MECHANISMS...............................................................................11
5. References................................................................................................................................................11
13338252328187300671.docx 3 of 11

3. PART 1 - Project Charter
3.1. Purpose of the Charter
This charter sets out the information that is currently known about the proposed student
project, with the purpose of ensuring that all parties involved in the project share the same
understanding of what the project is expected to achieve.
The project charter is also the brief that authorises the project team to proceed with
launching the project.
3.2. Purpose of the Project
The purpose of the project is to build a new corporate network for Globex including
upgradation of the current IT infrastructure so that all the three branches of the company
are connected to each other within a common network.
3.3. Business Objectives of the Project
To be considered successful, the proposed project must achieve the following goals for the
client:
BUSINESS GOAL EVIDENCE OF GOAL ACHIEVED
1. Develop a common
corporate network
connecting all three
branches
All the officers are now connected to the network
facilitating easy transmission of files, data and
information from one branch to another
2. Upgrade existing IT
infrastructure
All the new specified computer systems with the
specific configurations are installed
3. More efficiency in the
business operations
involving
Faster operations and no need to transfer files and
data from one server to another
3.4. Scope of the Project
The project team will provide the client with the following items:
In Scope Includes
System Functions Intrusion detection and prevention, connection to
cloud, access to SNMP server, disaster recovery and
backup system, access and use of Intranet and VoIP
server, all within one common network to which, all
13338252328187300671.docx 4 of 11

the three branches are connected
System Documentation Charter, Requirements Specification, Design
Specification, Test documentation. Maintenance
Manual
All final documentation on CD-ROM (save trees!)
Training User Training sessions and a Training Manual –
although it is more important that the system has a
remarkably high level of useability so training
documentation should be minimal.
Device configuration The configuration files of all network devices and
configuration parameters of the different applications
provided on CD, and technical documentation for the
person who will maintain the system.
The project will not provide:
Out of Scope Includes
System support and
enhancements
On-going problem resolution and maintenance after the
students have demonstrated the system at the end of the
project in November 2006.
Clients of ITC306 projects will need to consider the
means by which they will obtain on-going technical
support.
3.5. Budget and Timeframe
There is no budget for this project.
This project constitutes the assessment for the academic subject, ITC306 Project
Preparation & Professional Practice, and each student is expected to apply themselves to
the project for approximately 10 hours per week. There is no charge to any client for this
work.
The timeframe for the project is determined by the academic year.
At this early stage, the relevant milestones and deliverables are seen to be as per the table
below. These milestones and deliverables may be modified during the life of the project
with agreement from the client.
13338252328187300671.docx 5 of 11

3.6. Project Milestones and Deliverables
Project Milestone Deliverable Expected Date
Project Start-up Charter and Management Plan <<Assignment due
dates, mostly>>
Solution
Requirements
Specification of Requirements (use cases
or similar)
Test Strategy
Updated Project Plan
PLEASE FILL
Solution Design Fully worked out architecture and detail of
design
Test Plan in detail
PLEASE FILL
Prototype Basic component of solution PLEASE FILL
Iteration Additional functionality
Test Cases
PLEASE FILL
Iteration Test results PLEASE FILL
Iteration Test results PLEASE FILL
Final Release Solution plus all documentation, on CD PLEASE FILL
Project Completion Individual evaluation reports PLEASE FILL
3.7. Project Resources
3.8. Client Resources
Role Name Availability
1. Client Manager Joe Blogs, Head of Projects and IT Manager,
Globex
1 hour per month for
progress reporting.
2. User
Representative
Joe Blogs, Head of Projects and IT Manager,
Globex
Aaron Rossi, IT, Albury Office
Casey Dellacqua, IT, Griffith Office
Trevor Dunn, IT, Wagga Wagga Office
Approx 1 hours per
week to help refine
requirements, develop
test plans and provide
acceptance testing.
Availability for phone
calls.24 hour response
to emails, if possible.
3.9. Project Team Resources
Role Name/s Timeframe/s
1. Project
Manager
Harrison Stone 6 months
2. Requirements Joseph Maddison 4 months
13338252328187300671.docx 6 of 11

Engineer
3. Designer Andrew Sarkis 2 months
4. Network
Engineer
Anderson Stinn 3 months
5. Test Engineer Marissa Jeanette 2 months
6. Technical
Writer
Joe Paul 1 month
7. Hardware/
Network
Consultant
Nancy Reeves 1 month
8. Trainer Nancy Reeves 1 month
3.10. Technical Environment
Students are required to work with technology that must be able to integrate with the
client’s existing technical infrastructure.
It is important that any unconventional r00equirements be discussed at an early stage in the
project, to avoid unwelcome surprises when it is too late to recover
The main technical specifications developed for the project include the following.
Site Albury Wagga Wagga Griffith Cloud
Server 1 AD/DNS/DHCP/File/
Firewall
AD/DNS/DHCP/File/
Firewall
AD/DNS/DHCP/File/
Firewall
VPN Server /
Firewall
Server 2 Intrusion Prevention
System
Logging / SNMP server Disaster Recovery /
Backup solution
Intranet + VoIP
server
Solution
options:
Including
recommend
ed
specificatio
ns
 dedicated machine
running hyperv/esxi
(Core i3/5/7 + 8GB);
or
 2 dedicated machines
(corei3 +2/4GB); or
 non dedicated machine
(Corei7 + 16GB)
 dedicated machine
running hyperv/esxi
(Core i3/5/7 + 8GB);
or
 2 dedicated machines
(corei3 +2/4GB); or
 non dedicated machine
(Corei7 + 16GB)
 dedicated machine
running hyperv/esxi
(Core i3/5/7 + 8GB);
or
 2 dedicated machines
(corei3 +2/4GB); or
 non dedicated machine
(Corei7 + 16GB)
 AWS +
Azure; or
 AWS +
Google
Cloud; or
 Azure +
Google
Cloud; or
(incurs costs)
 AWS; or
 Azure; or
 Google cloud
13338252328187300671.docx 7 of 11

PART 2 - Project Management Plan (a brief version)
The Project Management Body of Knowledge from PMI states that there are nine main
areas of concern for a project. These are:
 Project Integration Management (planning, etc.) <<This charter & plan>>
 Project Scope Management <<above>>
 Project (Human) Resource Management <<above>>
 Project Time Management
 Project Cost Management
 Project Risk Management
 Project Quality Management
 Project Communication Management
 Project Procurement Management (if purchases are needed)
Some of these areas have been covered in the Charter, above. Some are covered below.
Both Network and Software teams must ensure that all areas of PMBOK are continually
checked by them, especially the Project Manager.
3.11. Risk Management
3.11.13.11.1 AssumptionsAssumptions
The plans and estimates for this project are based on the following assumptions:
 The new corporate network will solve the data transmission problem that is
currently a long process.
 The new cloud network will allow virtual storage and management of the data and
thus, no more physical storage devices will be required.
 The project can be completed within a reasonable schedule and budget.
3.11.23.11.2 DependenciesDependencies
The project is dependent upon the following external entities/events:
1. Virtual cloud network that is available on subscription basis
2. IT solutions consultants
3. External funding and support
4. Working during holiday weeks
3.12. Constraints
13338252328187300671.docx 8 of 11

The constraints within which the project will operate are as follows:
1. Time
2. Budget
3. Scope
4. Lack of extensive technical knowledge among the current staff
3.13. Risk Assessment
3.13.13.13.1 Risk RatingRisk Rating
(Note that the risks need to updated as the project proceeds.)
Id Possible Unwelcome Event Likelihood
(L)
1, 2, 3
Severity
(S)
1,2,3
Ranking
L * S
1 Cyber attack 3 3 9
2 Budget overshoot 2 2 4
3 Malfunctioning hardware 2 3 5
4 Missing deadline of delivery 2 2 4
5 Data migration failure 1 3 3
1 is a low risk, 9 high risk.
3.13.23.13.2 Risk MitigationRisk Mitigation
Id Event Risk mitigation or contingency
1 Cyber attack Installation of firewall and antivirus
software
2 Budget overshoot Weekly control and monitoring of
expenses
3 Malfunctioning hardware Check hardware before purchase / replace
hardware using warranty card
4 Missing deadline of delivery Make adjustments to the pending
activities and deliver the project as soon
as possible
5 Data migration failure Check whether the subscription to cloud
has been successfully completed and all
the protocols have been fulfilled before
data migration
13338252328187300671.docx 9 of 11

3.14. Schedule and Budget
3.14.13.14.1 Schedule ( Microsoft Project software compulsory)Schedule ( Microsoft Project software compulsory)
WBS Task Name Duration Start Finish
0 Project for Globex 112 days Mon 16-03-
20
Tue 18-08-
20
1 Requirement Specification and Analysis 2 days Mon 16-03-20 Tue 17-03-20
2 Project Planning 4 days Wed 18-03-20 Mon 23-03-20
3 Budget and Schedule Specification 5 days Tue 24-03-20 Mon 30-03-20
4 Hire IT Team for the Project 3 days Tue 31-03-20 Thu 02-04-20
5 Purchase Hardware Resources 3 days Fri 03-04-20 Tue 07-04-20
6 Purchase Online Software Resources and
Access 2 days Wed 08-04-20 Thu 09-04-20
7 Installation of the Purchased Hardware 5 days Fri 10-04-20 Thu 16-04-20
8 Testing of the Hardware 5 days Fri 17-04-20 Thu 23-04-20
9 Testing of Certain Software 2 days Fri 24-04-20 Mon 27-04-20
10 Create Cloud Virtual Space Account 3 days Tue 28-04-20 Thu 30-04-20
11 Installation of Firewall 10 days Fri 01-05-20 Thu 14-05-20
12 Installation of Anti Virus Software 2 days Fri 15-05-20 Mon 18-05-20
13 Testing of Network Security 15 days Tue 19-05-20 Mon 08-06-20
14 Connect the Network of the Three Branches
of Globex 15 days Tue 09-06-20 Mon 29-06-20
15 Network Testing 15 days Tue 30-06-20 Mon 20-07-20
16 Create Recovery Data Back Up 10 days Tue 21-07-20 Mon 03-08-20
17 Migrate All the Data to the Cloud 5 days Tue 04-08-20 Mon 10-08-20
18 Final Testing 5 days Tue 11-08-20 Mon 17-08-20
19 Hand Over 1 day Tue 18-08-20 Tue 18-08-20
20 Stakeholder Sign Off 0 days Tue 18-08-20 Tue 18-08-20
3.14.23.14.2 BudgetBudget
The budget of the project will mainly cover the prices of material resources, wages of the
IT team and also software costs and cloud subscription costs. An estimated budget is
developed in the following table.
Cost Element Budget
Hardware Costs $20,000
Software Costs $2500
Wages $20,000
Subscription Costs $2500
TOTAL $45,000
13338252328187300671.docx 10 of 11

3.15. Monitoring & Controlling Mechanisms
The project manager will monitor progress of the project.
The team will meet with the Lecturer weekly or as agreed.
The team will meet regularly with the client, weekly, or as agreed.
All project managers will meet together fortnightly, with the subject co-ordinator.
A weekly status/progress report will be provided by the project manager, based on
information supplied by individual team members.
Configuration management techniques will be used to control the documents and other
deliverables of the project – all versions will be kept and baselined when milestones are
reached.
Change management will be used to record changes in any aspect of the project. Each
document will carry a Change History.
All team communication and deliverables will be stored on the Forum, but also backed up
by the Project Manager.
4. References
Ecole Polytechnique Montreal, 2004, Upedu web site, viewed 20 February 2006,
<http://www.upedu.org/upedu/>.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project
management. Project Management Institute.
Heagney, J. (2016). Fundamentals of project management. Amacom.
Kerzner, H. (2017). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Meredith, J. R., Mantel Jr, S. J., & Shafer, S. M. (2017). Project management: a
managerial approach. John Wiley & Sons.
13338252328187300671.docx 11 of 11