EN 
NL Introduction
Imagine: a telecom provider aiming to develop an application intended to serve the entire Belgium. One app where the customer can do everything. Everything? Everything! That’s what Proximus aims to achieve with the Proximus+ superapp. And the most intriguing part: Proximus has decided to develop this using the Mendix low-code platform!
I have been one of the fortunate ones to assist in this project, not in the role of a developer, nor as a tester, nor as a business analyst. I was involved in this project as an M-shaped Mendix specialist.
In this article, I would like to share how, as an M-shaped Mendix specialist at Proximus, I learned the value of thinking and acting multidisciplinary. And also why I strongly believe that this approach is crucial for the success of low-code projects, such as the Proximus+ superapp. Read more about M-shaped Mendix specialists in our previous story.
My role at Proximus
My role as an M-shaped Mendix specialist in the Mendix project for the Proximus+ superapp presented me with challenges that tested not only my skills as a business analyst but also my technical expertise as a Mendix developer.
A major challenge in the initial months was understanding the complex technical backend. Due to my lack of experience with native applications, the complex microservices architecture, and the usage of custom code, working on user stories was like navigating a maze. Subsequently, testing these user stories was further complicated by the nature of the native app (mobile-only) and the complexity of the microservices architecture. For every journey (mobility, neighborhood, home, telco, etc.), a standalone backend Mendix app was created, each integrated via REST calls and UI modules with the ‘main’ frontend customer application. The aim was to ensure that the customer could do everything through the Proximus+ app.
However, the acquired knowledge and experience with the backend proved to be extremely valuable in enhancing my effectiveness in my business analysis tasks, which received increasing focus in the project. As a result of the experiences gained in the first few months, I was able to conduct much better analyses (both in terms of process and technology) and proactively come up with valuable quality improvement proposals. I made technical proposals, including suggestions based on AQM and my own findings. In terms of process improvement, I proposed closer collaboration with the other business analyst in the team and scheduling focused time.
Another aspect of my role involved coordinating complex analyses and integrations. For example, I had to facilitate an integration to retrieve consumed and produced energy data for the user of the app. This required close collaboration with various stakeholders, including the external party providing the API, our UX specialists, developers, translators for multilingual interfaces, and Proximus’ security department. My skills in communication, persuasion, and requirements engineering were instrumental in this process. Mapping the technical impact required not only an understanding of the process but also profound knowledge of Mendix to fully understand how the integration should ultimately be built.
Mapping the technical impact required not only an understanding of the process but also profound knowledge of Mendix to fully understand how the integration should ultimately be built.
The added value of the M-Shaped approach
The above challenge was a prime example of the versatility required in an M-shaped approach.
Leveraging my Mendix expertise, I was able to develop a proof of concept to validate integrations and conduct system tests before development even began.
Thanks to my experience in testing, I could easily translate acceptance criteria into test scenarios, preparing the tester to execute their work. This proved particularly valuable as the testers themselves lacked specific knowledge of Mendix.
With my experience and knowledge of business analysis and requirements engineering, I could effectively communicate with the business and with IT to ensure a thorough analysis.
With this broad knowledge base, communication with external parties became smoother, technical analysis didn’t necessitate developer intervention, and testers were integrated earlier in the process. The M-shaped approach notably enhanced efficiency and effectiveness.
During the final sprints leading up to the launch, the focus was entirely on resolving bugs, resulting in less priority given to picking up new analysis stories. As an M-shaped Mendix specialist, I was able to assist developers by taking on bugs myself, conducting peer reviews, and contributing to testing efforts. Due to my multidisciplinary nature, I could adapt and be deployed to areas where the highest priority was at that moment. This highlighted the potential of a fully multidisciplinary approach and strengthened my conviction that this is the future we should strive for.
Due to my multidisciplinary nature, I could adapt and be deployed to areas where the highest priority was at that moment. This highlighted the potential of a fully multidisciplinary approach and strengthened my conviction that this is the future we should strive for.
In addition to embracing a multidisciplinary approach, the strength of an M-shaped specialist lies in having in-depth knowledge of the platform on which they analyze, develop, test, prioritize, and manage. A proficient business analyst will still lag behind an ‘average’ one who is familiar with the specific platform being used. The same applies to testers, administrators, and product owners. Understanding what works for, in this case, Mendix projects and what Mendix offers out-of-the-box, significantly enhances the efficiency of the M-shaped specialist. The term ‘specialist’ emphasizes expertise in the platform, which is the true specialization of an M-shaped professional. This is what makes the M-shaped approach so powerful.
Reflection
As an M-shaped Mendix specialist at Proximus, I have gained a deeper understanding of the importance of multidisciplinary work and the value of an M-shaped approach in low-code projects like the Mendix project for the Proximus+ superapp. During this project, the management aimed to transition teams towards T-shaped structures, where members excel in one discipline and have basic knowledge of others. However, my experience demonstrated that taking a step further towards an M-shaped approach offers even greater benefits.
For me personally, this project presented an opportunity for growth. My focus was primarily on business analysis and Mendix development, and I have significantly improved my skills in both areas. I gained valuable experience with native applications and working within a complex microservices architecture. Additionally, I have become more adept at translating technical solutions into understandable language for stakeholders and coordinating with various teams and disciplines.
My time at Proximus has taught me the importance of not only having in-depth knowledge in a single discipline but also being capable of thinking and operating broadly, all while maintaining expertise in the platform. A highlight of this project was my involvement in integrating the energy data API from an external party. This was a pivotal moment where my M-shaped approach made a clear difference in the efficiency and effectiveness of the project.
I am convinced that M-shaped specialists will become increasingly important in the rapidly changing world of low-code. I hope to inspire those around me to become multidisciplinary and continue expending their scope without losing sight of platform specialization. This is valuable not only for individuals, but also enables better advice to clients and a more holistic approach to complex challenges.
M-shaped teams.That is my vision of the future.That is my ‘Anamata’.
Get your boarding pass at Anamata
Anamata is always looking for new colleagues to hop on our plane. If you want to become an M-shaped Mendix specialist or if you want to broaden your knowledge to other disciplines, please contact us so we can help you with your journey.
Maybe you are interested in developing other areas as well? In that case, Anamata provides the opportunity to learn more about Pega or business consultancy. Let’s have a drink today, so we can talk about tomorrow. Maybe this will result in a great journey for both of us.
