David KazinaPM III| Postmedia NetworkWinnipeg, Manitoba, Canada
The project is server migration to a new domain. The migration itself is a simple task for the OS support team. The challenge is the application impacts and required changes/testing. Because the app teams are not familiar with the potential impacts and the OS team is not aware of the app restrictions I am finding it a huge challenge to try to come up with a strategy to size the effort. Getting 30 people in a room and talking it out doesn't seem practical/possible.
The scope of this effort is across over 100 applications and 400+ servers. Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Hi David -
My recommendation is something along the lines of below. What is seemingly the tough piece of the puzzle is the lines of ownership/responsibilities. It will always be difficult to gather large disparate business groups or application owners into an effort they see as IT owned and disruptive to BAU activities.
- Determine the application owners
- Migrate in waves
- Communicate to application owners which wave their application is part of, expectations, date-range
- Hold open meetings for each wave to highlight/discuss open issues
- Clearly state that testing is the responsibility of the application owner and must take place during the assigned wave/date-ranges. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
If the application team are not able to evaluate the impacts into a change then you are lost. As you know a change on servers could demand a change on other things than operating system. For example, all related to network. So, your application team must be able to evaluate impacts. I was the leader of a whole datacenter migration where an amount of servers and applications higher than you stated were involved including ir some of those servers were critical to continue manufacturing and delivery process. Saving Changes...
You'll need to develop some sort of model which can be used to help size the effort. Assuming there are SMEs who understand some subset of the applications, you could use a simple complexity-based t-shirt sizing model to try to come up with a ROM.
hello all,
I am seeing that the post is a bit older, could someone share with me some templates that you are using for applications migration
many thanks in advance! Saving Changes...