The SPS Certification validates your ability to scale Scrum with Nexus. At 40 questions in 60 minutes (85% pass mark), it rewards sharp recall, nuanced scenario thinking, and calm execution. SPS certification requires that a student demonstrate their knowledge and understanding of Scrum through a rigorous assessment. There are no prerequisites to attempting this certification, but it is highly recommended to attend Professional Scrum Foundation, Professional Scrum Master, or Professional Scrum Product Owner training in order to grasp concepts faster. The tactics below combine proven learning science with exam-day psychology so you can walk in confident and walk out certified.

SPS Practice Exam – Click Here

Also, practice Scrum Master and Product Owner practice exams; these will help you brush up on your Scrum knowledge and assist in answering Nexus-related questions.

Pros:

• Questions are really high quality, unlike some other exams where questions don’t make real sense or don’t have any completely correct answers to choose from.
• It’s not as commercial as some other certifications: you don’t have to take accredited courses, and self-study is accepted. Overall, it can be one of the least expensive certifications you can aim for—if the cost is an important factor for you.
• You learn something really valuable when you try to pass this exam, unlike some other certifications that only force you to memorize a large bunch of unrelated topics.

Cons:

• It’s hard to pass; 85% passing score is really high.
• There’s no single resource that covers 100% of the things you need to know for the exam. So, you’ll have to study many books, and still, you won’t be sure if you know everything.
• There are not many e-Learning courses dedicated to this exam.

SPS Certification Subject Areas

Five subject areas are contained in the syllabus. Therefore, each subject area covers a specific topic. Let’s have a look at the Exam Objectives for this Certification:

Application of Nexus: Apply Nexus to complex situations and large software development efforts.

Nexus Framework: Rules, Roles, Events, and Artifacts of Nexus, the Exoskeleton of Scaled Scrum.

Scaling Framework: Scaling Scrum effectively requires a firm understanding of the Scrum Framework and how it is founded on empirical theory. This includes an understanding of the Scrum principles, values, and a focus on technical excellence.

Key Elements of Nexus

Nexus Roles: Nexus Integration Team, Product Owner in Nexus Integration Team (PO), Scrum Master in Nexus Integration Team (SM), Nexus Integration Team Members

Nexus Events: Refinement, Nexus Sprint Planning, Nexus Sprint Goal, Nexus Daily Scrum, Nexus Sprint Review, and Nexus Sprint Retrospective
Artifacts: Product Backlog (PB), Nexus Sprint Backlog (SB), Integrated Increment
Artifact Transparency: Definition of Done (DoD)

• Nexus’s key focus is to solve the primary source of issues and problems which is dependencies when scaling to multiple Scrum Teams.
• The Nexus Integration Team is a role, performed by people from multiple Scrum Teams under the Nexus Framework. This is not a Scrum of Scrums.
• The Nexus Integration Team behaves as another Scrum Team within the Nexus.
• Integration is another key focus area of Nexus, and while the Nexus Integration Team is responsible for integration, it does not mean that it has to perform integration itself.
• The best way to achieve integration resulting in a Done Increment is through tools and infrastructure that support Continuous Integration, Deployment, and Delivery.
• The work of the Nexus Integration Team requires prodigious amounts of teaching, coaching, and patience.