Foursys Blog | Tech Insights, Case Studies & Industry News

What changes when a bank starts working in squads?

Written by Foursys | Nov 18, 2026, 1:49:19 PM

With multidisciplinary teams and co-creation through Design Thinking, Foursys helped a major Brazilian state-owned bank evolve its business model, connecting business and technology with a user-centric focus.

Digital transformation required more than just new technological solutions. For the bank, it was necessary to change the way it developed, collaborated, and delivered value.

The traditional, waterfall-based model featured long delivery cycles and little interaction with end users during solution development. The pressure to digitize and improve the customer experience called for a transformation that would also extend to the IT organizational culture.

Foursys supported this evolution with agile squads in the areas of development, maintenance, and business analysis. The initiative combined Scrum, Design Thinking, and development and CI/CD tools to support a continuous delivery model and bring the business and technology areas closer together.

The Challenge: Long Cycles, Distance from Users, and a Traditional Work Culture

The bank needed to replace its traditional framework with an agile approach capable of promoting continuous delivery and incorporating user needs into development.

The change was not limited to adopting ceremonies or tools. It involved transforming work practices in an organization with a rigid hierarchical structure, supporting teams accustomed to the Waterfall methodology, and engaging business units in the joint development of solutions.

To move forward, it was necessary to link the evolution of the work model to the cultural transformation of IT.

Key Challenges:

  • Long Delivery Cycles: The Waterfall model hindered the continuous evolution of solutions in the face of digitization demands.
  • Limited User Interaction: Limited userparticipation during development created a disconnect between the solutions being built and their actual needs.
  • Cultural Transformation in a Hierarchical Structure: Adopting agile practices required changes in how teams worked and collaborated.
  • Teams’ Transition to Agile: Teams accustomed to traditional development needed to adopt a new working framework.
  • Business Unit Engagement: Co-creation depended on closer collaboration between business and IT.

Why Foursys?

In this scenario, Foursys’ contribution was to link the adoption of agile practices to the transformation of the work model, rather than treating the initiative merely as a change in methodology.

The initiative brought together multidisciplinary squads, user-oriented discovery, and technological support for continuous delivery. The focus was on bringing business and IT closer together and incorporating collaboration into the development of solutions.

The key differentiators of this initiative were:

  • Transformation Beyond the Framework: A combination of agile practices with the evolution of the IT organizational culture.
  • Multi-Front Approach: Squads dedicated to development, maintenance, and business analysis.
  • Co-creation Between Business and Technology: Use of Design Thinking to support discovery and the joint development of solutions.
  • User Focus: Incorporating user needs into the development approach.
  • Support for Continuous Delivery: Use of management tools and CI/CD to support the new work model.

The Solution: Agility and Co-creation Between Business and IT

Foursys supported the formation of multidisciplinary agile squads to address the bank’s various IT fronts. Scrum was adopted as the working framework, while Design Thinking supported discovery and co-creation between the business and technology areas.

The initiative combined team organization, the evolution of development practices, and cultural transformation to sustain continuous delivery.

The deliverables included:

  • Multidisciplinary Agile Squads: Structuring teams for development, maintenance, and business analysis.
  • Adoption of Scrum: Implementation of the agile framework as part of the modernization of the work model.
  • Discovery with Design Thinking: Application of the approach to understand user needs and support the definition of solutions.
  • Cross-Functional Co-creation: Joint participation of business and IT in building solutions.
  • Solution Development: Use of React and Node.js on the development front.
  • Management and CI/CD: Use of Azure DevOps to support work management and continuous integration and delivery processes.

Key Technologies and Methodologies

  • Scrum: An agile framework for organizing and managing the work of squads.
  • Design Thinking: Discovery and co-creation focused on user needs.
  • React: Development of solution interfaces.
  • Node.js: Development of back-end components.
  • Azure DevOps: Work management and support for CI/CD processes.

Success Factors and Challenges Overcome

  • Cultural Transformation at a State-Owned Bank: Evolution of work practices in an environment with a rigid hierarchical structure.
  • Adoption of Agile by Teams Accustomed to Waterfall: Transition from the traditional model to an approach focused on continuous delivery.
  • Business Unit Engagement: Bridging the gap between business and IT through co-creation.
  • User-Centric Focus During Discovery: Use of Design Thinking to incorporate user needs into solution development.
  • Multidisciplinary Approach: Squads working on development, maintenance, and business analysis.

Results

The initiative modernized the bank’s IT framework and established a way of working focused on agility, collaboration, and continuous delivery.

  • Cultural Transformation for Continuous Delivery: Evolution of the IT teams’ way of working.
  • User-Centric Approach with Co-creation: Application of Design Thinking to align solutions with user needs.
  • Agile Squads Operating Across All Areas: Adoption of the model in development, maintenance, and business analysis.
  • Modernized Work Framework: Transition from the traditional model to agile practices, supported by management tools and CI/CD.

This case study underscores that agile transformation goes beyond the adoption of a framework: it involves culture, collaboration, and a new way of connecting technology to the needs of the business and users.