How Ardoq Helped Them Establish a Quick Foundation for Strategic Transformation
Ardoq empowered Elkjøp to quickly sort through the unknowns and fast-track their transformation, speeding up painful onboarding processes.
1 . Getting the As-Is Overview of Their Application Landscape
With over 200 applications in their landscape and numerous in-house developed microservices, Elkjøp needed to find a way to streamline. Application Portfolio Management with Ardoq allowed them to get a top-level perspective to see which applications and technical objects were unnecessary and good candidates for removal.
“One of the systems we replaced had been with us for 30 years. We needed to change into a more composable architecture and move to a more agile way of working.”
- Trond Andersen
Getting the overview of how the entire landscape was interconnected relied heavily on Elkjøp’s IT organization. The project was under a lot of pressure to meet deliverables and timelines. Through the use of Ardoq, Elkjøp was able to keep a high-level view of the application portfolio and its transition stages. Orchestrating and controlling the transitions was imperative as Elkjøp was operating legacy systems and transitioning to the new stack in parallel.
2. Defining Elkjøp’s Capabilities and How They Connect to Teams and Applications
Transparency of their application portfolio was just the beginning for Elkjøp. They also needed to find a way to get transparency in terms of the organization and the adjacent responsibilities to document “who does what.” Business Capability Modelling in Ardoq helped them develop the map that could help anyone in the organization easily answer key questions that had long been challenging to find clear answers to, such as:
- Who is responsible for this?
- Who can make decisions?
- Which teams and applications are related to this?
This meant that anytime they were about to start an initiative, they could look at which capabilities were involved and which capabilities were needed. Teams can quickly understand who they need to consult and how it links up to the existing technology and information via a “toolbox” that Elkjøp had already created in Sharepoint with the insights from Ardoq. This toolbox contained all their development tools, data sources, dependencies, security measures, etc. that are critical for new initiatives. Through this toolbox, Elkjøp can ensure that projects started by product teams align with necessary processes and governance.
They also recently presented their architecture at the SAP Customer Experience Forum in Amsterdam and how they have mapped their business capabilities to supporting applications and building a composable architecture - including SAP business applications - to define semi-autonomous product-aligned teams.
“We see the trend towards semi-autonomous product-aligned teams throughout the industry. The way Elkjøp has captured the areas of responsibility for those teams in a complex IT environment with a significant SAP landscape in our platform is very interesting and has great potential for many other organizations.”
-Jason Baragry, Chief Enterprise Architect at Ardoq
3. Architecture Roadmapping for Different Domains
With an understanding of their technological landscape through APM and how it connects to the business’ capabilities, Elkjøp then had a foundation to start road mapping exercises to address the current and future needs for different domains. Their goal was to evaluate how well-equipped the organization was for its objectives in specific functions and whether they could reach targets with their current technology.
The EA team involved both business and IT people in the road mapping process through whole-day collaborative sessions where they could deep dive into the objectives for both technical and business-oriented focuses and come to a common understanding of what was needed.
Ardoq was used to conduct as-is assessments for the different domains, to evaluate their current applications. Ardoq made it easy for them to involve many people in this process, visualize costs in each domain, and generate clear observations and suggested actions.
The final step was the actual road mapping exercise, where they polled users in these domains on which proposed elements were most important to implement. This allowed them to ensure that they prioritized the most valuable things for each domain from the perspective of hands-on people in each domain. It was a very successful process that aligned both business and IT to reach a common understanding of business and technical performance, thus identifying future needs.
4. Closer Coordination with Owners to Align and Streamline
Elkjøp was also beginning to have closer dialogue with their owner, Currys, to identify opportunities to streamline for both sides. For example, finding opportunities to merge licensing agreements or aligning on the kinds of systems both sides were using. The big question they were trying to answer was, “How to be better together?”
They hadn’t had much dialogue before when it came to processes, capabilities, and IT, so they needed a clear overview of both sides to begin having meaningful conversations about streamlining.
Currys was not using Ardoq but Elkjøp’s EA team managed to put an overview of their architecture in the platform, link them to domains, and then remap how Elkjøp’s landscape was organized to align with Currys’ layout.
From this common structure, they could then see a clearer side-by-side comparison of domains which helped them to create a common ground for conversation. This foundation has already greatly sped up and facilitated dialogue on technology sharing in both directions.