Structured for success

Our six-part series of articles covers all important aspects of software modernisation. This is the second article in the series. An overview of the topics is provided at the end of this article.

Companies are facing a fundamental challenge: if they are to remain competitive and keep pace with the speed of technological developments, their existing software solutions need to be continually modernised. Legacy systems that have often existed for years with little attention paid to maintainability can no longer keep up with today’s dynamic business world.

Yet, modernising such systems is complex. It requires a deep understanding of the existing IT landscape, the business goals and technical requirements, while all the time ensuring smooth operation of applications and systems during the modernisation process. Companies face the challenge of making the right decisions regarding the modernisation strategy – whether that involves a complete new development or gradual adaptations. The risk of bad investments and unnecessary delays is high if the modernisation is not carefully planned.

These risks can be mitigated by following a structured approach. This is where bbv’s Software Modernisation Canvas comes into play. It was developed as a comprehensive tool for structuring modernisation projects and replicating all relevant factors on one clearly laid out page.

1. Introduction

The Software Modernisation Canvas is a strategic tool developed specifically for planning and implementing software modernisation projects. The canvas offers a visual, structured framework for depicting the diverse aspects of a modernisation project on one page. The aim of the canvas is to systematically record and coordinate all relevant factors – from the technical requirements to the business goals through to the financial requirements.

By following this visual and interdisciplinary approach, the canvas facilitates exchanges and collaboration between different stakeholders, for example IT teams, management, project management and external partners. A clear structure helps to avoid misunderstandings and to guide all stakeholders in the same direction. “The Software Modernisation Canvas creates a universal language”, says Britta Labud, Senior Software Architect .NET at bbv. “The framework enables clear and concise discussion between all stakeholders on the necessary steps and challenges posed by the upcoming software modernisation.”

2. Layout

The Software Modernisation Canvas is divided into a number of fields, each of which covers a specific aspect of software modernisation. These fields help to provide a holistic view of the modernisation project and ensure that no key aspects are overlooked.

Pain points: This is where the main problems with the current system are recorded. These can include technical debt, obsolete architectures, performance problems or lack of functionality. The pain points form the starting point for the modernisation.

Working well: The existing strengths of the system are also considered. What works well? What should be retained? These positive aspects should continue to form part of the new solution, thus ensuring that no existing advantages are lost.

Business opportunities: Software modernisation is never an end in itself. In the business opportunities field, all stakeholders identify the opportunities offered by software modernisation and how they can help to increase revenue or reduce costs. Use of new software often offers potential for new business fields, too. “Recognising these is often critical to the success of modernisation”, says Marco Ravicini, Senior Software Architect and Member of the CTO Board at bbv.

Stakeholders: Which stakeholders are affected by the modernisation? Stakeholder management is a key success factor, since different interests have to be considered and brought into line.

Constraints: This field identifies the personnel and technological constraints that have to be considered when performing the software modernisation. These factors define the boundaries within which the modernisation strategy has to operate.

Solution ideas: Based on the problems and opportunities identified, possible solution approaches are outlined here. Several alternatives are looked at to allow scope for different strategies.

Modernisation strategy: This area of the canvas is devoted to the specific implementation strategy. How will the modernisation be performed? Should it be a gradual adjustment or a complete redevelopment? How is the transition from old to new system ensured?

The layout of the canvas is designed to gradually allow the modernisation requirement to be clarified and to develop a sound strategy. “The clearly laid out canvas allows the complexity of a modernisation project to be concisely presented on one page”, highlights Britta Labud. “It therefore provides all stakeholders with a clear understanding of all the steps and factors at the heart of the modernisation.”

3. Application

The Software Modernisation Canvas is typically used in an interactive workshop, in which the bbv experts act as moderators and advisers. The aim of the workshop is to bring together all stakeholders to develop a shared view of the modernisation project and create a realistic roadmap. Attention not only focuses on recording technical details, but also on strategic orientation and appropriate stakeholder management during the entire software modernisation.

3. 1. Preparation

Before the workshop begins, bbv identifies all stakeholders together with the customer. This includes both technical experts and business decision makers. “It is especially important that all key stakeholder groups are involved from the outset”, explains Marco Ravicini. “This ensures that different perspectives – from business requirements to technical aspects – are considered in the planning.”

3. 2. Situation analysis

During the workshop, a detailed situation analysis of the existing software is carried out first, which identifies the pain points of the current system – as well as its strengths. Companies often overlook the positive aspects of their existing systems, because they are focusing exclusively on the problems. bbv provides support here by asking targeted questions to ensure that all aspects of the existing software that are working well are identified and included in the modernisation strategy.

3. 3. Identification of business opportunities

In the next step, bbv analyses the business opportunities that modernisation might offer. This is critical if the modernisation is to be seen not only as a technical challenge but also as an opportunity to develop new business models or increase efficiency. “bbv includes insights here from the consultation to identify potential business opportunities offered by new technologies”, says Labud.

3. 4. Stakeholder management and constraints

The success of a modernisation project often depends on whether the interests and expectations of all stakeholders – from developers to management – are taken into account. “The more stakeholders around the table, the more comprehensive the overall picture”, stresses Ravicini. Project limitations in terms of budget and time constraints as well as technical requirements are also analysed here. bbv supports companies in settings realistic goals and requirements to ensure that the modernisation can be implemented with the available resources.

3. 5. Development of solution ideas

Once the pain points, stakeholders and constraints have been recorded, bbv develops a number of solution ideas together with the customer. Various solution approaches are outlined for addressing the identified problems and exploiting the business opportunities. “We offer our experience from a range of modernisation projects and outline possible solutions based on modern technologies”, explains Labud. It is critical to have a number of options available to be able to respond flexibly to the project requirements.

3. 6. Creation of the modernisation strategy

The modernisation strategy is defined at the end of the workshop. This involves defining the long-term strategy for modernisation. bbv helps customers to make the right decision, whether gradual migration, combining old and new technologies or complete redevelopment. The technical and strategic direction must be elaborated jointly so that the software modernisation meets all company objectives.

The entire process is designed iteratively and flexibly. “Companies should not just finalise the canvas at the start of the modernisation, but should continually reassess and adapt it during the course of the project – especially when new requirements or stakeholders suddenly emerge as the project develops”, says Labud. “This is the only way to ensure that the software modernisation can be completed dynamically and flexibly.”

4. A roadmap for complex modernisation projects

The Software Modernisation Canvas offers companies a clear and structured approach to planning and implementing software modernisation projects. Thanks to the clear visualisation and interdisciplinary approach, it encourages exchanges between the different stakeholders and helps to take account of all relevant factors.

Especially in complex projects where technological, organisational and financial aspects are intrinsically linked, the canvas is a valuable tool for creating a universal language and an understanding of the modernisation goals. The success of a modernisation project depends on whether all stakeholders understand the challenges and opportunities and work together to develop a solution. The canvas offers the ideal framework in this respect and ensures that no important aspects are overlooked. For companies facing the challenge of software modernisation, the Software Modernisation Canvas is therefore an indispensable tool for strategically approaching and successfully mastering this challenge.

Further articles on software modernisation in the bbv blog:

• Blog #1: Software modernisation: Everything you need to know
• Blog #2: Software Modernisation Canvas: Structured for success
• Blog #3: Strategies for successful software modernisation
• Blog #4: The five most important factors for successful software modernisation
• Blog #5: The future of legacy systems: from modernisation to evolvability
• Blog #6: Artificial intelligence in software modernisation