Project Status & Update

Project Status & Update

Richard M Wells

Kaplan University

IT599

Professor Rhonda Chicone

August 26, 2014

Table of Contents

Abstract

The meeting for the Status report will give us an idea of what and how to continue the next phase of the updates. We will be looking over the goals of the business and the breakdown of some changes that will be made to improve the function of each level. The security, firewalls as well as the IPCONFIG issues that have been seen with the newer upgrades and what has to be done to correct this.

Updated Project Plan

The project will be used to upgrade the facilities with newer equipment since the older systems are over 5 years old. The new system will allow better use of the system for tracking orders, shipping, and receiving as well as the use of the accounting department being able to complete the work on time. The servers will be better prepared for the use of the upgrades to perform the work better than before. The systems that have been in place for the past few years will need newer software to accommodate the faster system being put into place.

WBS (Work Breakdown Structure)

Planning phase consist of;

1. To have the development set up for the requirements for an upgrade.
2. Preparing security (physical and virtual)
3. Equipment testing and preparation
4. Project approval

Analysis phase will consist of;

1. The reviewing of the company’s plans
2. Infrastructure analysis
3. Data analysis for the newer software to be installed
4. Physical analysis of the company for the upgrades
5. Completion analysis

Designing phase will consist of;

1. Hardware and software needed to improve the older systems
2. Configuration of newer systems

Implementing phase

1. Changing over the older computers to the newer computers
2. Upgrading the routers, servers, switches and Ipconfig

Closure will include

1. Testing all of the system in a dry run
2. Updating all systems
3. Reconfiguring the systems
4. Project completion

Project Meeting Status

Pilgrims |MEETING

Meeting date | time 8/26/2014 10:00 AM | Meeting location Teleconference

Meeting called by

Type of meeting

Note taker

Timekeeper

Agenda topics

Time allotted | 1hour | Agenda topic Upgrades | Presenter Gregg

Discussion: What we will be upgrading and the departments from start to finish. We are having the accounting department to start with after the servers are completed.

Conclusion: We will be completing the updates for the next week meeting.

Project Summary

The project is going as expected with a few minor adjustments that are to be made before the next weekly meeting.

Future Goals

To fix any and all problems associated with the next upgrades to fix any issues set forth by the team. Updates with the intention of completing the accounting department in the next process. The completion of the server will be done this week.

Project Cost

The cost of the project has given us the ability to make the updates for the next five years without any adverse effects.

Revisions & Peer Review

The peer review and revisions that are needing to be fixed will include the risk identification and mitigation strategies, as well as the change management process. When working with the risk ID there is a very tempered time with the servers for the risk of losing the data that runs the organization on each site. There will be a cloud backup of the servers and a physical backup of the servers. The mitigations strategies will consist of fixing any of the risk associated with the servers. The IPCONFIG codes will also have to be updated on each device so the network is back on track.

Change Management Process

Phase 1 - Preparing for change (Preparation, assessment and strategy development)

Phase 2 - Managing change (Detailed planning and change management implementation)

Phase 3 - Reinforcing change™ (Data gathering, corrective action and recognition)

Conclusion

When working in the Pm field the PM needs to be certain of the data that is being shared as well as the time the project should be started and finished. Also make milestones for any unseen problems in the future of the project so the project does not suffer because of the deadline not being met.

References

Goclio. (2013, 12 8). Goclio. Retrieved from Goclio: http://www.goclio.com

Harvard Business . (2013, 11 3). Harvard Business . Retrieved from Harvard Business : http://hbr.org

Microsoft MSDN. (2013, April 20). Microsoft MSDN. Retrieved from Microsoft: http://msdn.microsoft.com/

SANS.org. (2013, 12 9). SANS.org. Retrieved from SANS.org: http://www.sans.org

Techknol. (2014, August 11). Techknol. Retrieved from Techknol: http://www.techknol.net/2013/04/software-development-life-cycle.html

Webopedia. (2013, 12 8). Webopedia. Retrieved from Webopedia: http://www.webopedia.com/DidYouKnow/Internet/ipv6_ipv4_difference.html