Atlanta, GA 30310
ph: 678-362-9939
ronwilke
Infrastructure Migration
The physical machines were failing and causing an abnormal increase in production issues. By moving the Matrix42 Empirum software to virtual machines, we should have some reduction in costs.
Because we have the necessary hardware and software in house, we were dependent upon distributors for shipping. We were dependent upon internal resources being available to perform functions to complete the project.
The identified risk includes having available resources. Because there were unpredictable production issues, some of the resources used to repair those issues were also assigned to work on this migration.
Deployment Group | Number of Units | Date of Deployment |
Pilot | 1 | Thu 11/26/09
|
Rollout #1 | 25 | Tue 12/1/09
|
Rollout #2 | 100 | Thu 12/3/09
|
Rollout #3 | 200 | Mon 12/7/09
|
Rollout #4 | 200 | Wed 12/9/09
|
Rollout #5 | 200 | Mon 12/14/09
|
Rollout #6 | 200 | Wed 12/16/09
|
Rollout #7 | 200 | Fri 12/18/09
|
Rollout #8 | 200 | Mon 12/21/09
|
Rollout #9 | 200 | Tue 12/22/09
|
Rollout #10 | 200 | Wed 12/23/09
|
Rollout #11 | 253 | Thu 12/24/09
|
Solution Provided
The solution I implemented was successful because the methodology took the form of a standard RUP iteration plan.
Before rolling out in iterations, there were major items to be completed.
Afterward the testing of the first batch (NOC) we were able to move forward rather quickly recreating the successful plan. As the project manager my responsibility in Planning was to
| |
| |
| |
| |
| |
|
In execution my responsibility was to
Copyright 2010 Ron Wilkey II, PMP. All rights reserved.
Atlanta, GA 30310
ph: 678-362-9939
ronwilke