Clear Outline
The paper mainly reflects on the network infrastructure development within an organization in Australia. The main aim of the organization is to mitigate the challenges as well as issues that the organization faces due to absence of proper network architecture within the organization. The development of network architecture not only assists in resolving the issues of the organization but also helps in brining business related benefits. The entire project of network development will be successfully executed within the time that is around 15.2 weeks by assuming that the project will be commenced on 31st May 2018. In addition to this, it is analyzed that the entire project will be completed within the time that is around 13-09-18. The project objectives are listed below:
- To develop network infrastructure within an organization
- To resolve the issues and difficulties that the organization faces
- To finish the project within the timeframe that is around 15.2 weeks.
The requirements of the project are mainly categorized into functional and non-functional requirements are listed below:
Functional requirements: The project functional requirements are listed below:
Network security: proper network security is needed for securing the data as well as information from third party access. This is because the protection of confidential information is one of the significant priorities for the organization.
Networking software: The network software that is required mainly includes various types of network operations, firewall, and operating system as well as different types of other security related applications in order to enable the entire connectivity as well as operations of the organization.
Networking hardware: It is found that the organization generally requires various types of networking hardware including wireless routers, cables as well as switches. All the requirements are generally required for developing the networking infrastructure quite effectively.
Non-functional requirements: The non-functional requirements for the development of network infrastructure are listed below:
Performance: Appropriate speed of network infrastructure must be provided to the organization for managing the business related operation quite effectively.
Availability: The network infrastructures of the organization need to be available whenever needed. Appropriate service of network infrastructure generally assists in improving the entire operations of the business.
The team members who are involved within the network infrastructure of the organization are provided in the table below:
|
Stakeholders |
Expertise |
|
Project manager |
The project manager is quite responsible for managing,, executing as well as monitoring the project of network infrastructure. |
|
Project planner |
The project planner works with the project manager for developing the network infrastructure of the organization. |
|
Network engineer |
They are responsible for establishing appropriate environment off networking by designing system configuration as well as installing and defining the entire system.. |
|
Network consultant |
The network consultant provides guidance to the team members of the project for performing the work of the project. |
|
Network analyst |
The network analyst identifies as well as determines the network related issues that are associated with the network development. |
|
Hr. manager |
The Hr. manager takes the responsible for recruiting as well as providing proper training to the employees who are hired. |
|
Tester |
The tester takes the responsibility for testing the working, usability of the system. |
|
Financial manager |
The financial manager is responsible for managing the finance of the entire organization quite effectively. |
4. Project plan
4.1 Project scope
The project scope is provided below:
- Development of proper network infrastructure
- Completion of project within 15.2 weeks
- Designing logical as well as physical network
- Making proper connection with the devices
4.2 Work breakdown Structure
Figure 1: Work Breakdown Structure
(Source: Created by Author)
4.3 Estimated time-line
The time that is needed for the development of the network infrastructure will be around 15.2 weeks. The times that are needed for finishing each of the activities of the project are provided in the table:
|
WBS |
Task Name |
Duration |
Start |
Finish |
|
1 |
Development of network infrastructure |
15.2 wks. |
Thu 31-05-18 |
Thu 13-09-18 |
|
1.1 |
Initiation phase |
1.6 wks. |
Thu 31-05-18 |
Mon 11-06-18 |
|
1.1.1 |
Developing business case |
2 days |
Thu 31-05-18 |
Fri 01-06-18 |
|
1.1.2 |
Cost-benefit analysis |
3 days |
Mon 04-06-18 |
Wed 06-06-18 |
|
1.1.3 |
Developing charter |
2 days |
Thu 07-06-18 |
Fri 08-06-18 |
|
1.1.4 |
Appointing team members |
1 day |
Mon 11-06-18 |
Mon 11-06-18 |
|
1.1.5 |
Milestone 1: Completion of initiation phase |
0 days |
Mon 11-06-18 |
Mon 11-06-18 |
|
1.2 |
Planning phase |
3.8 wks. |
Tue 12-06-18 |
Fri 06-07-18 |
|
1.2.1 |
Developing project plan |
3 days |
Tue 12-06-18 |
Thu 14-06-18 |
|
1.2.2 |
Developing resource plan |
4 days |
Fri 15-06-18 |
Wed 20-06-18 |
|
1.2.3 |
Developing financial plan |
3 days |
Thu 21-06-18 |
Mon 25-06-18 |
|
1.2.4 |
developing risk management plan |
2 days |
Tue 26-06-18 |
Wed 27-06-18 |
|
1.2.5 |
developing quality plan |
3 days |
Thu 28-06-18 |
Mon 02-07-18 |
|
1.2.6 |
Developing procurement plan |
2 days |
Tue 03-07-18 |
Wed 04-07-18 |
|
1.2.7 |
Developing communication plan |
2 days |
Thu 05-07-18 |
Fri 06-07-18 |
|
1.2.8 |
Milestone 2: Planning phase completion |
0 days |
Fri 06-07-18 |
Fri 06-07-18 |
|
1.3 |
Analysis phase |
3 wks. |
Mon 09-07-18 |
Fri 27-07-18 |
|
1.3.1 |
Analyzing IP addresses |
3 days |
Mon 09-07-18 |
Wed 11-07-18 |
|
1.3.2 |
Sub-netting |
2 days |
Thu 12-07-18 |
Fri 13-07-18 |
|
1.3.3 |
Identifying network device |
2 days |
Mon 16-07-18 |
Tue 17-07-18 |
|
1.3.4 |
identifying network cables |
3 days |
Wed 18-07-18 |
Fri 20-07-18 |
|
1.3.5 |
Identifying software |
2 days |
Mon 23-07-18 |
Tue 24-07-18 |
|
1.3.6 |
Identifying server |
3 days |
Wed 25-07-18 |
Fri 27-07-18 |
|
1.3.7 |
Completion 3: Completion of analysis phase |
0 days |
Fri 27-07-18 |
Fri 27-07-18 |
|
1.4 |
Project designing phase |
1.8 wks. |
Mon 30-07-18 |
Thu 09-08-18 |
|
1.4.1 |
Design of logical network |
5 days |
Mon 30-07-18 |
Fri 03-08-18 |
|
1.4.2 |
Design of physical design |
4 days |
Mon 06-08-18 |
Thu 09-08-18 |
|
1.4.3 |
Milestone 4:Completion of designing phase |
0 days |
Thu 09-08-18 |
Thu 09-08-18 |
|
1.5 |
Implementation phase |
3.2 wks. |
Fri 10-08-18 |
Fri 31-08-18 |
|
1.5.1 |
Hardware placement |
2 days |
Fri 10-08-18 |
Mon 13-08-18 |
|
1.5.2 |
Cable placement |
2 days |
Tue 14-08-18 |
Wed 15-08-18 |
|
1.5.3 |
Allocation of IP |
3 days |
Thu 16-08-18 |
Mon 20-08-18 |
|
1.5.4 |
Connecting devices |
4 days |
Tue 21-08-18 |
Fri 24-08-18 |
|
1.5.5 |
Deploying server |
5 days |
Mon 27-08-18 |
Fri 31-08-18 |
|
1.5.6 |
Milestone 5: Completion of implementation phase |
0 days |
Fri 31-08-18 |
Fri 31-08-18 |
|
1.6 |
Testing phase |
0.8 wks. |
Mon 03-09-18 |
Thu 06-09-18 |
|
1.6.1 |
Testing of network device |
1 day |
Mon 03-09-18 |
Mon 03-09-18 |
|
1.6.2 |
Congestion testing |
1 day |
Tue 04-09-18 |
Tue 04-09-18 |
|
1.6.3 |
Performance testing |
1 day |
Wed 05-09-18 |
Wed 05-09-18 |
|
1.6.4 |
Milestone 6: Completion of testing phase |
1 day |
Thu 06-09-18 |
Thu 06-09-18 |
|
1.7 |
Closure phase |
1.2 wks. |
Thu 06-09-18 |
Thu 13-09-18 |
|
1.7.1 |
Post-project review |
3 days |
Thu 06-09-18 |
Mon 10-09-18 |
|
1.7.2 |
Sign off from stakeholders |
2 days |
Tue 11-09-18 |
Wed 12-09-18 |
|
1.7.3 |
Documentation |
1 day |
Thu 13-09-18 |
Thu 13-09-18 |
Project Requirements
4.4 Resource needs
The resources that are needed for the development of network infrastructure are provided below:
Hardware: The hardware that is needed for the development of the network infrastructure is provided below:
- Routers
- Switches
- Wireless cables
Software: The software that is needed are listed below:
- Operating system
- Server
- Firewall
Human resources: The human resources who are involved within the project are provided below:
- Project manager
- Project planner
- Network engineer
- Network consultant
- Network analyst
- Network designer
- System engineer
- Tester
- Financial manager
- manager
- Project sponsor
Figure 3: Network Diagram
(Source: Created by Author)
4.6 Estimated costs
The budget that is needed for finishing the project of network infrastructure is around $67,320. The overall budget that is needed is reflected in the table below:
|
Task Name |
Duration |
Resource Names |
Cost |
|
Development of network infrastructure |
15.2 wks. |
$ 67,320.00 |
|
|
Initiation phase |
1.6 wks. |
$ 2,480.00 |
|
|
Developing business case |
2 days |
Project manager |
$ 720.00 |
|
Cost-benefit analysis |
3 days |
Financial manager |
$ 840.00 |
|
Developing charter |
2 days |
Project planner |
$ 640.00 |
|
Appointing team members |
1 day |
Hr. manager |
$ 280.00 |
|
Milestone 1: Completion of initiation phase |
0 days |
$ 0.00 |
|
|
Planning phase |
3.8 wks. |
$ 5,968.00 |
|
|
Developing project plan |
3 days |
Project manager |
$ 1,080.00 |
|
Developing resource plan |
4 days |
Hr. manager |
$ 1,120.00 |
|
Developing financial plan |
3 days |
Financial manager, Project sponsor |
$ 840.00 |
|
developing risk management plan |
2 days |
Tester |
$ 608.00 |
|
developing quality plan |
3 days |
Network analyst |
$ 960.00 |
|
Developing procurement plan |
2 days |
Project manager, Project sponsor |
$ 720.00 |
|
Developing communication plan |
2 days |
Project planner |
$ 640.00 |
|
Milestone 2: Planning phase completion |
0 days |
$ 0.00 |
|
|
Analysis phase |
3 wks. |
$ 4,800.00 |
|
|
Analyzing IP addresses |
3 days |
Network consultant |
$ 960.00 |
|
Sub-netting |
2 days |
Network consultant |
$ 640.00 |
|
Identifying network device |
2 days |
Network consultant |
$ 640.00 |
|
identifying network cables |
3 days |
Network consultant |
$ 960.00 |
|
Identifying software |
2 days |
Network consultant |
$ 640.00 |
|
Identifying server |
3 days |
Network consultant |
$ 960.00 |
|
Completion 3: Completion of analysis phase |
0 days |
$ 0.00 |
|
|
Project designing phase |
1.8 wks. |
$ 5,760.00 |
|
|
Design of logical network |
5 days |
System engineer, Network designer |
$ 3,200.00 |
|
Design of physical design |
4 days |
System engineer, Network designer |
$ 2,560.00 |
|
Milestone 4:Completion of designing phase |
0 days |
$ 0.00 |
|
|
Implementation phase |
3.2 wks. |
$ 35,360.00 |
|
|
Hardware placement |
2 days |
Network analyst, Network engineer, System engineer |
$ 1,920.00 |
|
Cable placement |
2 days |
Network analyst, Network engineer, System engineer, Hardware[1],Software[1] |
$ 21,920.00 |
|
Allocation of IP |
3 days |
Network analyst, Network engineer, System engineer |
$ 2,880.00 |
|
Connecting devices |
4 days |
Network analyst, Network engineer, System engineer |
$ 3,840.00 |
|
Deploying server |
5 days |
Network analyst, Network engineer, System engineer |
$ 4,800.00 |
|
Milestone 5: Completion of implementation phase |
0 days |
$ 0.00 |
|
|
Testing phase |
0.8 wks. |
$ 10,912.00 |
|
|
Testing of network device |
1 day |
Tester |
$ 304.00 |
|
Congestion testing |
1 day |
Tester, Additional cost[1] |
$ 10,304.00 |
|
Performance testing |
1 day |
Tester |
$ 304.00 |
|
Milestone 6: Completion of testing phase |
1 day |
$ 0.00 |
|
|
Closure phase |
1.2 wks. |
$ 2,040.00 |
|
|
Post-project review |
3 days |
Project manager |
$ 1,080.00 |
|
Sign off from stakeholders |
2 days |
Project planner |
$ 640.00 |
|
Documentation |
1 day |
Project planner |
$ 320.00 |
4.7 Quality plan
|
Objective |
Status |
|
Does proper quality metrics are followed? |
No |
|
Does the project utilize quality plan for the project? |
Yes |
|
Does the project quality plan is accessible by the stakeholders? |
Yes |
|
Does the quality plan is approved? |
Yes |
4.8 Stakeholder analysis
|
Stakeholder |
Interest |
Power |
|
Project manager |
High |
High |
|
Project planner |
High |
High |
|
Network engineer |
High |
High |
|
Network consultant |
High |
Low |
|
Network analyst |
High |
Low |
|
Hr. manager |
Low |
Low |
|
Tester |
High |
Low |
|
Financial manager |
Low |
Low |
4.9 Communication plan
|
Audience |
Message |
Vehicle |
Frequency |
Owner |
|
Project manager |
Provides details about the about the risks related with the project. |
Email, face to face |
Weekly |
Team leaders |
|
Project team members |
Details about the objectives and scope of the project are explained |
Face to face |
Once |
Project manager |
|
Project planner |
Discusses about the schedule as well as budget status |
Email, conference |
Monthly |
Team leaders |
4.10 Risk management plan
|
Risk |
Description |
Impact |
Probability |
Mitigation |
|
Improper management |
Due to inappropriate management, it becomes difficult to finish the project on time. |
Medium |
Medium |
Experienced project managers must b e hired. |
|
Inappropriate tracking of schedule |
If the schedule is not tracked appropriately then the project can get delayed.. |
High |
High |
Regular tracking of schedule is necessary. |
|
Technical issue |
Due to inappropriate configuration technical challenges occurs. |
High |
High |
Network configuration should be done properly. |
|
Shortage of budget |
Due to inappropriate utilization of budge, financial challenges can occur. |
Medium |
High |
Proper earned value analysis needs to be conducted. |
4.11 Ethical issue analysis
It is identified that after undertaking ethical issue analysis, it is found that the project “development of network infrastructure” generally faces lot of ethical issues. The ethical issues include:
Data loss: If proper security related steps are not used then the sensitive data of the organization can get lost due to technical issues
Unauthorized access: In the absence of authentication, the unauthorized people can also access the data, which further can create lot of ethical issues.
The activities of the project that are generally deployed for the development of the network infrastructure are listed below:
|
Task Name |
|
Project designing phase |
|
Design of logical network |
|
Design of physical design |
|
Milestone 4:Completion of designing phase |
|
Implementation phase |
|
Hardware placement |
|
Cable placement |
|
Allocation of IP |
|
Connecting devices |
|
Deploying server |
5. Project crashing by duration of 2 weeks
Project crashing is done for getting earlier end date of the project. In this project, it is assumed that the network infrastructure will be developed within 15.2 weeks however after crashing the schedule by 2 weeks; the project will get finished within 13.2 weeks. The change in duration is reflected with the provided screenshot.
Figure 4: Screenshot reflecting reduction in project duration after crashing
(Source: Created by Author)
6. Project signoff
|
Stakeholder |
Signature |
|
Project manager |
<Please fill> |
|
Project planner |
Please fill> |
|
Network engineer |
Please fill> |
|
Network consultant |
Please fill> |
|
Network analyst |
Please fill> |
|
Hr. manager |
Please fill> |
|
Tester |
Please fill> |
|
Financial manager |
Please fill> |
7. Project review and recommendations
After reviewing the project it is identified that network infrastructure for the organization will be develop within 13.2 weeks after crashing. The development of network infrastructure is quite beneficial for the organization however there are number of issues that are associated with the project. The steeps that are taken for resolving the issues are reflected below:
Utilization of simple architecture: Simpler topology of the architecture needs to be developed so that the network engineers can easily develop the infrastructure without facing any type of complexities
Reduce buffering: Reduction in offering assists in solving the issues that are associated with buffering and thus the organization can be able to provide proper service
[1] Joslin, R. and Müller, R. Relationships between a project management methodology and project success in different project governance contexts. International Journal of Project Management, 33(6), pp.1377-1392, 2015.
[2] Kerzner, H. Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons, 2017.
[3] Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P.Project risk management methodology for small firms. International journal of project management, 32(2), 327-340, 2014.
[4] Mir, F.A. and Pinnington, A.H .Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), pp.202-217, 2014.
[5] Samset, K. and Volden, G.H. Front-end definition of projects: Ten paradoxes and some reflections regarding project management and project governance. International Journal of Project Management, 34(2), pp.297-313, 2016
[6] Sánchez, M.A. Integrating sustainability issues into project management. Journal of Cleaner Production, 96, pp.319-330, 2015.
[7] Sharbatoghlie, A. and Sepehri, M. An Integrated Continuous Auditing Project Management Model (CAPM). In 4th International Project Management Conference, 2015
[8] Svejvig, P. and Andersen, P. Rethinking project management: A structured literature review with a critical look at the brave new world. International Journal of Project Management, 33(2), pp.278-290, 2015
[9] Todorovi?, M.L., Petrovi?, D.?., Mihi?, M.M., Obradovi?, V.L. and Bushuyev, S.D. Project success analysis framework: A knowledge-based approach in project management. International Journal of Project Management, 33(4), pp.772-783, 2015.
[10] Too, E.G. and Weaver, P. The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), pp.1382-1394, 2014
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
