Resources

This article is part 2 of a series that highlights several case studies of companies using the Nexus Framework for scaling Scrum.

This article highlights several case studies of companies using the Nexus Framework for scaling Scrum.

In this webinar, Nic Easton, Nexus Scrum Master, Net Health, and Patricia Kong, Product Owner of Enterprise Solutions, Scrum.org walk through how they worked together to help Net Health address these challenges using Evidence-Based Management (EBM), a framework by Scrum.org that helps organizations measure, manage and increase the value they derive from their product delivery by focusing on improving outcomes, reducing risks, and optimizing investments. 

In this episode of the Scrum Master Toolbox Podcast, Patricia Kong and Kurt Bittner explore Nexus, a scaling framework developed by Scrum.org to tackle just that: the use of Scrum in larger organizations and multi-team product development efforts.

In this Scrum Tapas video, Professional Scrum Trainer Jeff Bubolz provides some tips from his experience working to deliver a product with multiple Scrum Teams. Jeff discusses Product Ownership, Backlogs, Daily Scrums and more. (5:41 Minutes)

In this Scrum Tapas video, Professional Scrum Trainer Krystian Kaczor discusses the purpose that the Nexus Integration Team plays when scaling Scrum beyond 2 Scrum Teams to deliver an integrated product. (4:43 Minutes)

This article discusses the growth of agility for customer-facing products with 3+ teams, probably tens of teams with Nexus and/or LeSS.

You’re likely to have been asked the question: “we need to go faster, how many more people do we need?” Most people naturally understand that just adding a random number of people isn’t likely to make us any faster in the short run.

In 2015, Cathay Pacific had a major project on their hands which concerned the development of a new Internet Booking Engine (IBE). They needed a framework that would help them deliver within a specific time line.

One of the hottest questions these days, whether online or in the boardroom, is “How does the organization become more ‘agile’?” As the discussion evolves, it leads to, “How do we scale agility from one team to multiple, or should we?

Nexus, created by Scrum co-creator Ken Schwaber and his Scrum.org team, extends Scrum to guide multiple Scrum teams on how they need to work together to deliver working software in every Sprint. Eric Naiburg explores the Nexus framework in this article.

It has been said that the definition of insanity is doing the same thing and expecting different results, and yet we engage in an unconscious fiction of predictability every day. We work in an uncertain world, and our main goal in pursuing agility is to confront the unknown, and in doing so, to master it.

In this session, we explore how to integrate Peter Senge's 5 Disciplines of Learning Organizations with the Nexus Framework to help organizations to scale their business agility with Scrum. Along the way, we find out what Michelangelo had to say many centuries ago that can guide and inspire them in their journey.

In this magazine, Scrum Studio is highlighted as a key part of KLM Royal Dutch Airlines digital transformation.

Impact Mapping is a powerful technique that helps teams understand how to link the work that they do with results that their organizations would like them to achieve. We’ve been using this technique for a while in our Scaled Professional Scrum and Professional Scrum Product Owner courses.

I need to get something off my chest. It's a personal thing, so don't mind me. But maybe it will get you thinking also. It's been on my mind for quite some time. Troublesome sometimes.... Here it goes.

In this video Richard Hundhausen, Professional Scrum Trainer talks about software delivery as a team, living the Scrum values, and using Microsoft Visual Studio Team Services (VSTS) to plan and execute the work.

Based on the feedback that I have received from my blog about the most popular blog articles, I have decided to do the same for the Scrum.org video series.  Over the past few years, we have generated more than 160 videos to help people learn more about Scrum.

In this session, Valerie Pearce, Senior Software Architect and Nic Easton, Nexus Scrum Master and Software Engineer III from Net Health, and Patricia Kong, Scrum.org Product Owner of Enterprise Solutions, walk through how Net Health scaled Scrum by implementing the Nexus framework in their product development organization.

A market leading international manufacturer of HVAC equipment in Germany was challenged with redesigning their online presence. Their more than 80 websites needed to be consolidated, redesigned, and implemented on a new content management system.

Agile For Humans' Ryan Ripley interviews Patricia Kong and Kurt Bittner from Scrum.org on the Nexus framework for scaling Scrum.

When your product gets really big and you need to work with teams at scale, what options do Product Owners have? In this episode, Scrum.org CEO, Dave West joins the show to discuss the Nexus framework and what PO’s need to know in order to work in this type of scaled environment. We cover some of the basics that are detailed in the new Nexus book and look at other keys to keeping multiple teams coordinated and delivering value together.

This short video provides an overview of the Scaled Professional Scrum with Nexus (SPS). In this video, course stewards and Scrum.org Professional Scrum Trainers (PSTs) Ravi Verma and Fredrik Wendt give you insight into the structure of the class and what you will learn over the 2 days. (

Kurt Bittner, VP of Enterprise Solutions presented "5 Things You Need to Know About Digital Transformation" at Agile 2018.

In this webinar, we provide an overview of Nexus, describe how it is being used around the world to help organizations scale their Agile efforts with Scrum. Our presenters then demonstrate how these real-world scenarios using Nexus can be applied within the VersionOne Lifecycle solution. 

InfoQ interviewed Patricia Kong, Product Owner at Scrum.org, about the changes to the Nexus Guide and the benefits that organizations have got from using Nexus.

Most organizations want to improve their agility to be more responsive to customer and market changes. They want to build on the success they have had with scrum at the team level and apply it across the whole organization. And while they might like to be more like Apple, Netflix or Airbnb, their challenge is that, unlike Silicon Valley startups and tech giants, they are not starting from a clean slate. Instead, they are trying to change from a traditional, process-centric, hierarchical organization into something else.

Scaling is a popular strategy these days: scaling innovation, scaling agile, scaling whole organizations. But scaling can easily undermine agile principles like focus and minimal viable product, and the abilities to deliver, learn quickly, and pivot decisively when required.

Net Health first adopted Scrum in 2014 to aid in the completion of two large software development projects and remove the burden of an exhaustive initial requirements phase, thanks to the iterative nature of Scrum.

These slides accompany the webinar What is Nexus? An Introduction to the Framework for Scaling Scrum

In this webinar, Patricia Kong, Scrum.org Product Owner of Enterprise Solutions and co-creator of Nexus provides an overview to the Nexus Framework, its principles and the thinking behind it. She will discuss how Nexus, like Scrum, promotes bottom-up intelligence to discover and emerge what works best for the teams and organization. She uses case studies as examples showing how Nexus can be used, and visits the recent updates to the Nexus Guide.

A friend sent me an e-mail, asking me to summarize Nexus and the Scaled Professional Scrum class. Here's the gist of what I sent in return.

Expanding a successful department-level agile initiative across an enterprise requires an agile project approach of its own. Agile delivery has hit a tipping point, with the majority of IT organizations finding some level of agile success. For these organizations, the next logical step is to scale this success into an "enterprise adoption", taking the value they are getting from a single team and replicating it.

In this episode Jochen Krebs speaks with Patricia Kong and Kurt Bittner of Scrum.org, about the changes made to the Nexus Guide release in January 2018 and their thoughts on Scaling Scrum.

In this DevOps.com article, they look at the announcement of the new release of the Nexus Guide, and Scaling Scrum with Nexus book.

In this SD Times article, they look at how Scrum.org is announcing new updates to the Nexus Guide, the body of knowledge for using its Nexus framework to scale Scrum. The new updates focusing on adding clarification as well as asserting the importance of transparency at scale.

In August 2015, Ken Schwaber and Scrum.org introduced the Nexus framework to the public via the Nexus Guide, the definitive guide to scaling Scrum. Today, on January 17, 2018, we release the first update to the Nexus Guide.

“I designed a defined framework for using many Scrum Teams on a single product or problem. The result is Nexus, an exoskeleton that rests on top of many Scrum Teams. Nexus provides information and management information for guiding their working together.” - Ken Schwaber

According to Forrester Research, 90% of Agile teams use Scrum.[1] One reason for this popularity is that Scrum is a simple framework that promotes transparenc

This Guide Describes Nexus, the Framework for Scaling Scrum

An online version of The Definitive Guide to Nexus

Scrum.org, the mission-based organization dedicated to improving the profession of software delivery through training, certification assessments and community, today announced that it has made updates to the Nexus Guide, the body of knowledge for using its Nexus framework to scale Scrum. The Nexus Guide was initially released in August 2015.

Scrum Studio creates an environment in which empiricism can thrive. It may exist as a physically separate organization, or it may simply be a protected part of an existing organization, especially when it is just getting started.   Read this paper to learn more.

Capital One was recently faced with the challenge of building a brand new product in 3 months. Not only did they meet this goal, but they were able to deliver their first release 3 weeks early. How did they do it? How were they able to build an entirely new product in such a short time frame? What hurdles did they face? How were they able to overcome them? 

When multiple Scrum Teams are working on one product, shared DoD becomes necessary. DoD helps to ensure that each increment is transparent by the end of every Sprint and creates a shared understanding of what “Done” means.

In this talk from Scrum Day Germany, Dave West CEO and Product Owner of Scrum.org describes how Scrum is being used at scale and how organizations are managing the friction between the needs of Agile and the traditional needs of the organization. 41:47 Minutes

El Nexus Integration Team es un nuevo rol dentro de Nexus, el framework de referencia para escalar Scrum.

Some companies develop 1 product with 10s to 100s of people using Scrum. And they do that without adding any roles, events or processes to Scrum. They can do this because they use an organisational design that optimises for the right goals.

In their first attempt at attaining agility, Intralinks took a well-intentioned “mechanical” implementation of Scrum - done in good faith and with lots of hard work - but failed to deliver against their goal of greater agility. So, they took on a “Scrum Reboot” and succeeded by augmenting the mechanics of Scrum with the fundamental idea of inspection and adaptation and the Scrum Values of Courage, Focus, Openness, Respect and Commitment.