Nexus – A relationship or connection between people or things.
Scrum is a simple framework for delivering products using an empirical approach in which teams deliver value in small increments, inspect the results, and adapt their approach as needed based on feedback.
Nexus builds upon Scrum’s foundation, and its parts will be familiar to those who have used Scrum. It minimally extends the Scrum framework only where absolutely necessary to enable multiple teams to work from a single Product Backlog to build an Integrated Increment that meets a goal.
As with the Scrum framework, the Nexus Framework is comprised of a number of Accountabilities, Events and Artifacts & Commitments:
Accountabilities
Developers
Product Owner
Scrum Master
Nexus Integration Team*
Events
The Sprint
Cross-Team Refinement*
Nexus Sprint Planning*
Sprint Planning
Nexus Daily Scrum*
Daily Scrum
Nexus Sprint Review*
Nexus Sprint Retrospective*
Sprint Retrospective
Artifacts & Commitments
Product Backlog & Product Goal
Nexus Sprint Backlog* & Nexus Sprint Goal*
Sprint Backlog
Integrated Increment & Definition of Done
*Nexus specific
“Nexus is the exoskeleton of scaled Scrum” – Ken Schwaber
Over the next series of posts I will go into detail about these Nexus specific elements to help you understand how you can use Nexus to scale your Professional Scrum.
<– Previous post: The Secret To Scaled Professional Scrum
Index – Scaled Professional Scrum And Nexus – The Definitive Guide
Do You Want To Learn Scrum & Agile?
Learn Scrum & Agile at lost cost and online. Our 5-star rated Ultimate Scrum & Agile eLearning Courses can take you from beginner to advanced at your own pace.
Prepare and practice for the assessments from the major Scrum & Agile providers. Our 5-star rated Ultimate Scrum & Agile Practice Assessments will help you gain certification.
About TheScrumMaster.co.uk
Hello Simon – i hope you are good. Can you please help on below , i marked it as ‘d’ as this is the goal considering question is about the goal but it was wrong?
The primary goal of Scaled Professional Scrum is best described as:
Select 1 answer.
a)To keep the scaling as uniform as possible. As your costs rise your productivity should rise at as close to the same rate as possible.
b) A framework to allow you to achieve linear scaling from a productivity/cost perspective.
c)A methodology to help you scale your software development.
d)To allow you to develop software at scale.
Hi Rinku,
D is a good answer, but not the best answer. Is Scrum & Nexus only about software development?
Regards
Simon
Is it B in that case as the best answer? “A framework to allow you to achieve linear scaling from a productivity/cost perspective.”
Can any framework/method legitimately claim to allow linear productivity/cost scaling?
The answer is no but i have read it in aline in nexus framework book so i assume it is a wrong choice of words in chapter 6
“With Nexus, and the appropriate practices, the goal is to try to keep progress as linear as possible so that the Nexus is scalable”
Hi, product owner and scrum master would remain as unique role across all the teams or instead would be an scrum master for each team, including another one for the nexus integration team?
I understand that product owner should be unique maybe with some representatives helping across the team? Maybe a product owner representable for each team?
Hi Simon,
How & why Nexus is the exoskeleton of scaled Scrum?
Hi Pradip,
Just as Scrum is a framework to help you develop innovative and valuable Products, Nexus is a framework to help you do this at scale. As a framework it doesn’t have all the answers you will need to be successful. Scaled Professional Scrum introduces 40+ practices to build on and extend Nexus to increase your chance of success. Therefore Nexus is just the core to get you started, which Ken describes as the exoskeleton.
I hope that helps.
Regards
Simon
But the Nexus guide lists them as artifacts . Snapshot from the guide below. Isn’t that in congruent ?
Nexus Artifacts
Product Backlog
Nexus Sprint Backlog
Integrated Increment
Hi Selvi,
I’m not sure what you mean here?
Regards
Simon
Hi Simon I think Integrated Increment is also Nexus specific. If it is same as Increment what is being used in Scrum framework then why a different name? Correct me if my understanding is wrong.
Hi Pradip,
The Integrated Increment is not Nexus specific. Integration is a prerequisite for an Increment even if not using Nexus. Integration is just emphasised in Nexus because it will be essential at scale.
Regards
Simon