Agile transformations typically begin with pilot projects that involve testing out new methods of operation and exploring different cultural aspects. Yahoo, for instance, initiated this process in 2004 with a single team and gradually expanded it to encompass hundreds of teams. Similarly, major fintech companies worldwide have adopted Scrum methodology and other innovative approaches within large IT centers, leading to a demand for scaled operational methods such as SAFe, LeSS, Nexus, and others.
Several companies such as Spotify, ING Bank, and numerous others have adopted the scaled frameworks based on the Spotify model or Agile WOW.
Having only one team practicing Scrum (or another methodology) is now seen as a luxury, while managing 10 teams under the same product umbrella poses a significant challenge.
If you belong to a network of teams that has expanded, you may face the following challenges:
Too many MEETINGS (TMM syndrome)
Transitioning from personal involvement to a more IMPERSONAL setting, feeling lost in a large group and experiencing a lack of contribution
Reduced space for exploration and discovery, with an emphasis on PLANNING
Dealing with complex DEPENDENCIES
Feeling like a small part of a larger entity (Product), having less understanding of the product being developed, leading to increased SEGREGATION
Limited COLLABORATION AND COMMUNICATION with other teams working on the same product, essentially becoming strangers within the same project
Staying at the project level instead of progressing towards the PRODUCT stage
You might be wondering, "What can we do to address this? How can we enhance our efficiency and create products that customers love within large-scale frameworks?"
The most important thing is to understand that ONE model does not fit ALL. The people we interact with, the environment, the industry, and our company culture all play a significant role in shaping our work and products. Even Spotify itself does not adhere strictly to the Spotify model, as they continuously evolve.
Examine and adjust your approach to work, your mindset, and the factors contributing to your success. This entails customizing the scaled frameworks to suit your preferred way of working. While the frameworks serve as a valuable foundation, it is essential to develop your own scaled framework that aligns with your needs. This may involve eliminating certain stages or meetings while incorporating new ones.
Come along with me in my upcoming articles on "Is Agile SAFe?" as I explore concepts and potential resolutions for you and your teams.
Have a SAFe day!
Mihai, an Agile cricket
Comentarios