Salvatore was working in a large-scale transformation, when he and his colleagues started noticing that it was hard to get clarity across many team backlogs, and the planning sessions at scale were not delivering the value they expected. As the team of Scrum Masters started investigating the situation, they discovered that decision making was only happening outside the teams, in management groups or higher. As the Scrum Masters started to talk to managers, Salvatore realized that Scrum Masters were not allowed to influence the system around the teams. This taught Salvatore an important lesson about being able to, and focusing on influencing the system around the teams, not only the teams themselves or the PO. These are the 3 concerns Scrum Masters must pay attention to: the Scrum team, the PO and the system around them!
About Salvatore Rinaldo
Salvatore is an Agile Coach and Scrum Master based in London. His background is in telecommunications and software engineering. For the past 7 years, Salvatore has been helping organizations leverage Lean, agile, Flow principles and system thinking to achieve better business agility.
Dana Pylayeva, will host the coaching track at the summit, where we explore some of the hard lessons we need to be aware of when adopting coaching in our practice
Ayodeji Ishola, hosts a track on the state of Agile in the African continent, and will be showcasing talks that address the cultural specific aspects of Agile in Africa
Mariana Trigo, will have 6 sessions on career advice for Scrum Masters and hiring advice for those hiring Scrum Masters. She’ll have a special focus on how you can get into the Scrum Master role even if you don’t have a tech background.
Yves Hanoulle, the co-author of the Tips from The trenches audiobook, hosts a track on Hybrid work, very topical now that we have our teams remote most of the time
Martin von Weissenberg, will share patterns of scaled agile. Not the frameworks we always hear about, but rather practical, down-to-earth advice for specific needs when we scale agile
Accepting and learning to deal with Social Complexity in Agile adoption
Gerry came across Agile while working as a project manager in a construction company. Motivated by his drive to provide a great service to his customers, he started to study how to make his own business more adaptable and Agile.
Working with new technologies, he started to improve certain aspects of his business. However, he quickly realized that the size of the projects and demands of the customers were making what once was an “easy” to manage service, into a complicated service with many moving parts.
The use of computers helped manage that complexity, but also brought even more complexity. This was when Gerry discovered Agile and what it could bring to a non-IT business.
The Nexus Framework has been a topic on the podcast before. In this episode, we explore critical lessons for Scrum Masters that need to work with multiple teams and large organizations with the help of the Nexus Framework.
Organizing A Multi-Team Retrospective: A Key Scaling Tool
One of the aspects that gets shortchanged in the “scaling” frameworks and approaches is the aspect of learning as a whole organization. It is not enough that each individual team learns how to improve. We also need to help the wider organization learn, and for that, we need to be able to organize multi-team retrospectives.
Simon introduces the idea of the “sandwich retrospective”, and highlights that we must ensure that there is a product level and an organizational level learning loop.
Facilitating Multi-Team Planning Efforts: The Key Steps
Knowing how to help a single team is not enough when it comes to helping a set of teams succeed with planning the next increment. The “Nexus” (a group of teams working on a product) planning requires different tools to help eliminate and account for possible dependencies. One of the tips Simon shares is that of ensuring that refinement is done together with multiple teams and before a big room planning event, where multiple teams come together to plan their product increment.
In this segment, we talk about what works when helping multiple teams plan and sprint together, and how to facilitate the refinement when multiple teams are involved.
Focusing on Product Development, not Organizational Development
Every scaling framework has a different focus. In this episode, we talk about what is the reason behind Nexus’ approach to scaling Agile and differentiate Nexus from other frameworks that may focus on organizational changes, while Nexus focuses on the Product Development aspects, not on the organization.
About Simon Flossmann
Simon helps teams effectively use Scrum and an agile mindset to deliver products and services that matter! As a Scrum Master and Professional Scrum Trainer, licensed by Scrum.org, he supports teams and organizations of varying sizes in a wide range of business domains, like automotive, home appliance, energy sector, federal government agency, and insurance.
The financial processes of companies can defeat their own efforts to become more agile. It’s simply impossible for an organization to be adaptable if their project processes require all projects to be specified up-front and funded months ahead of their starting date.
Tackling the financial process changes in our organizations is one of the make-or-break aspects of helping organizations become Agile and adaptable.
In this episode, we talk about Lean and Agile Financial Planning (PDF article download), an approach that tries to adopt Agile and Lean thinking in the funding and financial processes of an organization.
The reason why Lean and Agile Financial planning is a core aspect of Agile transformation in enterprises