The Quatronic Framework
The start of 2019 was very productive at Quatronic — we released the first version of SMART’s Digital Asset Management & Inspection Solution, released new versions of our internal applications based on the latest version of the OutSystems platform, and are already looking forward to our next update!
But first, let us tell you how we are going to create a digital footprint by applying principles like Poka Yoke in a software-driven world. How do we make sure each of our projects is a success? That is why we have developed The Quatronic Framework.
Toyota!
Building complex cars just in time with no concessions on quality is something Toyota does every day. Even though all cars of a model are made using standard components (like the chassis), a degree of customisation is still present. This results in many different varieties of cars being produced in a very efficient manner. How is that possible and how could we learn from that when building custom apps?
If Toyota builds cars that still drive for over 20 years and Airbus makes aircraft fly for over 20 years, why do most of the application not even survive their 5-year anniversary? Why are 60% of the IT projects still over budget? Have you ever wondered why some projects succeed and others do not?
We have experienced that application development is mainly focussed on the short-term delivery. Speed of development and meeting deadlines is often deemed the most important aspect in a software project, which often comes at the expense of the quality of the application. This results in a decrease in development speed over time, as shortcuts are taken, technical debt grows, and new features are built on top of an unstable foundation.
Our Way of Working
With our beta and engineering management background we know this could be done in a better way. We hate waste and inefficiency, which is why we are putting the Lean principles like Jidoka and Seven Wastes to practice in a software-driven world. Reducing waste to a minimum and streamlining the technical delivery means that we spend little time on repetitive technical tasks (building the “chassis” of applications). This allows us to spend more time creating features with real business value (the “customisation options”) while still ensuring high quality and scalable solutions.
That’s why we have developed The Quatronic Framework (Figure 1) that serves as a blueprint for our projects. It is a guide through a standardised process (manufacturing a car is not that different from developing an app in that sense). Checkpoints are in place to ensure that all necessary prerequisites are met when transitioning from one phase of the application lifecycle to another. For example, how to go from an innovative 3-day Design Thinking workshop to a modular and scalable architecture that has the same lifespan as an aircraft, while managing communications with the stakeholders?
In the coming months we will write a series of blogs to cover the different aspects of running a successful digital app factory. And of course, we will share our customer success stories with you!
