MN601 Network Project Management Assignment Sample
Here’s the best sample of MN601 Network Project Management Assignment, written by the expert.
Executive Summary
The main aim of this study is to develop a project through the use of network project management. For this study, the software application developed is used as a project that would be completed with 12 months according to the project planning. In addition to this, the project scope and project requirements are also explaining with providing WBS, estimation of Time, cost, quality key stakeholders’ roles, and responsibilities etc. In addition, this study also analyses the stakeholder, communication matrix, risk matrix, and ethical issues. Moreover, the project includes the different activities and tasks using Project Management software such as Gantt chart, Network diagram, etc. There is a description of the project deployment plan, project signoff letter, and recommendations for the post-project review regarding the project planning.
Introduction
In the technological environment, most of the projects are completed through the project networks. A project network provides the well-designed planning to understand the project in an easy way. In concern to this study, the project is planning for building a software application. In addition to this, the study also includes the project scope and requirements that includes WBS, time & cost estimation, and the role of the project team. Moreover, the stakeholders, communications, risk management plan, and ethical issues are considered in the project with the output of the Project Management software. At last, the project development plan is provided in the study.
Description of the project
The firm is planning to develop a software application for the clients that have specific use into their organization. Through this software application, the firm can manage their work and team members by allocating their tasks on daily basis. The main purpose behind the introduction of this project is to the delivery of effective management through network services (Burke, 2013). This application would be helpful to manage the work task in an effective manner and work will be completed before the deadline as well as it will reduce the serious damages of work quality completing the task on deadline.
Project scope and project requirements
Project scope
This project is developed to build a software application. For this project, all the tasks and work are included in the project scope that needs to be done in the development of software application. In this, the planning, coordination, meetings, and reports or other managerial activities are included to achieve project scope (Kerzner & Kerzner, 2017).
Work Breakdown Structure (WBS)
In the project management and systems engineering, a work breakdown structure is a breakdown of a project into several small components deliverable. In this, the project is delivered to the team members in manageable sections to effectively complete the task.
In concern to this project, the below figure is explaining the WBS of this software development project:
Estimated time-line
There is a project regarding the development of a software application for the client. In order to complete the project in a timely manner, the project manager has explained that the project would be completed approx in a year. The company needs to complete the project within 12 months but it must have effective qualities (Harrison & Lock, 2017). The project would be started with identifying the work that requires to be done during the project. For this, different tools would be used such as business requirements analysis, work breakdown structures, gap analysis, and drill-down to developing an understanding of the project.
Resource needs and estimated cost
A number of resources are required to complete the project in an effective manner and the given table is representing the needful resources with an estimated cost:
| Title of resource | Quantities | Estimated cost |
| ISP provider | 1 | $50 per month |
| Telephony services | 1 | $20 per month |
| WAN provider | 1 | $40 per month |
| Connecting components | 1 | $20 |
| Computer system | 3 | $100 per computer |
| Operating system | 1 in each computer | $5 |
| MS project software | 1 in each computer | $3 |
| Share point software | 1 in each computer | $4 |
| SQL software | 1 | $10 |
In addition to this, it is defined that the company needs to provide a salary to the team members for completing the project. The given table is providing estimated salary for the team members:
| Role of the team member | Salary per month |
| Project Manager | $4,000 |
| Network Administrator | $3,000 |
| Software expert | $4,500 |
| Business Analyst | $4,000 |
| Total Cost | $15,500 |
Quality plan
During the project, it will be highly focused on the quality of the project for the client satisfaction. In order to complete the project in a timely manner, each step of the project should be structured and planned ineffective way. The teamwork philosophy statement is also achieved during the project planning (Nicholas & Steyn, 2017). In addition, other activities are also included in the quality such as identification of the resources, structures, stages, security measures, possible risk, and their solutions.
The below table is representing the activities review that needs to be verified and validated:
| Title | Project Manager | Software expert | Business Analyst | Network Administrator |
| Meeting 1 |
Reviews of the team members during the meetings and discussions. |
|||
| Meeting 2 | ||||
| Meeting 3 | ||||
| Discussion 1 | ||||
| Discussion 2 | ||||
Project stakeholders, communications, risk management plan, and ethical issues
Project stakeholders
The key project stakeholders for the project of building new software application include:
- Project owner
- Project sponsor
- Project manager
- System analyst
- System designer
- IS Development audit profession
- IT Technicians
- Project Team members
Communications management plan
The plan guide and maintains the information of flow among the project stakeholders. The key responsible person is a project manager to develop and execute the plan (Marchewka, 2014). The information that will be communicated includes design, testing, budgeting, reviewing roles and responsibility, project progress/status, project deliverables, key milestones, risk assessment, and management.
The communication plan for the software project is outlined below:
| From | To | Type of Information | Frequency |
| Owners | Project manager, and principal designer | Overall project requirement and expectation | As needed |
| Project manager | Owners and Sponsors | Approvals, budget report, project status report, a key milestone achieved and project deliverable completed | Once in a month |
| Project manager | Project team members | Project risks responses
Review the role and responsibilities of each team members Project deliverable progress |
Once a week |
| System analyst
|
Project owner
Project sponsor Project manager |
Project scope
Project features |
As asked |
| Project manager | System analyst,
System designer, IS Development audit profession and IT Technicians |
Work and standard guidelines
Project status Project audit reporting |
Once in 15 days |
| Project manager | Project team members | Project risks responses
Review the role and responsibilities of each team members Project deliverables progress |
Once a week |
| Project team members | Project manager | Agenda/ minutes of the meeting
Project risks and the reason for the delay Other project related issues Project status and progress |
On a weekly basis |
Risk Management Plan
This plan identifies the potential risk associated with the project along with the possibility and likely impact of risk, responsible person and the response that can be taken towards the risk.
| Description of Potential Risk | Reasons | Time occasion during project life cycle phase | Probability-
High/medium/low |
Impact –
High/medium/low |
Risk Owner | Risk response |
| Financial risk | -Change in the scope of the project
-cost overrun -Over exceeding budget
|
Executing | Medium | High | Project sponsor and project manager | Review and monitoring of expenses
Lower exceeding costs to keep the budget under control by adjusting with contingency budget amount |
| Time risk
|
Project delay and not meeting time schedule
Time overrun |
Executing and closing | Low | Medium | Project manager and team members | Make a provisional time schedule
Close supervision to achieve project deliverable and milestone as per updated timeline |
| Technical Resource risk | Lack of technical resources
Lack of IT support and facilities |
Planning and executing | Low | High | Project manager | Careful planning for IT resources
|
Ethical issues
The ethical issues for this project are related to compromise the professional ethics in executing and closing the project on time within budget. The ethical issue can be accountability to avoid the consequences of action or decision in determining scope, budget, failure of risk response and other project related issues. Another ethical issue can be a conflict of interest of interest among the project stakeholders and for the preference of key involved project members (Napier et al., 2009). The approach to deal with ethical issues to maintain honesty towards formal managerial process and practices as well as transparency in project scope and software project activities to complete the tasks as per required standards.
Project Management software outputs
| Activities | Duration | Starting date | Finish date |
| Planning (Define the project) | 15 days | 1-Oct-18 | 15-Oct-18 |
| Cost analysis | 15 days | 10-Oct-18 | 25-Oct-18 |
| Project scope analysis | 1 month | 15-Oct-18 | 15-Nov-18 |
| Requirement management plan | 1 month | 20-Oct-18 | 20-Nov-18 |
| Design Implementation | 2 months | 1-Nov-18 | 31-Dec-18 |
| Process improvement plan | 6 months | 1-Jan-19 | 30-Jun-19 |
| Quality plan | 1 month | 1-Jul-19 | 31-Jul-19 |
| Testing | 1 month | 2-Jul-19 | 1-Aug-19 |
| Documentation | 15 days | 1-Aug-19 | 15-Aug-19 |
| Training and Support | 1 month | 15-Aug-18 | 15-Sep-18 |
| Maintenance | 1 month | 1-Sep-18 | 30-Sep-18 |
Gantt chart
Project Deployment plan
The project deployment plan includes different strategies:
| Deployment strategy | Description |
| Concept strategy | The description of technological infrastructure, application of the project, communication network, and the current environment of the project are provided in this strategy. |
| Installation strategy | The development of high-level work-breakdown structure is included with Gantt-chart in this strategy. Additionally, the benefits and impacts of the proposed project are also included. |
| Communication strategy | The regular and proper conversation activities are involved in the project management. |
| Training strategy | The training strategy includes schedule, time and facilities for training are provided. |
| Financial analysis | The complete spreadsheet of the estimated cost and salary of the stakeholders are included in the financial analysis (Binder, 2016). |
| Master schedule | The Gantt chart uses for deployment in the project are included to complete it in a timely manner. |
Project signoff
| Topic | Description |
| Title of the project | Network Project Management for application software development |
| Start date | 1 October 2018 |
| End date | 30 September 2019 |
| Duration | 12 months |
| Project deliverables | The project deliverables are achieved |
| Signature from team member for completion of the project | There are four members in the team of project development-
1. Project manager 2. Network administrator 3. Software expert 4. Business analyst |
| Service owner signature | The company |
| Client approval (signature mandatory) | The client |
| Sponsor signature | |
| Project status | Completed |
| The actual date of completion | |
| Comments | If any |
Post project reviews and recommendations
There are some possible review feedbacks regarding resource requirement, communication plan, and project testing. In this, it is defined the company has used the old version for the system that created an issue. It is recommended that the company may have provided an advanced version that can be helpful to support the current stability of the server, requires low maintenance, and it is less risky. On the other hand, the feedbacks are getting regarding an improper meeting held and created the issue for communication plan (Leach, 2014). It is recommended that the company should provide proper documentation to reduce the miscommunication and disputes among the team members. In addition to this, it is reviewed by the client that the project testing was not proper. It is also recommended that the project manager should determine the risk possibilities and determine the proper functioning of the project.
Conclusion
From the above discussion, it can be concluded that this study has successfully developed the network project management on software application development. In concern to this, the project manager has used appropriate planning with the use estimated time-frame. It is also concluded that the project scope is established with identifying the stakeholder and required resources. In addition to this, work breakdown structure and Gantt chart are also designed with the use of MS project. In addition, it concludes the risk, communication skills and quality plan for the project.
References
Binder, J. (2016). Global project management: communication, collaboration and management across borders. Routledge.
Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
Clarke, H. J. (2012). U.S. Patent No. 8,306,841. Washington, DC: U.S. Patent and Trademark Office.
Harrison, F., & Lock, D. (2017). Advanced project management: a structured approach. Routledge.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Leach, L. P. (2014). Critical chain project management. Artech House.
Marchewka, J. T. (2014). Information technology project management. US: John Wiley & Sons.
Napier, N. P., Keil, M., & Tan, F. B. (2009). IT project managers’ construction of successful project management practice: a repertory grid investigation. Information Systems Journal, 19(3), 255-282.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and technology. Routledge.
Too, E. G., & Weaver, P. (2014). The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), 1382-1394.
Zheng, X., Le, Y., Chan, A. P., Hu, Y., & Li, Y. (2016). Review of the application of social network analysis (SNA) in construction project management research. International journal of project management, 34(7), 1214-1225.
Know more about UniqueSubmission’s other writing services:
