Agile Realities: Adapting Organizational Models to reality

In my work, I have been confronted a lot with the crucial question of how to establish an effective connection between business and IT. In the pre-Agile era, this responsibility typically fell on the Business Analyst, who would hand over business requirements (needs) to the Functional Analyst for conversion into a functional design (solution). However, even then, discussions revolved around:

Should a business analyst be part of the business or IT team?
Where are the boundaries of a Business Analyst versus a Functional Analyst, considering cost and technical restrictions that may challenge certain business needs.
Who takes care of small enhancements for which there is no need of a detailed and complex analysis and process?
Who makes the bridge with the end-users and all non-IT activities (like marketing roll-out, process adaptations…)? To fulfill these requirements, organizations often introduced additional roles such as Process Analysts, Business Owners, or Business Application Owners.
…

With the rise of Agile methodology, the traditional roles of Business Analyst and Functional Analyst have given way to new positions like Product Managers and Product Owners. Although the way of working has evolved and these new roles come with different responsibilities, the pain points and discussions remain the same as before.

In these discussions everyone seems to have a proposal for the perfect organizational model. However, in reality, organizational models are always a compromise, depending on the skills of individuals and the nature of the work. Considerations include:

Project Size: the organization for a 1000 manday project differs from a small 2 manday evolution.
Project Type: a technical project (e.g. refactoring or setup of new monitoring system) requires a different organization than a business project. And even 2 business projects can be very different. E.g. a project which is very UI oriented requires a different approach than a project, where a back-end workflow is modified, despite both having significant business impacts.
Existing Logic vs. Building from Scratch: projects that adapt existing logic/code are organized differently from those that involve creating new applications or features. Similarly, implementing a custom-built application varies significantly from implementing a packaged solution.
Programming Approaches: Low-code/No-code applications enable developers to work closely with the business and iterate more rapidly, unlike traditional programming languages. AI/ML projects also follow a distinct approach, even though they ultimately result in algorithms.
Perspective and experience of individuals¨: the background and experience of the persons involved in the project will also impact the approach. Technical experts with deep application knowledge approach the work differently from junior product managers or owners with a stronger business orientation.

In essence, context is paramount, and there is no one-size-fits-all rule. Nevertheless, I often encounter posts making absolute statements such as:

The Scrum Master and Product Owner must be different individuals.
Product Manager and Product Owner roles cannot be separate.
Product Owners should not impose solutions while defining stories.
Product Owners should not be part of the Scrum team.
Development tickets should be written in the form of user stories in the format "As a [persona], I [want to], [so that]".

While these statements hold merit, they excel in ideal and theoretical scenarios where

The scrum team is only occupied with 1 project
The project is rather large, but not too big either (around 100-200 mandays)
The project will result in a new custom-built application
The application is strongly end-user facing

This situation rarely exists in reality, i.e. in reality IT teams have to deal with a mix of

Small and large projects
Back-end and user-facing work
Changing priorities and budgets
Evolving teams (people joining/leaving the company)
Different profiles (full-stack engineers versus front-end/back-end engineers, junior versus senior profiles, people who already know well the application stack versus people who are discovering the application stack…)
…

To address these complexities, each Scrum team must find the best organizational approach for their specific context and continuously adapt and improve based on lessons learned.

Some key considerations include:

Keeping Scrum teams relatively small (following the "two-pizza team rule").
Granting teams a high degree of autonomy.
Making teams accountable for end-to-end outcomes, embracing both the challenges and rewards.
Establishing a set of guiding principles (5-10 golden rules) that cannot be compromised.

This combined with a good dose of pragmatism and a hands-on approach, will propel your team a lot further than any rigid theoretical framework imposed in many organizations.

Check out all my blogs on https://bankloch.blogspot.com/

Comments

Transforming the insurance sector to an Open API Ecosystem

1. Introduction "Open" has recently become a new buzzword in the financial services industry, i.e. open data, open APIs, Open Banking, Open Insurance …, but what does this new buzzword really mean? "Open" refers to the capability of companies to expose their services to the outside world, so that external partners or even competitors can use these services to bring added value to their customers. This trend is made possible by the technological evolution of open APIs (Application Programming Interfaces), which are the digital ports making this communication possible. Together companies, interconnected through open APIs, form a true API ecosystem , offering best-of-breed customer experience, by combining the digital services offered by multiple companies. In the technology sector this evolution has been ongoing for multiple years (think about the travelling sector, allowing you to book any hotel online). An excellent example of this

Are product silos in a bank inevitable?

Silo thinking is often frowned upon in the industry. It is often a synonym for bureaucratic processes and politics and in almost every article describing the threats of new innovative Fintech players on the banking industry, the strong bank product silos are put forward as one of the main blockages why incumbent banks are not able to (quickly) react to the changing customer expectations. Customers want solutions to their problems and do not want to be bothered about the internal organisation of their bank. Most banks are however organized by product domain (daily banking, investments and lending) and by customer segmentation (retail banking, private banking, SMEs and corporates). This division is reflected both at business and IT side and almost automatically leads to the creation of silos. It is however difficult to reorganize a bank without creating new silos or introducing other types of issues and inefficiencies. An organization is never ideal and needs to take a number of cons

RPA - The miracle solution for incumbent banks to bridge the automation gap with neo-banks?

Hypes and marketing buzz words are strongly present in the IT landscape. Often these are existing concepts, which have evolved technologically and are then renamed to a new term, as if it were a brand new technology or concept. If you want to understand and assess these new trends, it is important to reduce the concepts to their essence and compare them with existing technologies , e.g. Integration (middleware) software ensures that 2 separate applications or components can be integrated in an easy way. Of course, there is a huge evolution in the protocols, volumes of exchanged data, scalability, performance…, but in essence the problem remains the same. Nonetheless, there have been multiple terms for integration software such as ETL, ESB, EAI, SOA, Service Mesh… Data storage software ensures that data is stored in such a way that data is not lost and that there is some kind guaranteed consistency, maximum availability and scalability, easy retrieval and searching

IoT - Revolution or Evolution in the Financial Services Industry

1. The IoT hype We have all heard about the "Internet of Things" (IoT) as this revolutionary new technology, which will radically change our lives. But is it really such a revolution and will it really have an impact on the Financial Services Industry? To refresh our memory, the Internet of Things (IoT) refers to any object , which is able to collect data and communicate and share this information (like condition, geolocation…) over the internet . This communication will often occur between 2 objects (i.e. not involving any human), which is often referred to as Machine-to-Machine (M2M) communication. Well known examples are home thermostats, home security systems, fitness and health monitors, wearables… This all seems futuristic, but smartphones, tablets and smartwatches can also be considered as IoT devices. More importantly, beside these futuristic visions of IoT, the smartphone will most likely continue to be the center of the connected devi

Neobanks should find their niche to improve their profitability

The last 5 years dozens of so-called neo- or challenger banks (according to Exton Consulting 256 neobanks are in circulation today) have disrupted the banking landscape, by offering a fully digitized (cfr. "tech companies with a banking license"), very customer-centric, simple and fluent (e.g. possibility to become client and open an account in a few clicks) and low-cost product and service offering. While several of them are already valued at billions of euros (like Revolut, Monzo, Chime, N26, NuBank…), very few of them are expected to be profitable in the coming years and even less are already profitable today (Accenture research shows that the average UK neobank loses $11 per user yearly). These challenger banks are typically confronted with increasing costs, while the margins generated per customer remain low (e.g. due to the offering of free products and services or above market-level saving account interest rates). While it’s obvious that disrupting the financial ma

Can Augmented Reality make daily banking a more pleasant experience?

With the increased competition in the financial services landscape (between banks/insurers, but also of new entrants like FinTechs and Telcos), customers are demanding and expecting a more innovative and fluent digital user experience. Unfortunately, most banks and insurers, with their product-oriented online and mobile platforms, are not known for their pleasant and fluent user experience. The trend towards customer oriented services , like personal financial management (with functions like budget management, expense categorization, saving goals…) and robo-advise, is already a big step in the right direction, but even then, managing financials is still considered to be a boring intangible and complex task for most people. Virtual (VR) and augmented reality (AR) could bring a solution. These technologies provide a user experience which is more intuitive, personalised and pleasant , as they introduce an element of gamification to the experience. Both VR and AR

Beyond Imagination: The Rise and Evolution of Generative AI Tools

Generative AI has revolutionized the way we create and interact with digital content. Since the launch of Dall-E in July 2022 and ChatGPT in November 2022, the field has seen unprecedented growth. This technology, initially popularized by OpenAI’s ChatGPT, has now been embraced by major tech players like Microsoft and Google, as well as a plethora of innovative startups. These advancements offer solutions for generating a diverse range of outputs including text, images, video, audio, and other media from simple prompts. The consumer now has a vast array of options based on their specific output needs and use cases . From generic, large-scale, multi-modal models like OpenAI’s ChatGPT and Google’s Bard to specialized solutions tailored for specific use cases and sectors like finance and legal advice, the choices are vast and varied. For instance, in the financial sector, tools like BloombergGPT ( https://www.bloomberg.com/ ), FinGPT ( https://fin-gpt.org/ ), StockGPT ( https://www.as

From app to super-app to personal assistant

In July of this year, KBC bank (the 2nd largest bank in Belgium) surprised many people, including many of us working in the banking industry, with their announcement that they bought the rights to broadcast the highlights of soccer matches in Belgium via their mobile app (a service called "Goal alert"). The days following this announcement the news was filled with experts, some of them categorizing it as a brilliant move, others claiming that KBC should better focus on its core mission. Independent of whether it is a good or bad strategic decision (the future will tell), it is clearly part of a much larger strategy of KBC to convert their banking app into a super-app (all-in-one app) . Today you can already buy mobility tickets and cinema tickets and use other third-party services (like Monizze, eBox, PayPal…) within the KBC app. Furthermore, end of last year, KBC announced opening up their app also to non-customers allowing them to also use these third-party servi

Eco-systems - Welcome to a new cooperating world

Last week I attended the Digital Finance Summit conference in Brussels, organized by Fintech Belgium, B-Hive, Febelfin and EBF. A central theme of the summit was the cooperation between banks and Fintechs and more in general the rise of ecosystems. In the past I have written already about this topic in my blogs about "Transforming the bank to an Open API Ecosystem ( https://www.linkedin.com/pulse/transforming-bank-open-api-ecosystem-joris-lochy/ ) and "The war for direct customer contact - Banks should fight along!" ( https://www.linkedin.com/pulse/war-direct-customer-contact-banks-should-fight-along-joris-lochy/ ), but still I was surprised about the number of initiatives taken in this domain. In my last job at The Glue, I already had the pleasure to work on several interesting cases: TOCO ( https://www.toco.eu ): bringing entrepreneurs, accountants and banks closer together, by supporting entrepreneurs and accountants in their daily admin (and in the f

PFM, BFM, Financial Butler, Financial Cockpit, Account Aggregator… - Will the cumbersome administrative tasks on your financials finally be taken over by your financial institution?

1. Introduction Personal Financial Management (PFM) refers to the software that helps users manage their money (budget, save and spend money). Therefore, it is often also called Digital Money Management . In other words, PFM tools help customers make sense of their money , i.e. they help customers follow, classify, remain informed and manage their Personal Finances. Personal Finance used to be (or still is) a time-consuming effort , where people would manually input all their income and expenses in a self-developed spreadsheet, which would gradually be extended with additional calculations. Already for more than 20 years, several software vendors aim to give a solution to this , by providing applications, websites and/or apps. These tools were never massively adopted, since they still required a lot of manual interventions (manual input of income and expense transaction, manual mapping transactions to categories…) and lacked an integration in the day-to-da

Bankloch

Search This Blog