Network Project Management: Project Analysis and Deployment Details

This project report provides a comprehensive overview of network project management. It begins with an executive summary and table of contents, then delves into project identification, constraints, and requirements. The report meticulously analyzes project stakeholders, communication, and risk management plans. It includes a responsibility matrix, project plan with estimated timelines, and cost estimations. Further sections cover project deployment strategies, including network contingency plans and site preparation. The report also contains an analysis of the project plan, project stakeholders, and a communications and risk management plan. The project plan and estimated time are presented using a Gantt chart and a WBS chart. The cost estimation is also provided. Finally, the report concludes with project review, recommendations, and references.

Running head: NETWORK PROJECT MANAGEMENT
Network Project Management
Name of the student:
Name of the university:
Author Note

1NETWORK PROJECT MANAGEMENT
Executive summary
The following study is the discussion on the project constraints and the project requirements
regarding networks. The project management sturdy has also included the stakeholders,
communication and the risk management plan. Finally the project deployment, project sign-off,
reviews and recommendations are included.

2NETWORK PROJECT MANAGEMENT
Table of Contents
Introduction:..........................................................................................................................................3
Project Identification:............................................................................................................................3
Project constraints and project requirements:........................................................................................4
Project requirements:.............................................................................................................................6
Analysis of the project plan:..................................................................................................................9
Project stakeholders:..........................................................................................................................9
Communications and risk management plan:..................................................................................10
The responsibility matrix:................................................................................................................10
The project plan and estimated time:...............................................................................................11
The cost estimation:.........................................................................................................................13
The project sign of sheet:.....................................................................................................................15
Project review:.....................................................................................................................................16
Conclusion:..........................................................................................................................................16
Recommendations:..............................................................................................................................17
References:..........................................................................................................................................18

3NETWORK PROJECT MANAGEMENT
Introduction:
Networking is regarded as the construction, designing and the usage of network in the field
of information technology. It has been including the physical layer, the selecting and the usage of the
telecommunication protocol and the computer software to use and manage the network (Phillips,
2013). This is to use and manage the network and establishing the operation procedures and policies
relating to the network.
The project management on the other hand has been concerned with the entire coordination
and planning of the project from the idea to the ending aimed to face the estimated necessities and
ensure the completion within time. This has been under the cost and to the needed standards of
quality.
The following report has discussed the project constraints and the project requirements
regarding networks. It has also included the stakeholders, communication and the risk management
plan. Lastly the project deployment, project sign-off, reviews and recommendations are included
(Handschu et al., 2014).
Project Identification:
The very first stage in the development of the project cycle has been recognizing the
components of the projects. The projects could recognize for externally and internally.
The internal identification has been taking place as the energy manager recognizes the
package of energy saving scopes. This includes the daily time, cost and energy managing activities
(Kheni & Ackon, 2015). This might also be from the facility audits.

4NETWORK PROJECT MANAGEMENT
The external identification of the time and cost savings could take pace via the systematic
audits of energy. This has been undertaken by the auditor of the reputable auditor or the company.
In screening projects some of the criteria are used to rank the order of the scopes. This
includes the cost-effectiveness of the time and cost savings of the entire package of the measures.
This includes the net present value, internal rate of return, cash flow and the average payback. Then
there is the sustainability of the savings on the life of that equipment. Then there is the ease of
monitoring, quantifying and verification of the time and cost savings. Next there is the determination
of the technology and the ease to adapt of the technology to the surrounding environment (Corona-
Suárez, AbouRizk & Karapetrovic, 2014). Lastly the environmental and the social cost benefits are
to be determined.
Thus the benefit of the stage of project identification has been assured that the project has
been submitted for the PPA or Preliminary Project Approval. This must be developed and analyzed
in the context of the Network and Tele-communication Program and the Centralized Portfolio
management and representing the best solution of investment.
It has been also assisting the clients of the government departments to develop and recognize
the proper projects supporting the departmental objectives. It has been also been supporting the
government agenda for the information technology and the business projects.
Project constraints and project requirements:
Identifying Business Constraints:
The business constraint has been limiting on the basis of the present organizational state.
They have been focusing on the resources, money and the available time for the project. The
common business constraints have been including the time and budget restrictions, resource skills

5NETWORK PROJECT MANAGEMENT
and resource limitations and so on. For instance the business case containing the assumptions
regarding the business benefits of the project. The assumptions regarding any a particular business
benefit is needed to be documented and connected to the premises in the business (Schwalbe, 2015).
This is because it has been possible that the assumptions might be true or not true at ended.
Identifying Technical Constraints:
The technical constraints have been focusing on the architectural decisions limiting the
solution design. They has been tending to the unchanging and inflexible. This can have the effect on
the solution implantation. They have including the sectors like the hardware, languages and the other
infrastructure and the software used for the project.
The constraints and the assumptions have been the crucial aspect of the project necessities. It
is to be made sure that it must be analyzed and documented properly to the projects. Though there
have been no requirements, they must be documented with the necessities that they influence (Low
& Ong, 2014). This has been the simple step for managing the communicating the constraints,
requirements and assumptions of the project as they are documented and identified the new risks are
required to identifies related to the constrains and assumptions of the project that is required to be
incorporated to the risk register.
It must also be remembered that the project stakeholders might be included with the
identification and the definition of the project constraints and the assumptions for identifying the
effective risks. This might impact the project implementation and the delivery. This might also have
the negative effect on the expectations of the end0users of the ultimate solution. The project
management has been essential to keep the handle on the constraints and assumptions that has been
the part of the project.

6NETWORK PROJECT MANAGEMENT
Project requirements:
This has been defining the IT project necessities that have been the important task while
initiating the latest projects. As it has been clear that defining the necessities has been one of the top
PM best practices, the series of steps are complied that the project teams must follow. This is to get
on track to success (Levin, 2014).
Business and Functional Requirements:
The initial step for the IT project team and the end-users has been the document and define
the functional and the business requirements of the project. This process has been beginning with the
documenting the requirements. This has documenting the details of the functional requirements of
the project.
Design Requirements:
Then the team and the users must design the design necessities and add them to the
documents of the requirements. The design necessities have been describing the way to create the
solutions (Wagner et al., 2014). Every team members has fully understood every requirement before
going ahead.
Project Phases:
The upcoming step has been the outline the phases of the project on the basis of the requirements.
The ending of every phase must have the measurable deliverables. This must make that clear when
the step gets completed.

7NETWORK PROJECT MANAGEMENT
Project Schedule:
Next the team generates the project schedule forming the determined phases. This are needed
to be approved before making continuation.
Test Plans:
This has been another practice of project management. This is to write and execute the test
plans while every project phase gets complemented. Every requirement has been listed in the test
plan and then cross referenced with the associated test. This is to ensure than all the requirements ate
tested for the success (Chartier et al., 2017).
Completion:
The project has been deemed to successful and complete while executing the corresponding
plan of test. This has been validating the project has met every documented necessities. For getting
the deemed successful, the project has been completed under the budgeted cost and time.
Project Deployment:
This includes how the network must be implemented. It includes the hardware and the
facilities. The deployment plan has been network specific. It never covers the user preparation and
the cutting over the activities. The preparing of the network deployment plan has been starting early
in the life-cycle and the plan is expanded at the subsequent stage. The contents below have been
representing the entire network deployment plan.
Network Deployment Strategy:
The description has been the general approach to implement the new network. It Hs been the
deployment approach or the description of the entire deployment strategy. This has been the

8NETWORK PROJECT MANAGEMENT
transition strategy or the description of the strategy recognizing the present communications network
and the proposing the strategy to the transition the clients from the present network to the new
networks. Then there is the transition strategy. This has been the description of the strategy of the
present communication network and suggesting the strategy to transition of the customer from the
present network to the new networks. The next one is the cost\benefit analysis (Zeng et al., 2015).
This has been summary of the benefits of the costs of the proceeding with the delivery of the
network for justifying the deployment strategy chosen. The last one is the preliminary deployment
schedule. This has been describing the steps required to follow for the provided site installation and
for the multi-site installing. This has been defining the order by which the sites are needed to be
installed.
Defining a Network Contingency Plan:
This has been providing the fall-back to cover the possibility that the unexpected events
could cause the installing of the new network to get failed. This has been for the new network
proving to be unusable after it gets deployed.
Site Preparation & Deployment Samples Overview:
This has been relying over the project. This includes the type and the level of the in-depth of
the site-preparation checklist might vary. Depending on the project, the type and level of detail of the
site preparation checklist may vary.
Planning a Technology Deployment:
This has been defining and documenting the steps needed to taken for producing, staging,
installing and testing the hardware, third-party software, system software and the communication

9NETWORK PROJECT MANAGEMENT
components (Olafsdottir, 2016). The scheduling and work plan must be completed for every release
of the system of the unique site to get installed.
Analysis of the project plan:
Project stakeholders:
IT Stakeholder Area/skill set
Network Architect Networks
Network Engineer Networks
Programmer Software
Programmer Analyst Software
Source IT project stakeholder
Network System Administrator Networks
Applications Engineer Software
Database Administrator Database

10NETWORK PROJECT MANAGEMENT
1. Project scope
statement
2. Cost management
plan
3. Communication
management plan
4. Schedule
management plan
1. Planning
analysis and
meetings
1
1. Risk
management plan
INPUTS Tools and
Techniques Outputs
Communications and risk management plan:
Figure: “The communication and risk management plan”
(Source: Created by Author)
The responsibility matrix:
Deliverable: Project
Manager
Mark Cross
Environment
al
Coordinator
Internet
Server Office
Utilities
Permission for
deployment
A R
Network Report A R
Utility Locates I I R
Intersection A C R C

11NETWORK PROJECT MANAGEMENT
Design
Here:
P=Participant is involved but not at a critical level
A=Accountable -must answer to the management for the status of project task
R=Review is needed Input is needed
S=Sign Off is required
The project plan and estimated time:
WBS Task Name Duration Start Finish Predecessors
0
Deploying the network
connections
56 days Tue 6/6/17 Wed 8/23/17
1
Preliminary Design
Compilation
0 days Tue 6/6/17 Tue 6/6/17
2 Facility Design – Research 4 days Wed 6/7/17 Mon 6/12/17 1
3 Facility Design - Architecture 3 days Wed 7/12/17 Fri 7/14/17 2
4
Management Organization
GPO
7 days Tue 7/18/17 Wed 7/26/17 3
5 Management Organization 5 days Thu 7/27/17 Wed 8/2/17 4