16 Strategy and roadmaps

 

This chapter covers

  • Building a compelling modernization narrative to generate excitement and buy-in
  • Structuring a modernization strategy deck
  • Starting with a small first slice and delivering value within three to six months
  • Ramping up modernization across the organization
  • Measuring and adapting continuously

Instead of continuing business as usual—developing new product features and working as you always have—modernization is an investment in a better future by spending time improving the architecture of a system and learning new ways of working. However, the idea of slowing down feature delivery is often perceived as bizarre by those without experience in software development and concepts like technical debt. So how do you persuade them that investing in modernization is in their, and everyone else’s, best interests? Equally, how do you get buy-in from employees who might be happy with the current setup and be concerned by potential changes?

When crafted skillfully in a language that speaks to all stakeholders, a compelling modernization strategy is an inspiring vision that sets the scene for a united modernization journey. It helps everybody to see how modernization will benefit them, increasing the chances of securing their buy-in. A good strategy connects modernization initiatives to business outcomes, enabling modernization work to be prioritized and sequenced into a roadmap showing how the inspiring vision will gradually become a reality.

16.1 Think big: Building a compelling vision

16.1.1 Crafting a modernization strategy deck

16.1.2 Industry example: Building and evolving a modernization strategy at IgluCruise.com

16.2 Nail it: Delivering a first slice within three to six months

16.2.1 Planning a first slice

16.2.2 Choosing where to start

16.2.3 When to think about internal developer platforms

16.2.4 What if things don’t go to plan?

16.3 Scale it: Ramping up modernization