Nothing surpasses learning from the experience of others if you're looking for motivation, useful guidance, or to broaden your common sense. To relate to our fellow humans and share both our triumphs and failures is the most human thing we can do.

It's the same in business; we look at other people's exposure to and experience in the field, draw lessons from them, and strive to be even better. We've chosen to discuss how some leading companies are scaling agility and creating Agile organizations today as a result.

What are the main characteristics of Agile companies?  

The organizations that we’ll talk about have one common key trait – their drive and willingness to change. The goals of the change can vary: adapt to the market, drive innovation, gain a competitive edge, the important part is the continuous desire to improve.  

Let’s explore the examples.  

1. How Boa Vista aligned team operations with strategic goals on the path to business agility?  

The Brazilian provider of financial solutions Boa Vista initiated a digital transformation project back in 2019. The project’s goal was to accelerate delivery and foster the ability to swiftly adapt to changing customer requirements.  

The company’s pain points at the time were related to:  

  • Long delivery cycles  
  • Lack of clear visualization  
  • Identification of improvement opportunities  

To support their mission, the company chose to apply the Kanban method. The method helped them break down work into value-stream oriented departments and product-oriented teams. As a result, the new team structure brought greater visibility across teams and departments, reducing waiting times and blockages caused by moving a project through different departments.  

To continue on their path to organizational agility, Boa Vista turned to the Kanban Maturity Model to scale their Kanban commitment efforts across the company. Introducing a five-layered Kanban board where team projects were linked to strategic goals, enabled greater transparency and alignment between operations and company objectives. In addition, introducing the practice to work on small batches made teams more flexible to external factors.  

On their mission to achieve digital transformation goals, Boa Vista also employed Kanban metrics. The results showed improvement of teams’ workflow performance and justified that the work processes were becoming more stable and predictable.  

2. Simplicity and effectiveness or how Vanguard became a truly Agile company?

The renowned investment management company started its Agile transformation back in 2007 “officially” employing the Scrum framework among various teams in the organization. Internal research on the framework’s adoption showed that by 2014, about 40% of the employees who originally implemented the method, switched or were planning to switch to Kanban.  

The popularity of the Kanban method among Vanguard teams was attributed to:  

  • The fast learning processes  
  • The fast feedback flow mechanisms  
  • Comprehensive visualization of the end-to-end flow  

The challenges that various teams were experiencing at the time were related to:  

  • Uneven workflows  
  • Poor capacity distribution  
  • Not understanding who the customer is  

The end-to-end Kanban board with mapped work states and the ability to integrate internal teams with external vendors (upstream filtering) helped Vanguard teams to streamline their multiple flow boards and levels. Another attempt to manage their workflows better was introducing service classes and work sizing which enabled a faster flow of work downstream. Furthermore, applying explicit work policies and WIP limits improved the understanding of the overall capacity distribution as well as reduced the workflow lead time.  

Employing workflow visualization and classifying work types enabled a deeper understanding of customers and vendors, stronger work policies, and reduced costs. The teams at Vanguard managed to establish consistency in their work processes, as well as policies utilization, and decision-making models. A turning point in the Agile transformation journey at Vanguard was consolidating multiple flow boards into one grand Kanban board which enabled the simplicity and effectiveness of a truly Agile company.  

3. From team-focused to flow-oriented program management – the BBVA journey to scaled agility.

One of the largest financial companies in the world – BBVA (The Banco Bilbao Vizcaya Argentaria) started its Аgile journey in 2014 and continues to this day. The goal of the endeavor was to establish a steady flow of value, enable quick adaptation to the market, do meaningful work prioritization, and promote continuous learning.  

A year after the start of the Аgile initiative, the largest part of the business – Business as Usual (BAU) services, was suffering due to the prioritization of the Agile transformation programs. As a result, a number of other projects were affected.  

BAU, additional projects, and cross-team dependencies had to be managed more effectively. The Kanban method provided the needed capabilities to enable fast feedback about work items’ status, support evidence-based decision-making, and identify improvement opportunities.  

To evolve their organizational agility, BBVA introduced Portfolio Kanban to their program management. The model enabled better work synchronization and prioritization among multiple projects, bringing a greater understanding of the work process including the cross-team and cross-project dependencies. Using work-related metrics improved their work planning and delivery commitments.  

Some of the challenging areas where Kanban provided effective solutions were related to:  

  • Lack of proper coordination of services  
  • Poor work prioritization  
  • Lack of synchronization across teams  

In the span of one year, the two programs selected for agile transformation of the BBVA’s finance domain managed to establish a synchronized work hub, and improve the understanding of the types of delivered services. The programs also gained a deeper quantitative perspective about the demand and capabilities which enabled effective planning. Another major success was instilling a sense of belonging through the practice of Kanban cadences and empowering a flow thinking.  

4. Leadership buy-in – the key to achieving organizational agility at Bosch.  

With the goal to stay in the present and satisfy the demands of today’s market, the automotive giant Bosch saw the critical need to become more innovative and agile. In 2018, the company started its transformation to business agility employing Scrum teams.  

A major milestone in the transformation process was the initial approach to create a “dual organization”. In other words, business as usual (BAU) would run as normal alongside specific teams that would adopt Agile. The failure of the approach pushed management to start from scratch and this time the goal was to spread agility across the company starting from leadership.  

Some of the practices that turned out process impediments were related to:  

  • Plain status reporting  
  • Annual planning and fixed priorities  
  • Isolating impediments to specific sectors  

The leadership role was key to the success of the agility adoption at Bosch. Engaging in conversations facilitated fast feedback and collaboration. Furthermore, leadership guided the organizational change by prioritizing the backlog of the entire enterprise. Transitioning to continuous planning, on the other hand, enabled faster adaptation to emerging changes and made the company more flexible. Organizational issues would no longer be seen as problems dedicated to specific groups but as impediments affecting the company’s operations as a whole.  

5. Higher operational transparency – the major step towards business agility transformation at SSOE.  

With a bold mission – to save time, trouble, and money to their clients, the global project delivery player for architecture, and construction management, SSOE Group turned to Lean/Agile practices. The company was looking to implement the practices and drive performance through enhanced collaboration and optimized workflows.  

The key challenges before achieving organizational agility at SSOE at the time were related to:  

  • Lack of operational transparency  
  • Poor collaboration  
  • Lack of alignment between execution and planning  

Kanban was identified as the leading method to respond to these challenges. The Kanban practice to visualize the workflow made it possible to streamline work processes quickly. In the span of only three months, team members were better aligned on how work is done, there was greater collaboration and improved scheduling of work between teams and work stages. Furthermore, the use of digital Kanban boards required team coordination on defining the major steps in a delivery process, which naturally supported team collaboration. The daily, weekly, or monthly practice to discuss ongoing work and bottlenecks through the use of Kanban cadences, allowed better team discussions and knowledge-sharing opportunities.  

Critical to the success of the business agility transformation at SSOE was measuring the results of the efforts put in. The Kanban Maturity Model for scaling Kanban across an organization provided reliable data to SSOE managers allowing them to measure the progress of the transformation, and to identify room for improvement. For instance, SSOE introduced work types for various activities and multi-level work structures. These layered structures made it possible for project managers to have greater visibility over the status of projects and project-related work across teams, in real-time and in a single place.

6. The Big Bang Agile transformation across 3500 employees at PayPal.

The global leader in the payment domain initiated their transitioning to business agility back in 2013 employing Scrum teams across their 40 offices worldwide. The organization had multiple product organizations with no defined product hierarchy and no common leadership. As a result, despite the hard work, little value was delivered to PayPal’s customers.  

The issues with the operating model were related to:  

  • Lack of project-focus  
  • Poor dependencies management  
  • Multiple orphaned projects  

To respond to these challenges, PayPal imposed a big bang Agile transformation with four major pillars. The first step was to bring the teams closer to the customer and understand their wants and problems. Next, clear product ownership was induced which enabled structuring the agility scaling efforts as well as organizing the company product portfolio. The third step was imposing to begin to work on Scrum teams. Тhe final phase was introducing KPIs to measure the entire transformation project.  

Critical for the success of the operation were the provided Аgile trainings for product owners, scrum masters, and Аgile coaches. Another factor was the achieved transparency through mapping all ongoing projects inside a unified workspace where everyone was able to see what everyone was working on. This resulted in optimized dependencies management. A cornerstone of the success of the project was introducing planning and execution at a portfolio level.  

What does it mean to scale business agility across the company?  

As we saw from the Agile organization examples above, truly Аgile companies tend to focus their efforts around the same goals. To name a few, company culture shift, high employee engagement and morale, embracing of feedback, improving customer service, increasing delivery rate, improving quality, etc. But these are not to be mistaken for the “final goal” of Agile organizations – the key is in the continuation and nurturing of the practices that helped you unleash true business agility.

Ready to ace your exams? Access our top-notch practice exams for optimal results!

https://prepzo.com/categories/business/agile

Posted 
Oct 23, 2022
 in 
Business
 category

More from 

Business

 category

View All

Join Our Newsletter and Get the Latest
Posts to Your Inbox

No spam ever. Read our Privacy Policy
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.