Skip to end of metadata
Go to start of metadata

1. Hypothesis

It's going to be impossible to modernize our legacy apps enough to get them into a cloud environment.

"We believe that with the right resources, even old VB6 apps can run effectively in Azure.  We have not yet met a legacy app that we were unable to shift to a cloud environment".


2. Problem

Legacy application support (or lack thereof) is going to block our plans to modernize our infrastructure but are going to be too expensive to outright replace.


7. Ideas

Legacy applications are a specialty of Bluejacket Software.  We love taking old creaky code and investing in it's rehabilitation into whatever environment our customers require.


6. Value

Why migrate legacy apps instead of replacing them?

  • Cost
  • Corporate knowledge
  • Retraining on new systems


4. Stakeholders

CEO's, CTO's, CIO's are often the stakeholders when considering how to extend the investment in legacy applications.

Airline example: "CEO, pilots, travel agents, air regulators".


3. Customer personas

Regional or Global companies that have a significant investment in legacy applications such as LOB etc. often delay realizing cloud infrastructure advantages because they believe they cannot migrate old, unsupported legacy applications that their company depends on.


8. Minimum viable experience

The PM, Architect, Engineer, and Developer can all be the same person if the project is small enough.  For enterprise applications, right-sizing the team will be important.


5. Team

Project Manager, Software Architect (reverse engineering), Senior Development Engineer (conversion planning) and Software Developers (coders)


10. End to end demo

One of our clients is in the Petro-Chemical regulation industry.  We were tasked with taking their legacy, unsupported, customer facing application from a local data center and host it in MS Azure.  We were not able to speak with the original developers or the infrastructure team as they were unavailable.  From a cold start, and a badly managed source tree, we were successful in not only creating a development environment to quickly fix existing bugs, but were able to leverage that work into a CI/CD pipeline in Azure that allowed us to hand off to incoming developers quickly and efficiently.  This migration was done over a period of a few weeks and required zero down time for customers.


9. Metrics

We measure our success by what our stakeholders define as requirements.  From downtime to ramp-up time, we track and provide client visible dashboards of project progression and costs.  We measure our success on your success.


Learn more:

This work, the 'Experience Canvas', is a derivative of 'The Business Model Canvas' by used under CC BY-SA 3.0. This Experience Canvas is licensed under CC BY-SA 3.0 by Atlassian.