I wanted to share a recent experience I had with one of our newest customers. We’ll keep the name undisclosed for now, but these guys are a truly global company and a recognized leader in their industry.
When we first met the customer’s team, they were faced with the challenge of migrating away from antiquated technologies and hand coding into a platform that would allow their team to respond to business needs very fast but also with high quality and scalability. The team had evaluated tens of alternatives to achieve this goal and eventually decided on OutSystems
as a technology that would allow them to achieve their time to market goals without sacrificing quality or scalability.
I had the pleasure to be involved with this process from the beginning and on my last visit I was asked to help them define their migration strategy from the older technologies like Lotus Notes into a modern, web-enabled platform like OutSystems
. Now for the challenge: the team has been very prolific over the years and had well over a thousand Notes applications that need to be migrated, discontinued, or rewritten from scratch. The big question behind this process was clear – what is the most efficient way to determine which applications go where?
What goes where?
With this many applications it was almost impossible to understand the entire portfolio usage – let alone determine each application’s fate. Luckily, the team had been disciplined and kept track of useful information like application purpose, templates used, and change requests. Using an Excel file with all this information, the team built an OutSystems application in 5 minutes using IntelliWarp. The application was then used to determine a conversion score for each application, taking into consideration five important factors:
- Type of application – Applications that were primarily discussion based were deemed more adequate for other technologies, like Sharepoint. OutSystems applications are typically high-value, highly customized applications that you just can’t get out of the box;
- User population – Targeting reasonably small groups of users seemed like a sound strategy to initiate a technology deployment;
- Usage patterns – Because value comes from usage, the team decided that highly intense usage would be a good scoring facet for the applications;
- Development team – To ensure knowledge transfer happened smoothly, the old applications that were originally developed by team members staffing the new OutSystems dev group were preferred;
- Rate of change – The OutSystems Platform is all about change – the team wanted applications that are alive and evolving, with constant requests for new features or tweaks to existing ones.
Taking into account the above factors, our “secret sauce” conversion score algorithm yielded a migration score that determined the benefit of migrating an application to the OutSystems Platform. Because this was all done automatically and in just a couple of hours, target applications were defined and discussed much earlier than they would have been by any other means.
Next, the team took advantage of the ‘speed to change’ capability of the Agile Platform by extending the new portfolio management application to record the proposed migration strategy (destination platform) when it came time to replace each old application.
Curious to see what the new portfolio management tool looks like? The screenshot below shows the application (with data erased for privacy).
By using the speed of the Agile Platform, combined with technical skill and a healthy dose of pragmatism, the team was able to create the new portfolio application that helped them optimize a fundamental process in their work and bring more value, faster! – This is the essence of agility.
What about you? Do you have any similar success stories to share with us?