Project Plan and WBS for VoIP System Deployment in Two Universities

This project plan and WBS outlines the deployment of a new VoIP phone system, integrating Google's G-Suite, across two universities. The project aims to enhance business operations by leveraging G-Suite for personal use and fostering user familiarity with its products. The project scope includes stakeholder management, project priorities defined through a matrix, a detailed work breakdown structure (WBS) encompassing planning, migration, and closure phases. A communication plan details the frequency and responsibilities for project updates. Finally, a comprehensive project schedule is provided, outlining task start and end dates, durations, and assigned team members. The project involves various stakeholders, including university owners, technical leads, and project managers, who are responsible for the successful planning, execution, and implementation of the software solutions. The document also includes a bibliography of relevant research materials.

Running head: DEVELOPMENT OF PROJECT PLAN AND WBS
Development of Project Plan and WBS
Name of the Student
Name of the University
Author’s note

1DEVELOPMENT OF PROJECT PLAN AND WBS
Table of Contents
1. Project Scope...............................................................................................................................2
2. Project Priorities..........................................................................................................................3
3. The Work Breakdown Structure..................................................................................................5
4. Communication Plan of the Project.............................................................................................7
5. The Schedule of the Project.........................................................................................................9
Bibliography..................................................................................................................................10

2DEVELOPMENT OF PROJECT PLAN AND WBS
1. Project Scope
The project is based on the deployment of a new VoIP phone system that would be
implemented in two universities. The cell phones, which would be implemented in the
universities would be exchanges with the latest form of Google smartphone. With the
deployment project of the G-Suite project, it would greatly help in scaling the business. The
main purpose of the project is help the business domains in making use of G-Suite for personal
usage. This project would also be helpful for building a familiarity with the user among the
products and also innovate the services within the workplace.
The major stakeholder involved within the project are the owners of the universities. The
other primary stakeholders involved within the project are the technical lead and project
manager. These stakeholders involved within the project would be responsible for the planning,
execution and bringing success for the software solutions that would be implemented for the
benefit of the universities.

3DEVELOPMENT OF PROJECT PLAN AND WBS
2. Project Priorities
(Figure 1: Project Priority Matrix)
(Source: Created by author)
The project priority matrix helps in listing of the importance of tasks that would be done
within the project. It would also discuss about the urgency of tasks that need to be done for the
project. From the above figure, it can be discussed that the most high priority task that needs to
be done for the project includes the setup process or gathering of schema for the university. In
this phase, the various Google applications would be tested and then a proper planning would
need to be made based on the testing phases, migration phases, logo design and documentation
phase.

4DEVELOPMENT OF PROJECT PLAN AND WBS
After the planning phase has been done, there would also be a need for migrating phase.
In this phase, each of the user accounts would be migrated to the Google suite and a proper form
of training would need to be provided to the employees. They should learn the basic tactics for
using the phones in order to provide the best outcomes.
During the closure phase, the final draft based on the deployment plan would need to be
developed. Each of the project resources would be released and thus the project plan would be
finalized. The signing off of documents would be made in this phase.

5DEVELOPMENT OF PROJECT PLAN AND WBS
3. The Work Breakdown Structure

6DEVELOPMENT OF PROJECT PLAN AND WBS
Deployment of G-suite/VoIP in universities
Planning phase
Development of
scheme to create
user accounts
Setting test
domain accounts
Testing of Google
applications
Development of
scheme to create
passwords
Develop scheme
for training
Confirm of go-live
dates
Determine
ownership
Customize logo
and login page
Customize
documentation
Migration phase
Testing of pilot IT
Google moodle
site
Signature files
Google training
calender
Migration for
google accounts
Migrate
listservers
Setting monitoring
tools
Users migration
for mail and
documents
Migration for
calender accounts
Departmental
training
Signature files
Migrate the
calender data
Closure Phase
Final draft of the
deployment plan
Release the
project resources
Finalize the
project plan
Sign off the
project
documents

7DEVELOPMENT OF PROJECT PLAN AND WBS
4. Communication Plan of the Project
Communication Frequency Goal Owner
Project Manager
Project Status
Report
Daily To determine the planning for the next
day based on the progress of work done
in a particular day.
Project
Manager
Team meetings Weekly Each of the team meetings would be
done in order to motivate the team and
thus help in performing better.
Project
Manager
Update on task
progress
Daily Each of the progress over the activities
of task should be looked in to by the
project manager. They would thus be
responsible for keeping a progress over
the work activities and thus ensuring that
the tasks in relation to the project would
be done in proper order.
Project
Manager
Project review Weekly After each of the activities would be
completed, the project manager would
perform a review activity based on the
necessities and urgency of task.
Project
Manager
Technical Lead
Project Status
Report
Weekly To determine the status of each of the
update made over the project.
Technical
Lead
Team meetings Weekly To ensure that the goal of the project is
made clear and also explain them about
the next phase of the project.
Project
Manager
Update on task
progress
Daily To ensure that each of the necessary
progress over the task activities would
be done.
Technical
Lead
Project review Weekly Ensure that the particular part done in a
certain week would be made under
review and then the next phase of the
project would begin.
Technical
Lead, Project
Manager
Planning Committee
Project Status
Report
Weekly They would ensure that the project
would progress in a positive manner.
Planning
committee
members
Team meetings Weekly To ensure that a better form of
communication would be made and thus
Planning
committee

8DEVELOPMENT OF PROJECT PLAN AND WBS
the work on the project would be done as
per proper feedbacks.
members
Update on task
progress
Weekly To ensure that the work done on the
project would be able to affect the
university community. Each of the work
that would be done within the project
should be reported to the planning
committee. This would help in
understanding the various measures that
need to be taken by them.
Planning
committee
members
Project review Weekly To ensure that the project done would be
completed as per the proper feedback
from clients.
Planning
committee
members

9DEVELOPMENT OF PROJECT PLAN AND WBS
5. The Schedule of the Project
Planning phase
Development of scheme to create user
accounts 4/9 4/12 0 4 Project Manager, Technical lead
Setting test domain accounts 4/15 4-22 6 8 Migration lead, Porject Manager
Testing of Google applications 4/23 4/24 14 2 Planning Committee
Development of scheme to create
passwords 4/25 4/30 16 6 Project Manager
Develop scheme for training 5/1 5/3 22 3 Training lead
Confirm of go-live dates 5/6 5/13 27 8 Project Manager,Technical Lead
Determine ownership 5/14 5/17 35 4 Project Manager
Customize logo and login page 5/20 5/22 41 3 Planning committee,Project Manager
Customize documentation 5/23 5/29 44 7 Project Manager
Migration phase
Testing of pilot IT 5/30 5/31 51 2 Technical Lead,Training Lead
Google moodle site 6/3 6/12 55 10 Migration Lead,Project Manager
Signature files 6/13 6/24 65 12 Technical Lead,Training Lead
Google training calender 6/25 6/27 77 3
Marketing Graphic Designer,Project
Manager
Migration for google accounts
Migrate listservers 6/28 7/2 80 5 Technical Lead,Training Lead
Setting monitoring tools 7/3 7/19 85 17 Migration Lead,Technical Lead
Users migration for mail and documents 7/22 7/31 104 10 Project Manager,Technical Lead
Migration for calender accounts
Departmental training 8/1 8/13 114 13 Technical Lead,Training Lead
Signature files 8/14 8/26 127 13 Project Manager,Technical Lead
Migrate the calender data 8/27 9/4 140 9 Project Manager
Closure Phase
Final draft of the deployment plan 9/5 9/6 149 2 Planning committee,Project Manager
Release the project resources 9/9 9/12 153 4 Project Manager
Finalize the project plan 9/13 9/17 157 5 Project Manager,Training Lead
Sign off the project documents 9/18 9/23 162 6 Project Manager
WEEK 4WEEK 3WEEK 2WEEK 1
TASK NAME START ON
DAY* TEAM MEMBER
DURATION*
(WORK DAYS)
END DATESTART DATE
0 20 40 60 80 100 120 140 160 180
Development of scheme to create user accounts
Setting test domain accounts
Testing of Google applications
Development of scheme to create passwords
Develop scheme for training
Confirm of go-live dates
Determine ownership
Customize logo and login page
Customize documentation
Migration phase
Testing of pilot IT
Google moodle site
Signature files
Google training calender
Migration for google accounts
Migrate listservers
Setting monitoring tools
Users migration for mail and documents
Migration for calender accounts
Departmental training
Signature files
Migrate the calender data
Closure Phase
Final draft of the deployment plan
Release the project resources
Finalize the project plan
Sign off the project documents
Days of the Project
(Figure 2: The Schedule of the Project)
(Source: Created by author)

10DEVELOPMENT OF PROJECT PLAN AND WBS
Bibliography
Cohen, J.E., 2017. Law for the platform economy. UCDL Rev., 51, p.133.
Joerger, G., Rambourg, J., Gaspard-Boulinc, H., Conversy, S., Bass, B.L., Dunkin, B.J. and
Garbey, M., 2018. A Cyber-Physical System to Improve the Management of a Large Suite of
Operating Rooms. ACM Transactions on Cyber-Physical Systems, 2(4), p.34.
McCulley, S., 2017. Forensic Analysis of G Suite Collaborative Protocols.
MILLEFANTI, L., 2016. ICT value chain: the impact of the Cloud computing paradigm on
competitive dynamics.
Pannu, M., Salih, Q., Yuen, C., Li, Z.H. and Tanu, E., 2018, November. Web based Project
Management Systems for small to midsize businesses. In 2018 IEEE 9th Annual Information
Technology, Electronics and Mobile Communication Conference (IEMCON) (pp. 1233-1237).
IEEE.
Portier, A., 2018. Security In Plain TXT Observing the Use of DNS TXT Records in the Wild.
Villanova University.