MN601: Network Project Management - Online Business Platform Design

This project, MN601: Network Project Management, details the design and implementation of an online business network. It includes an executive summary, table of contents, and an introduction outlining the project's goals: to establish a user-friendly and secure online platform for business transactions. The project defines functional and non-functional requirements, team roles, and responsibilities. It presents a comprehensive project plan, including the project scope, work breakdown structure (WBS), estimated timeline, resource needs, Gantt chart, estimated cost, and schedule crashing. Additionally, the project covers quality, stakeholder analysis, communication, and risk management plans. Ethical considerations, a project deployment plan, project signoff, and post-project review with recommendations are also included. The project aims to mitigate risks like cyber-attacks and data breaches, ensuring a secure and reliable online business environment. Appendices and references are also included to support the project's findings and methodologies. The project was completed with the use of MS Project software for time, cost, and resource planning.

Name of University
MN601: Network Project Management
Assignment 2 of‐
Name of Student
9/19/2017
Name of Professor

MN601: Network Project Management
Executive Summary
These days the business world has developed cut throat competition level, where every penny is
important and equally the growth in business is also required. The on-line platform for doing business
transactions, developing customer base all over the world by providing 24 hrs of services are the few
major advantages of the system1. Moreover the cost expenditure is less than the traditional business
with less investment and less risk. In this report the designing and implementation of such on-line
businesses is to be developed and the planning document shall contain all the project management
plans as per the requirement regarding time, cost, resources and quality and finally the close-out too.
Page 1

MN601: Network Project Management
Table of Contents
Introduction.................................................................................................................................................2
Body............................................................................................................................................................2
Title..........................................................................................................................................................2
Dates.......................................................................................................................................................2
Project Goal.............................................................................................................................................3
Project Objective.....................................................................................................................................3
Functional requirement...........................................................................................................................3
Non-Functional requirement...................................................................................................................3
Team members & Responsibility.............................................................................................................4
Project Plan.............................................................................................................................................4
Project scope.......................................................................................................................................4
Work Breakdown Structure (WBS)......................................................................................................4
Estimated time line‐ .............................................................................................................................4
Resource needs...................................................................................................................................5
Gantt chart and Network Diagram.......................................................................................................6
Estimated cost.....................................................................................................................................6
Schedule crashing by 2 weeks.............................................................................................................6
Quality plan.........................................................................................................................................7
Stakeholder analysis............................................................................................................................7
Communications plan..........................................................................................................................7
Risks management plan.......................................................................................................................8
Ethical issues analysis..........................................................................................................................9
Project deployment plan.....................................................................................................................9
Project Signoff...................................................................................................................................10
Post project review and recommendations.......................................................................................11
Conclusion.................................................................................................................................................11
References.................................................................................................................................................12
Appendices................................................................................................................................................13
Page 2

MN601: Network Project Management
Introduction
To develop the on-line business platform, we need to first develop the requirement matrix and once it is
done, then we need to plan for the four parameters of the projects that are time, cost, quality and
resources. All the planning is been tried to be done using MS Project software. Using this software the
time, cost and resource utilization / deployment planning is also obtained which we shall discuss below
in the main body of the report. The body contains all planning related requirements like the project plan
with well-defined goals and objectives, functional and non-functional requirements etc. We shall also
develop the team roles and responsibilities, communication plan, risk management plan and quality plan
for the report.
Body
Title
Implementation of Network for On-line Business
Dates
Start: 02 / October / 2017 Finish: 24 / October / 2018
Project Goal
The goal of doing the project is to develop a network system for doing on-line business with the comfort
from one location itself and the network need to be user friendly and safest too.
Project Objective
The objective of this project is to design and implement a network for on-line business purpose by
considering all the merits and de-merits of the on-line businesses. The network is required to be
developed in such a way that all the demerits of doing on-line business like lack of trust, cyber-attack,
getting hacked and many more such instances can be avoided2.
Functional requirement
Sl No. Requirement Description
1 Allow to sign-up for
the user
The facility of registration is required to be there in the system so that
all the users of the network can use it and store their personal data too
2 Password protected All the users shall have their own passwords which shall be required to
Page 3

MN601: Network Project Management
enter the system on-line
3 Advertisement All the sellers should access it and advertise their product too for
attracting buyers
4 Tracking system The network need to have proper consignment tracking system so that
the products can be tracked automatically
5 Auto Invoicing As per the buyer and sellers billing transactions all the invoices shall
get generated automatically
Non-Functional requirement
Sl No. Requirement Description
1 Access control system The users must need to provide their passwords which they have set
during first time log-in in the network for further accessing
2 Compatibility The network system must be accessed from any mobile, laptop, tablets
etc. at user’s ease.
3 Secured The network is required to be the safest, and all the transaction and
personal data must be stored safely
4 Portability The network system is required to be accessed from all the parts of the
world
5 Reliability The data generated from the network system need to be reliable to
enable more usage.
Team members & Responsibility
Team members Authority Responsibility
Project Manager High To coordinate among the internal and external stakeholders
Quality Manager Medium To check and confirm the quality standards and their adherence
level in the project
System Designer Medium To gather the requirement and design the system architecture
Technical Manager Medium To develop the network according to the architectural design
Project Plan
Project scope
The overall project scope is to build a network system for doing on-line business with user friendly and
security against any kind of cyber-attack.
Page 4

MN601: Network Project Management
Work Breakdown Structure (WBS)
WBS Task Name
1 Design Network for On-line Business
1.1 Initiate
1.2 Plan
1.3 Implement
1.3.1 Order the purchase item
1.3.2 Design & Configuration
1.4 Close
Estimated time line‐
WBS Task Name Duration Start Finish
1 Design Network for On-line Business 278 days Mon Oct 2, '17 Wed Oct 24, '18
1.1 Initiate 45 days Mon Oct 2, '17 Fri Dec 1, '17
1.1.1 Prepare Business Case 10 days Mon Oct 2, '17 Fri Oct 13, '17
1.1.2 Prepare Project Charter 10 days Mon Oct 16, '17 Fri Oct 27, '17
1.1.3 Document Stakeholder's need 10 days Mon Oct 30, '17 Fri Nov 10, '17
1.1.4 Finalise requirement 15 days Mon Nov 13, '17 Fri Dec 1, '17
1.2 Plan 105 days Mon Nov 13, '17 Fri Apr 6, '18
1.2.1 Prepare Scope Plan 20 days Mon Dec 4, '17 Fri Dec 29, '17
1.2.2 Prepare Time Plan 20 days Mon Jan 29, '18 Fri Feb 23, '18
1.2.3 Prepare Cost Plan 25 days Mon Mar 5, '18 Fri Apr 6, '18
1.2.4 Prepare Quality Plan 25 days Mon Jan 1, '18 Fri Feb 2, '18
1.2.5 Prepare Risk Plan 20 days Mon Jan 1, '18 Fri Jan 26, '18
1.2.6 Prepare Communication Plan 20 days Mon Nov 13, '17 Fri Mar 2, '18
1.2.7 Prepare Procurement Plan 20 days Mon Jan 1, '18 Fri Jan 26, '18
1.3 Implement 175 days Mon Jan 29, '18 Fri Sep 28, '18
1.3.1 Order the purchase item 175 days Mon Jan 29, '18 Fri Sep 28, '18
1.3.1.1 Server 75 days Mon Jan 29, '18 Fri May 11, '18
1.3.1.2 Ports 30 days Mon Aug 6, '18 Fri Sep 28, '18
1.3.1.3 Other hardware 60 days Mon May 14, '18 Fri Aug 3, '18
1.3.2 Design & Configuration 150 days Mon Feb 5, '18 Fri Aug 31, '18
1.3.2.1 Design the system 40 days Mon Feb 5, '18 Fri Aug 24, '18
1.3.2.2 Derive all security protocols 35 days Mon Feb 26, '18 Fri Apr 13, '18
1.3.2.3 Design Implementation 45 days Mon May 14, '18 Fri Jul 13, '18
1.3.2.4 System Configuration 25 days Mon Jul 16, '18 Fri Aug 17, '18
1.3.2.5 Test the system 10 days Mon Aug 20, '18 Fri Aug 31, '18
1.4 Close 35 days Thu Sep 6, '18 Wed Oct 24, '18
1.4.1 Receive feedback 15 days Thu Sep 6, '18 Wed Sep 26, '18
1.4.2 Conduct review meeting 5 days Thu Sep 27, '18 Wed Oct 3, '18
Page 5

MN601: Network Project Management
1.4.3 Document Lessons Learnt &
Recommendation 15 days Thu Oct 4, '18 Wed Oct 24, '18
Resource needs
Manpower:
Resource Name Type Initials
Project Manager Work PM
Quality Manager Work QM
System Designer Work SD
Technical Manager Work TM
Material:
Resource Name Type Initials
Server Material S
Ports Material P
Other hardware Material OH
Gantt chart and Network Diagram
Refer Appendix-1
Estimated cost
Page 6

MN601: Network Project Management
Schedule crashing by 2 weeks
Since the overall duration of a schedule is determined by the critical path / longest path, so we need to
reduce the duration by two weeks of the activities in critical path only.
So, after selecting the activity no. 17, ‘Order and Purchase Servers’ which has a duration of 75 days and
in critical path, we shall reduce the duration by 2 weeks, i.e. 10 days (excluding weekend off days
Saturday and Sunday).
After reducing the duration to 65 days, the finish date changed to 10 / October / 2018, i.e. exactly 2
weeks from 24 / October / 2018.
Since the activity was randomly selected and it was a supply item, but if it would have been derived by
manpower, then the activity with cheapest cost/day value needed to be crushed to have minimum
impact on the project cost baseline.
Quality plan
All the project deliverables like time, cost and quality measures must be monitored and in case of any
difference between the target and planned matrices is observed, then it must be brought to the notice
of higher management for taking proper action.
Quality standard are required to be maintained by the associated quality manager to look for the ways
of preventive action from any issue to save time and money. The network system should be developed
by receiving the comments and then again revising the system by following the Agile Methodology.
Quality matrices needed to ensure daily regarding the maintenance of Agile Methodology throughout
the project life cycle.
Stakeholder analysis
3
Stakeholder Accountable Responsible Consulted Informed Priority Internal /
External
Page 7

MN601: Network Project Management
Project
Manager Yes Yes - - High Internal
Quality
Manager Yes - Yes - Medium Internal
System
Designer - Yes Yes - Medium Internal
Technical
Manager - Yes Yes - Medium Internal
Sponsor Yes Yes High Internal
Sellers - - - Yes Low External
Buyers - - - Yes Low External
Advertisers - - - Yes Low External
Communications plan
Stakeholder What to share Why to share Where to
share
How to share When to share
Project Manager All reports of
time, cost,
quality, risk,
resource,
change orders
Central
coordinator
e-mail or
meeting room
Report or
presentation
Daily, Weekly
& Monthly
Quality
Manager
All reports of
time, cost,
quality, risk,
resource,
change orders
Compile the
data for PM
e-mail or
meeting room
Report or
presentation
Daily, Weekly
& Monthly
System
Designer
All reports of
time and task
Compile the
data for PM
e-mail or
meeting room
Report or
presentation
Daily, Weekly
& Monthly
Technical
Manager
All reports of
change orders
Compile the
data for PM
e-mail or
meeting room
Report or
presentation
Daily, Weekly
& Monthly
Sponsor All reports of
time, cost,
quality, risk,
resource,
Arrange
necessary
statutory
approvals and
e-mail or
sponsor’s
meeting room
Report or
presentation
Monthly
Page 8

MN601: Network Project Management
change orders funds
Sellers Updates on
the progress
To remain
involved
On-line
publications
Report Quarterly
Buyers Updates on
the progress
To remain
involved
On-line
publications
Report Quarterly
Advertisers Updates on
advertisement
To advertise as
per need
Meeting Presentation Quarterly
Risks management plan
Risk
ID
No.
Type Description and Cause Likelihoo
d
Consequen
ce
Level Response
R-1 Opport
unity
If the team could deliver
good network then the
client may provide some
reference and more
business
4 4 High
R-2 Threat Cost is tight, so there is a
risk of getting cost overrun
3 5 High
R-3 Threat There is risk of developing
less secured network and
diverted towards providing
more facilities
4 5 Extre
me
Ethical issues analysis
The team must abide the below codes of ethics for maintaining proper motivational and trust worthy
level in the project group4:
Always help other team members
Always use proper approach as defined in management plan, avoid shortcuts
After assigning any role or responsibility, team member need to own the job fully
Always obey the leader’s decision
Always protect the stakeholder’s interest
Always provide true and correct information
Page 9

MN601: Network Project Management
Project deployment plan
The deployment plan defines the project’s initiation phase to closing phase.ll the stages need to be
covered and explained in detail. It also includes all the assumptions made while developing the plan5.
Project Signoff
6
1. Project Summary
Start Date 10/02/2017 Finish Date 10/24/2018
Project Duration 278 days (excluding weekend off days)
2. Project Goal
Yes, the project goal of developing a user friendly as well as secured network system has been met
successfully.
3. Project Deliverables
Yes, all the defined deliverables with desirable quality standards has been delivered.
Page 10

MN601: Network Project Management
4. Document Signatures
Name Description Signature Date
Sponsor Herewith I confirm that, I have
received the deliverable as a whole
with the documented quality
standard.
11/25/2018
Project Manager Herewith I confirm, that I have
delivered all the documented
deliverables to my client by
maintaining the entire desired
quality standard within the
baseline schedule duration.
10/25/2018
Post project review and recommendations
Now once the project is completed so we need to receive the feedback from the client and document
the lessons learnt. The lessons learnt must include the following data as below7:
Document actual reasons, not the molded one
All the historical data / happening / miss happening need to be documented in chronological
order of happening
Remedial plans must be properly analyzed before documenting them
All key stakeholders must be involved in the process
Recommendation: The future projects need to be planned well before the beginning of execution stage.
All the steps and stages are required to be detailed up to the last WBS level. Activities need to be
assessed properly after accessing the resource constraints and some cushion of around 4 weeks for
allowing the adjustment of some unforeseen situation or risks must be kept.
Page 11