The Doppler Quarterly Summer 2018 | Page 71

• V3 of wave schedule ( dependencies )

• Group apps together based on their dependencies

• For selected apps in wave x , move the dependent apps into that wave ( if they are not already there )

• If the number of apps in a wave exceeds the expected migration velocity , adjust / move nondependent apps to the next wave , and continue through the remaining waves

• V4 of wave schedule ( complexity , app tiers )

• Irrespective of the scores , we should make sure we are migrating a good mix of less complex and more complex apps in a duration ( we do not want to leave all complex apps at the end or the beginning ). When the migration velocity is calculated , an additional factor is the mix of complexity in each time period . Complex apps may require additional staff , additional duration , reduced downtime , etc ., and these things influence the velocity .

• Rebalance the wave with the desired mix of less complex and more complex apps . What we generally recommend is to start and end with less complex apps , and add more complex apps in subsequent waves . This logic may need fine tuning based on specific requirements .

Figure 1 displays an example of a summary wave schedule .

Figure 1 : Summary Wave Schedule

SUMMER 2018 | THE DOPPLER | 69