Network Project Scope and Management

This assignment delves into the crucial aspects of network project management. It outlines the project scope, emphasizing data storage, sharing, security, and addressing technological challenges. The document further elaborates on time and cost considerations, highlighting the importance of project crashing methods to optimize time and budget. Stakeholder roles and responsibilities are discussed, along with functional and non-functional requirements for a successful network implementation.

Network Project Management

TABLE OF CONTENTS
SECTION 2 .....................................................................................................................................1
Project scope, requirements and project crashing ...........................................................................1
REFERENCES ..............................................................................................................................4

SECTION 2
Project scope, requirements and project crashing
In order to achieve business goals, it is necessary for the organisations to
define clear set of objectives and scope of the project development. The proposed
project has following scope and requirements.
Scope of the project:
The project will meet the networking requirements of business. It will allow
the organisation to meet its data storage and sharing needs. The security concerns
and failure risk of the project are also addressed by this project so that long term
business objectives can be achieved by the company. The project will cover
technological challenges which can be server as the barrier in the successful
operation of business function.
Time and cost:
The network can be implemented within 2 weeks. It will include the time
duration for analysing business requirements and then to implement networking
devices as per need. The approximate cost for the network for 10 users will be
approximately $2000. This cost will only include the installation charges. The
maintenance cost will differ on the basis of improvement required (Svejvig &
Andersen, 2015). The technological advancements are rapid and thus additional
cost may also require for upgrading with the latest networking techniques.
Quality keys:
The project quality can be sustained for long term by following key principles
of quality management. The organisations must monitor that project deliverable are
meeting requirements of customers and satisfactory services are provided to them.
Networking threats are key concern which can lead to project failure. Thus, project
team must regularly inspect and monitor the activities and performance of project
so that risks can be eliminated before they can cause any losses. With technical
improvements project attributes must also be improved otherwise business may fail
to compete in regularly developing business environment.
Role of stakeholders and team members:
1

The project must be designed by keeping view and interest of all
stakeholders. For example, advanced network techniques may not be easily
accepted by investors and consumers. Thus, before project implementation it must
be explored to its stakeholders (Marchewka, 2014). The project structure must clear
to team members so that they can introduce necessary efforts for achieving project
outcomes. The project features can be best described by team members so they
must describe these features to stakeholders. It will help investors and other
stakeholders to understand and adopt the project.
Different stakeholders have their significant role in project development. The
directors and board members have responsibility to propose and approve the
budget for the project so that team members can develop the same within budget
range. The finance and accounting team monitors that fund is utilising in proper
direction. The quality section ensures that every stage of project meets the quality
standards and requirements so that resources and efforts are not wasted. It is the
duty of the project team members that they coordinate with the employees and
consumers so that their requirements can be accurately addressed by project
implementation.
Functional and non-functional requirements of project:
The technical requirements are known as the non-functional requirements of
project. For example, the routing paths, networking protocols and security tools are
mandatory for sustaining the effectiveness and continuity of project. On the other
hand, functional requirements of the networking projects are its reliability, quality,
performance evaluation, its functionality, characteristics of various networking
layers and error mechanism. These requirements are required to fulfil so that it can
be validated that project scope and outcomes are achieved (Kerzner & Kerzner,
2017).
Project crashing method:
The project can be crashed within 2 weeks. With the help of project crash
methods, the trade-off is established between time duration and cost so that
optimum solution for project can be obtained.
Activity Time (In days) Direct cost (in $)
2

Normal Crash Normal Crash
1, 2 8 4 3000 6000
1 to 3 5 3 4000 8000
2 to 4 9 6 4000 5500
3 to 5 7 5 2000 3200
2 to 5 5 1 8000 12000
4 to 6 3 2.5 10000 11200
5,6 6 2 4000 6800
6,7 10 7 6000 8700
5 to 7 9 5 4200 9000
Total cost 45200 70400
Thus, it is observed that when project is crashed by 2 weeks then its direct cost is
increased by $25200.
3

REFERENCES
Books and Journals
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to
planning, scheduling, and controlling. John Wiley & Sons.
Marchewka, J. T. (2014). Information technology project management. John Wiley &
Sons.
Svejvig, P., & Andersen, P. (2015). Rethinking project management: A structured
literature review with a critical look at the brave new world. International
Journal of Project Management. 33(2). 278-290.
4