Skip to main content

Nexus Case Study

Last post 11:09 pm August 20, 2017 by Lipe Andrade
7 replies
05:06 pm September 8, 2016

Do we have any practical case studies on Nexus? If yes, what were the shortcomings found in the model?


Anonymous
05:32 pm September 8, 2016

Hello T,

Thank you for your post. We have not yet published any Nexus case at this time. However, in case you're interested, we have published some Nexus white papers here: https://www.scrum.org/Community/Community-Publications

Thank you and enjoy your day, T!


04:04 am September 9, 2016

OK. Let me ask one thing. Is it got adopted anywhere and if yes, did you had access to the end results and if yes, could you share the learning, if it can be shared?


01:42 pm September 9, 2016

Hi T,

As I am sure you can understand, having companies go public with their results and names of the company is not an easy one to get past their corporate infrastructures, but we do have several case studies in the works and going through that process today. Those include major airlines, retailers, banks and others. Also, remember, that Nexus at its heart is Scrum.

Some of the results that we have documented in these drafts include:

By using Nexus, one organization has been able to better meet the needs of their customers by releasing features more frequently. For instance, after conducting a focus group, the Development Teams were able to take the user feedback from the research session, incorporate it into the app and release new capabilities in just two weeks, directly addressing and delivering on stakeholder input and therefore delivering value back to customers and the overall business.
Before applying Nexus, the Scrum Teams were producing an integrated increment every eight weeks. Now, with Nexus they’re producing one every two to four weeks, with a goal of more consistently delivering every two weeks.

In another, A formal Nexus integration team, made of one delegate from each of the nine Scrum teams, come together twice a week to discuss any integration issues that have been flagged. By removing integration and operations issues from within the individual Scrum teams which make up the Nexus, production pushes forward, undeterred, preventing development from being stalled. At the onset of “Done” – the Scrum term for the completion of a Sprint, which is pre-determined in Sprint Planning – Scrum teams deliver their results to the Nexus, who then delivers it to production.
This organization formally introduced Nexus in 2015. Nearly four months later, the entirety of the organization’s front and back end are now operating with Scrum.

I hope this helps.


02:22 pm September 9, 2016

That is good know, Eric.
However the crucial data I would be looking for would be how many scrumbles were there in each case before reaching that state?


08:50 pm August 20, 2017

Hi!

Do you know if there's a specific source where I can find Nexus case studies?

I was taking a look at the Community publications, but couldn't find much.

Thank you!!


09:32 pm August 20, 2017

Yes, there are 3 case studies in the Resources section on there: https://www.scrum.org/resources/scaling-scrum


11:09 pm August 20, 2017

Awesome, thanks Clem!


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.