BONUS: The Nexus Framework For Scaling Up Scrum with Simon Flossmann

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. 

To know more about Nexus and how it can help your organization, visit Simon’s Nexus course. 

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. 

In this segment, we refer to the Nexus Framework Guide and the concept of Double-Loop Learning.

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.

You can link with Simon Flossmann on LinkedIn and connect with Simon Flossmann on Twitter.

You can follow Simon Flossmann’s writings on this home page.

 

 

Steve Tendon on what the scaling frameworks are missing and how to get it to your organization

There’s some serious gaps in the current Agile scaling frameworks. We know that because we are the start of the scaling journey. But what are the scaling frameworks missing today that we should be looking out for? Steve shares his views on what is missing and how looking at the system performance can help us find the gap, as well as what solutions are already out there to help us close the gap. In this episode we discuss the TameFlow community as well as the concept of Throughput Accounting, from the Theory of Constraints.

About Steve Tendon

Steve Tendon popularised the Theory of constraints in some of the agile community and he is also the Creator of the TameFlow systems thinking approach which nurtures breakthrough performance innovation. This system is described in the book with the same name: Tame the Flow. 

You can link with Steve Tendon on LinkedIn and connect with Steve Tendon on Twitter.

Antti Tevanlinna discusses how to scale agile software development

How to scale agile software development? is a question we hear often these days. Antti describes his experiences, how long it took him and his colleagues to get it right, and what they learned in the process. Scaling agile software development isn’t easy, and it is important we learn about what has failed in the past.

About Antti Tevanlinna

scrum_master_toolbox_podcast_Andy_Deighton Antti is an agile practitioner, who got started with agile in my own very first Agile project way back in 2004. He’s been through all kinds of roles, from team member, to management, to customer-facing roles.
You can connect with Antti Tevanlinna on twitter, and check Antti Tevanlinna’s blog.

Stephen Thomas shares his recipe to help the organization adopt scrum and engage with the scrum team

How do we help organizations to recognize the value that scrum teams can bring, and the obstacles they face in the process? Stephen Thomas shares his recipe and describes a few ideas of how the retrospectives can be an effective practice to help organizations evolve and get better.
Stephen’s recipe for organization improvement:

  1. Help the teams understand their progress with a physical (as opposed to digital) and visual burndown (colorful if possible).
  2. Write the principles on the wall and make sure people see them regularly. Point to them when needed.
  3. Have lots of wall space for teams to use and create their shared view of their work.
  4. Help start and facilitate organization-level retrospectives, because improving one team is not enough for lasting change.
  5. Make the team independent

Before implementing all of this, make sure that the organization has the necessary knowledge to work in an agile manner, helping organize training if needed, and working with stakeholders regularly.

About Stephen Thomas

Stephen Thomas Scrum Master toolbox podcast Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.