Delivery in day(s): 4
MN601 Network Project Management Paper Editing Services
Section1: Executive summary, introduction, logical structure and conclusion
1.1. Executive summary
The approach of project management is to maximise the speed flow in development of a project with the help of a deployed project team. The deployment of project ensures the best experience for the customers. The qualified professionals are involved in the development of the real world networking industry. The skilled experts bring the specific solutions for the complex problems and provide an independent view for the relevant technical recommendations. The networking which involves new technology involves complex challenges to any organization strategy and the third party is involved which is commonly called as service providers. The project management software includes the MS project and the ability of this software is that it can tie all aspects of project in a encapsulated unit. It provides relatively easy way to create plan for the network installation. The setting up of project plan draws a time frame which has many dividends over the course of the network project (Schaffer, 2009).
The management of networking is typically a well-planned structure in the technical aspects of project. The configuration of devices such as router and switch, deployment of server and other deployments depends on management structure of whole project. The training part is most important which includes the employee skill development for the operation of developed project.
1.3. Project title and description
Table1: Project Description
Title of the project
Network Project Management for Server development
24 September 2017
23 September 2018
To achieve a project planning document based on overall parameters with appropriate project plan and quality check to complete the project.
1.4. Project team members
Number of team members: 4
Table2: Team Description
Title of Role
Management expert, planning expert, quality expert, financial expert
Networking expert, testing expert, developer, quality expert
Resource expert, testing expert, training expert
Business expert, scope expert, financial expert, quality expert
1.5. Logical flow diagram
Section2: Project scope and project requirements, project crashing.
2.1. Project scope
The project scope is an important part of the implementation plan of the network project management. The aim of the project is to achieve the appropriate planning of the project with respect to time estimated and good quality level.
2.2. Estimated time?line
The total estimated time will be 12 months and the project is divided into seven stages. Each will have its appropriate time for completion. Thus time estimated is divided into seven parts. The project will achieve completion on time if each is completed within expected time.
2.3. Project requirements
(1) Functional requirements: The functional requirements involve the hardware and software requirement. The hardware requirement involves the small dataset, medium dataset, and large dataset. The software requirements are operating system, share point server and SQL server. The last thing which is required is Project Server (latest version).
(2) Non-functional requirements: The non-functional requirements involve the client requirements which include the project professional compatibility, project installation requirement, project professional office and Web app requirements.
2.4. Crash the total project duration
Ms Project will be used for crashing the project duration by 2 weeks.
2.5. Stakeholders’ roles and responsibilities
Table5: Team responsibility
-timely deliverables of the project
-providing solutions for the problem during complexities in project
-continuous communication with the team members in professional manner
-provide solution for complexity in server issues
-identification of resource requirement and finalizing required resources for the project
-testing and maintenance of server
-developing training session for employees
-easily operate on operating system, share point server and SQL server
-MS project implementation on time
-providing surety in availability of identified requirements
-maintenance and updating of hardware and software
-manage financial aspects of project
2.6. Resource needs
Table6: Resource requirement
Title of resource
MS project software
Share point software
Section3: Project stakeholders, communications, risk management plan, and ethical issues.
3.1. Quality plan
Team philosophy:The team should focus on the good quality of project for the clients. Every step of the project should be goodstructured and planned so that it gets completed by estimated time. I have achieved the teamwork philosophy statement. The next part in quality comes that all the requirements should be achieved with respect to project plan. The timely accomplishment of project requires the conduction of many activities which can identify the resources, structures, stages, doubts and their solutions, possible risk and security measures.
Table7: Activities Review
Verification and Validation of activities
The activities need to be verified and validated by the attended team members by the help of regular attendance during meeting and providing signature on their commented reviews. The activity during the project management includes meeting, discussions, and training.
Table8: Activity Validation
Signature from respected team members.
3.2. Stakeholder analysis
Table9: List of Stakeholders
List of name
Local internet users
Social media users
Power/ interest graph description:
1. High power, interested people
These people have full engagement towards the development such team members and make highest efforts to satisfy the requirements.
2. High power, less interested people
These people are the users of the developed project; they don’t engage in functionality of the project but in engage in the application of the project.
3. Less power, interested people
These people are interested in good quality of project application such as private and popular organization.
4. Low power, less interested people
The people have not much excessive communication with respect to project. These are the local user of server such as users of social sites.
3.3. Communication plan
Communication plan includes the methods of communication between team members for sorting the different stages of the network project management. The methods include meetings, discussions and free time conversation. The timing of the meeting should be fixedin morning in morning for one hour from 9:00 am to 10:00 pm. The meeting should be attended by each member and making it compulsory will make the project successful. Regular discussion after lunch break should occur to boost the project development and for doubt clarification. The doubt session should be organized separately. Data should be shared through Email with proper encryption.
3.4. Risk management plan
The risk management plan includes:
Phase 1: Risk Identification
The possible risks are identified during testing phase of the project development which includes risk at technical level, cost estimating level, scheduling level, in miscommunication with client, financial, political, environmental and by the users itself.
Phase 2: Categorizing risk
The risk should be categorized on the basis of two factors. The factors are the impact of the risk and likelihood of happening of risk. The impact of risk categories the risk in three levels which are high level, medium level, and low level. The likelihood of the risk divides the possible risk into three levels and these levels are their possibilities of happening- unlikely, likely and very likely.
Phase 3: Mitigation of risk
Mitigation is done on the basis of following factors:
a. Avoid: The best method is to prevent the risk from happening and definitely it will not affect the project. It usually involves the development of alternate method where probability of risk is high.
b. Share: It involves sharing of risk mitigation activities during risk occurrence so that it should resolve as faster as possible. Many organizations have strategies to divide their possible risk into different departments and these departments handle them in a different manner.
c. Transfer: This method involves shifting of risk from project to another risk solution providers. The best example of risk transfer is providing insurance to equipment and software.
d. Reduce:This method involves the reduction of risk on the basis of funded amount from the sponsors.A project manager assigns the risk cost estimation to the experts so that a proper safe backup can be taken from the sponsors.
3.5. Estimated cost
3.6. Ethical issues
The responsibilities of project manager and its team members are high in considering the ethical issues for being a good team member and citizen. The most common ethical issues analyzed in the project management are:
1. Ignoring health of the employees
2. Making partially deals and not closing deals properly
3. Assigning fraud employees for the project
4. Biased behavior of the project manager
5. Disputes in not accepting own mistakes in teamwork
6. Not maintaining public interest in completion of project
7. Non-professionalbehavior during project development like coming late at meeting venue
8. Dishonest and non-competence behavior towards project (MAJEED, 2012).
Section4: Project Management software outputs
4.1. Work Breakdown Structure (WBS) and Gantt Chart
4.2. Network Diagram
Section5: Project Deployment plan
It involves the completion of following strategies.
Table12: Deployment strategies
It provides the description of technology infrastructure, communication network, application of the project and current environment of the project.
It involves development of high-levelwork breakdown structure and Gantt chart. Further, it includes the benefits and impacts of proposed project.
It involves proper and regular conversation activities during the project management.
This strategy includes the training schedule, training time and facilities provided.
It includes the complete spreadsheet of the estimated cost of the resources and salary of the stakeholders.
This includes use of Gantt chart for the deployment of project in a timely manner.
Section6: Project signoff, project review and recommendations
6.1. Project signoff letter
Table13: Project signoff letter
Title of the project
Network Project Management for Server development
24 September 2017
23 September 2018
Signature from team member for completion of project
Project manager -
Service owner signature
Client approval (signature mandatory)
Actual date of completion
Comments (if any )
6.2. Post?project review and Recommendations
This includes the possible review feedbacks and possible recommendations
Table14: Table for review and recommendation
Name of the stage
Feedback from clients and sponsors
1. Resource requirement
Old version used
Possibly advanced version should be used
-advanced version will support current stability of server
-less maintenance is required
-less risk of threat occurrence
Meeting not properly documented
Regular meeting should be scheduled
-proper documentation will provide solution of some unwanted miscommunication
-less dispute will raise
3. Project testing
Testing is not properly documented
Risk may arise, need proper documentation
-determine risk possibilities
-provides knowledge of any threat in any hardware.
-determines proper functioning of project.
The Network Project Management on Server development is successfully created. The appropriate planning is developed with the estimated time frame. The project scope is established with stakeholder and resource identification. The work breakdown structure and Gantt chart are developed on MS project. The risk, communication skills and quality plan is discussed. The other factors such ethical issues, deployment plan, project sign off, recommendation are achieved.
Section7: Reference and appendices
Borysowich, C., (2009). Deliverable: Project Deployment Plans. Toolbox. Retrieved fromhttp://it.toolbox.com/blogs/enterprise-solutions/deliverable-project-deployment-plans-30036
John, V., (2015). Post project preview. Slideshare. Retrieved fromhttps://www.slideshare.net/SilverMkenda/post-project-review
PMG, (n.d.).Project management initiating tools and techniques.projectmanagementguru.Retrieved fromhttp://www.projectmanagementguru.com/initiating.html
Pwgsc, (n.d.).Risk Management plan template. Pwgsc. Retrieved fromhttps://www.tpsgc-pwgsc.gc.ca/biens-property/sngp-npms/bi-rp/conn-know/risque-risk/plan-eng.html
Rao, T. R. (2012).Project Sign Off Template. Slideshare. Retrieved fromhttps://www.slideshare.net/TarakeshRao/project-sign-off-tempalte
Schaffer, G. (2009). Project management for networking geeks. ITworld. Retrieved fromhttps://www.itworld.com/article/2769683/networking/project-management-for-networking-geeks.html
Thompson, R., (n.d.).Stakeholder Analysis. Mindtools. Retrived from https://www.mindtools.com/pages/article/newPPM_07.htm
Thompson, R., (n.d.). Stakeholder analysis.Mindtools.Retrieved fromhttps://www.mindtools.com/pages/article/newPPM_07.htm
WATT, A.,(n.d.). Risk Management planning. Opentextbc.Retrieved from https://opentextbc.ca/projectmanagement/chapter/chapter-16-risk-management-planning-project-management/