Skip to main content

Thoughts on Nexus

Last post 05:05 am July 2, 2018 by Simon Mayer
5 replies
12:09 am July 1, 2018


we are shortly going to be embarking on number of sprints to deploy a product (the sprints will be concurrent but have different team members). My understanding is that Nexus is the recommended methodology to run multiple sprints. I ordered the book from Amazon but has anyone any thoughts, esp those who have practiced this?

01:25 am July 1, 2018

How familiar are you and the organization with Agile and Scrum? You can buy a book and try to make it work but without real word experience it won’t be easy.

Nexus is recommended when you have 3-9 teams not just  concurrent sprints.

You are going to fall flat on your face if you have no applied knowledge or experience. As the guide says easy to learn hard to master. Nexus adds a layer of difficulty on top of tradtional scrum.

Why do you need to scale? What’s the driver? How many teams do you have? Are you already doing something like Lean Software Development.

As dumb as this is going to sound I decided to do Nexus Scrum because it is one of the “easier” scaled scrums to implement but not without experience.

Good luck.

03:46 am July 1, 2018

we are shortly going to be embarking on number of sprints to deploy a product (the sprints will be concurrent but have different team members)

How important do you think it will be to integrate work on a regular basis in order to assure transparency? What’s the best way for this to be co-ordinated and managed?

07:11 pm July 1, 2018

Very first question before going to be scale is, do you think you can achive the same work with teams you already have ? In addition this, dependencies are getting as an obstacle? Finally, as @Ian mentioned you need to create an integrated work each sprint?

I would recomend you thinking twice these items then decide to scale.

08:15 pm July 1, 2018

I would recomend you thinking twice these items then decide to scale.

Indeed. Scaling ought to be viewed as something of a last resort, since it introduces co-ordination dependencies such as complexities around integration. Improving the ways-of-working of a single team ought to be the first recourse. There is also a danger of scaling inefficient practices when it is done precociously.

05:05 am July 2, 2018

How many Scrum Teams will be working on the same product?

Although the Scrum Guide doesn't specifically mention multiple teams, they can still work on the same product without introducing a scaling framework.

For instance, two co-located teams working on the same product should be able to collaborate effectively without any scaling framework.

If there isn't the need to introduce a full scaling framework, it is still sensible to consider how the teams will co-ordinate.

You might choose to run sprints on the same cadence, and consider adjusting some of the events. e.g. the first part of the Sprint Planning held with all teams, holding a shared Sprint Review, and perhaps holding a combined retrospective before or after each team has its own Sprint Retrospective.

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

Please note that the first and last name from your 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. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, 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 may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.