CMGT 444: Implementation Plan

CMGT/445 Implementation Plan – Week 4
To file a bug report, see Slide 14. Forward completed bug report to QA

Project Stakeholders
• David Bartmess
•
•

• Sr. Software Configuration Manager
• [e-mail]
Randy Allen
• Sr. Software Configuration Manager
• [e-mail]
Matthew McAdams
• Systems Engineer
• [e-mail]

Project Description
• The background of this project is that CCM, Inc., bought Procard, Inc., and is now looking to consolidate resources in the data server farms.
• All production and UAT (User Acceptance Testing) servers will move to the Atlanta Data Center and be hosted on hardware located there.
• The desired impact is to bring all servers into the same arena with the same equipment and cut back on employment
• The ROI should be reached within a couple years of the completion of the project.
The cost vs benefit is relatively small, since the cost savings in separate software package deals will bring the cost down and make it easier to maintain multiple servers. Project Scope
• What will be included in the scope of this project is:
•
•
•
•

•

Upgrading all offsite servers and software to current specs (i.e., Windows Server 2008 R2).
Installing new virtual servers in Atlanta Data Center.
Submit requests for ACL’s for all server connectivity.
Performing Disaster Recovery functions on all new servers (i.e., install all necessary third-party software and configure appropriately).

• Installing all current project software and configure appropriately.
The project’s main deliverables are:
• The completion of all new server build ups.
• The completion of all ACL connectivity issues.
• Successful startup of project software.

Project Schedule Summary
• The project schedule is liberal in respect to time for completion of each phase, because not keeping up with the project deadlines will cause problems with the development schedules as well, if the code freeze date of
December 20 is not
• All documentation will be in Microsoft Word, Excel, and Powerpoint.

• Assumptions used to develop estimates
• Personnel will work a minimum of 60% per week on the project.
• Servers in Golden cannot be taken down until the web configuration necessary to reach the Atlanta servers is completed and tested successfully.

• Key risks, probability of occurrence, and impact
• Software updates will be ongoing during the project, so the installation of software on the destination servers will be done once that version of the software is tested and approved.

• Organizational or time constraints
• This needs to be completed before the code freeze on December 20, so that any fixes to the software are completed and tested