Scrum.org Scaled Professional Scrum (SPS)

What is the maximum number of Scrum Teams that can form a Nexus?

• A5 Scrum Teams
• B9 Scrum Teams
• C12 Scrum Teams
• DThere is no maximum

How many Product Backlogs exist in a Nexus of six Scrum Teams?

• ASix — one per Scrum Team
• BTwo — one for the Nexus Integration Team and one shared
• COne single Product Backlog shared by all teams
• DSix team backlogs plus one Nexus backlog

Who is accountable for maximizing the value of the product and the work performed by all Scrum Teams in a Nexus?

• AThe Nexus Integration Team collectively
• BEach Scrum Team's Product Owner
• CThe single Product Owner
• DThe Nexus Scrum Master

Which additional accountability does the Nexus framework introduce beyond those defined in the Scrum Guide?

• ARelease Train Engineer
• BNexus Integration Team
• CChief Product Owner
• DScrum of Scrums Master

What is the composition of the Nexus Integration Team?

• AOne representative from each Scrum Team with no Product Owner involvement
• BThe Product Owner, a Scrum Master, and Nexus Integration Team Members
• CThe Scrum Masters of all Scrum Teams in the Nexus
• DA dedicated team of architects and DevOps engineers only

What is the primary accountability of the Nexus Integration Team?

• AManaging the Product Backlog on behalf of the Product Owner
• BFacilitating all cross-team meetings in the Nexus
• CEnsuring that a done Integrated Increment is produced at least every Sprint
• DReporting project status to organizational leadership

Which of the following best describes the Integrated Increment in Nexus?

• AA report summarizing each team's Sprint output
• BThe current sum of all integrated work completed by a Nexus
• CThe Sprint Goal for the entire Nexus
• DThe set of Product Backlog items selected by the NIT

What is the commitment associated with the Integrated Increment in Nexus?

• AThe Nexus Sprint Goal
• BThe Product Goal
• CThe Definition of Done
• DThe Release Plan

What is the Nexus Sprint Backlog?

• AAn additional backlog maintained by the Nexus Integration Team separate from the Product…
• BThe composite of all team Sprint Backlogs plus the Nexus Sprint Goal, used to visualize c…
• CA tool for the Product Owner to manage inter-team priorities
• DA list of impediments tracked during the Sprint

During Cross-Team Refinement, what is the primary purpose of this Nexus event?

• ATo allow each team to refine its own Sprint Backlog independently
• BTo reduce cross-team dependencies and make Product Backlog items ready for individual tea…
• CTo replace the Sprint Review by integrating stakeholder feedback
• DTo assign Product Backlog items to specific Scrum Teams

How does Nexus Sprint Planning differ from a standard Scrum Sprint Planning?

• AIt is optional in Nexus if teams are experienced enough
• BIt adds a Nexus-level phase where all teams coordinate before planning their individual S…
• CIt eliminates individual team Sprint Planning sessions
• DIt lasts exactly twice as long as regular Sprint Planning

What is the purpose of the Nexus Daily Scrum?

• ATo replace each team's Daily Scrum with a single Nexus-wide standup
• BTo identify integration issues and cross-team impediments so teams can adapt their plans
• CTo allow the Product Owner to re-prioritize the backlog each day
• DTo report progress to organizational management

In Nexus, who typically attends the Nexus Daily Scrum?

• AAll members of all Scrum Teams simultaneously
• BOnly the Nexus Integration Team members
• CAppropriate representatives from each Scrum Team
• DOnly the Scrum Masters from each team

What is the key output inspected during the Nexus Sprint Review?

• AEach team's individual Sprint velocity and burndown chart
• BThe Integrated Increment produced by all teams during the Sprint
• CThe Nexus Sprint Backlog completion rate
• DEach team's individual Definition of Done compliance

During the Nexus Sprint Retrospective, what unique concern does Nexus add compared to a standard Scrum Retrospective?

• AEach team is required to present its own retrospective findings to all other teams
• BThe Nexus Sprint Retrospective only focuses on the NIT's performance
• CCross-team impediments, the effectiveness of the Nexus as a whole, and integration practi…
• DThe Product Owner sets the improvement items for all teams

A team in the Nexus discovers mid-Sprint that its work creates an unresolved dependency blocking two other teams. What should happen first?

• AEscalate to the Product Owner to re-prioritize the Product Backlog
• BRaise the dependency at the next Nexus Daily Scrum so all relevant teams can coordinate
• CWait until the Nexus Sprint Review to surface the dependency
• DThe blocked teams should remove those items from their Sprint Backlog

How does Nexus handle the Definition of Done across multiple Scrum Teams?

• AEach Scrum Team maintains its own Definition of Done independently
• BThere is a single shared Definition of Done that all teams must meet for the Integrated I…
• CThe NIT defines separate Definitions of Done for each team based on their domain
• DThe Definition of Done is optional at the team level but mandatory at the Nexus level

In the Nexus Guide, which empirical pillar does managing and visualizing cross-team dependencies primarily support?

• AAdaptation
• BInspection
• CTransparency
• DCommitment

A Nexus is struggling to produce an Integrated Increment each Sprint because integration is always left to the last two days. What does the Nexus Guide recommend?

• AAdd a dedicated integration Sprint at the end of every Release Train
• BHire more testers and DevOps engineers for the NIT
• CIntegrate continuously throughout the Sprint, not just at the end
• DReduce the number of Scrum Teams to simplify integration

Which Nexus artifact exists to make the overall Sprint plan and cross-team dependencies transparent?

• AThe Nexus Product Backlog
• BThe Nexus Integration Board
• CThe Nexus Sprint Backlog
• DThe Dependency Register

A member of the Nexus Integration Team is also a Developer on one of the Scrum Teams. What does the Nexus Guide say about this?

• ANIT members must be fully dedicated and cannot work on any Scrum Team
• BNIT members may also work on Scrum Teams, but priority must be given to NIT work
• CNIT members cannot attend team-level events if they participate in Nexus events
• DOnly the Scrum Master on the NIT may work on an individual Scrum Team

What does the Nexus Sprint Goal represent?

• AThe Product Goal broken into Sprint-sized chunks for each team
• BThe objective for the Sprint that all Scrum Teams in the Nexus are working toward collect…
• CA milestone marker set by organizational management
• DThe combined individual Sprint Goals of all teams in the Nexus

Scrum Team A in a Nexus finishes its work on day 5 of a 10-day Sprint. How should Team A proceed according to Nexus principles?

• AWait for other teams to finish so they can all review together
• BBegin planning work for the next Sprint immediately
• CHelp other teams that have remaining work or address cross-team dependencies
• DTake the remaining Sprint days for team-building and training

Which of the following is a key scaling myth that Nexus is designed to counter?

• AThat empiricism does not scale beyond one team
• BThat adding more Scrum Teams automatically increases product output proportionally
• CThat the Scrum Guide must be replaced entirely when scaling
• DThat Product Owners cannot manage large backlogs without a hierarchy of owners

What is the minimum number of Scrum Teams required to form a Nexus?

• ATwo Scrum Teams
• BThree Scrum Teams
• CFour Scrum Teams
• DFive Scrum Teams

How does Nexus augment the standard Scrum framework?

• ABy replacing Scrum roles with new scaling roles
• BBy adding the Nexus Integration Team accountability and Nexus-level events and artifacts…
• CBy introducing a Program Increment planning ceremony on top of Scrum
• DBy eliminating the Sprint Retrospective to save time across many teams

A Product Owner in a Nexus has trouble keeping the Product Backlog refined at the pace needed for six teams. What is the most appropriate Nexus-aligned approach?

• AAssign a Product Owner per team to manage team-level backlogs
• BUse Cross-Team Refinement sessions with team members to share the refinement work while t…
• CDelegate the Product Backlog management to the Nexus Integration Team
• DReduce the number of teams so the Product Owner can keep up

Which statement best describes the relationship between the Nexus Sprint Retrospective and individual team Sprint Retrospectives?

• AThe Nexus Sprint Retrospective replaces all individual team retrospectives
• BIndividual team retrospectives happen first, then insights inform a Nexus-level retrospec…
• CIndividual team retrospectives are held before the Nexus Retrospective; then teams may ho…
• DThe Nexus Sprint Retrospective is held by the NIT only; teams hold their own separately

In Nexus, what is the role of the Scrum Master on the Nexus Integration Team?

• ATo manage the team-level Scrum Masters and report on their performance
• BTo ensure the Nexus framework is understood and enacted as described in the Nexus Guide
• CTo create the release plan for all Scrum Teams in the Nexus
• DTo resolve all technical integration issues personally

How should Nexus teams handle a cross-team dependency discovered during Nexus Sprint Planning?

• ARemove all dependent items from the Sprint and defer to the next Sprint
• BMake the dependency transparent in the Nexus Sprint Backlog and coordinate which team wil…
• CAssign the dependent item to the Nexus Integration Team to resolve
• DEscalate to the Product Owner to reprioritize the backlog before any team begins work

Why is minimizing cross-team dependencies a core goal of the Nexus framework?

• ADependencies require additional documentation and slow down ceremonies
• BDependencies increase coordination overhead and reduce the Nexus's ability to deliver a d…
• CDependencies violate the Scrum principle of self-organizing teams
• DDependencies are only problematic in hardware development, not software

What does the Nexus Guide mean when it says Nexus 'preserves' the Scrum framework?

• ANexus freezes Scrum and prevents teams from adapting it
• BNexus adds roles and events on top of Scrum without changing or removing any Scrum accoun…
• CNexus preserves the Sprint length of two weeks for all teams
• DNexus keeps teams from experimenting with new practices

During Nexus Sprint Planning, all teams have selected their work and plan to begin. A team realizes the sequencing of dependent work items makes it impossible to finish integration by Sprint end. What should the teams do?

• AProceed and raise the issue at the Nexus Sprint Review
• BRemove the dependent items from the Sprint and inform the Product Owner
• CRevisit the selection and sequencing of backlog items to create a viable integrated plan…
• DAsk the Nexus Integration Team to solve the sequencing problem

What does the Nexus Guide say about the frequency of integration across Scrum Teams within a Sprint?

• ATeams should integrate at the end of the Sprint only to minimize disruption
• BIntegration is required at least once per day
• CIntegration should happen as frequently as possible and at least once per Sprint
• DThe NIT decides the integration frequency each Sprint during planning

An organization is running five Scrum Teams on a single product without Nexus. They have integration problems every Sprint. Which Nexus mechanism most directly addresses late-Sprint integration failures?

• AIncreasing the Sprint length to give more time for integration
• BAdding an integration Sprint between feature Sprints
• CContinuous integration supported by Cross-Team Refinement and the Nexus Daily Scrum to ca…
• DAssigning one Scrum Team exclusively to integration and testing

What does 'appropriate representatives' mean in the context of the Nexus Daily Scrum?

• AOnly Scrum Masters from each team
• BPeople from each team who have knowledge of the cross-team integration and dependency iss…
• CThe Product Owner and one Developer from each team
• DAll team members who are blocked by a cross-team dependency

What is the primary difference between the Nexus Sprint Backlog and individual team Sprint Backlogs?

• AThe Nexus Sprint Backlog contains only the NIT's work; team backlogs contain team work
• BThe Nexus Sprint Backlog is the composite of all team Sprint Backlogs plus the Nexus Spri…
• CTeam Sprint Backlogs are optional in Nexus; only the Nexus Sprint Backlog is required
• DThe Nexus Sprint Backlog is managed by the Product Owner; team backlogs are managed by th…

In Nexus, at what level is the Definition of Done owned and maintained?

• AEach team defines its own, with no Nexus-level standard
• BThe Nexus Integration Team creates it and teams follow it without input
• CThe Nexus defines a shared Definition of Done; individual teams may strengthen but not we…
• DThe Product Owner defines the Definition of Done unilaterally

What is the most important outcome the Nexus Sprint Review should produce?

• AA velocity report for each Scrum Team in the Nexus
• BA revised Product Backlog that reflects stakeholder feedback on the Integrated Increment
• CA list of impediments identified by the Nexus Integration Team
• DFormal sign-off from management on the Sprint's deliverables

A Nexus has five Scrum Teams. Two teams regularly deliver done increments each Sprint; three teams consistently fail to integrate their work. What does the Nexus Guide suggest as the first inspection target?

• AReplace the three struggling teams' Scrum Masters
• BSplit the three struggling teams into smaller teams
• CInspect how cross-team dependencies are being managed and whether integration practices a…
• DIncrease the Sprint length to give struggling teams more time

What is the Nexus Sprint Goal's commitment artifact?

• AThe Product Backlog
• BThe Integrated Increment
• CThe Nexus Sprint Backlog
• DThe Definition of Done

Which of the following correctly lists all the Nexus events as defined in the Nexus Guide?

• ACross-Team Refinement, Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review, Nex…
• BNexus Daily Scrum, Nexus Sprint Planning, Nexus Sprint Review, Nexus Sprint Retrospective
• CScrum of Scrums, Cross-Team Refinement, Nexus Sprint Planning, Nexus Sprint Review
• DCross-Team Refinement, Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review

What are the three artifacts defined in the Nexus framework?

• AProduct Backlog, Nexus Sprint Backlog, Integrated Increment
• BProduct Backlog, Sprint Backlog, Increment
• CNexus Sprint Backlog, Integrated Increment, Dependency Map
• DProduct Backlog, Nexus Sprint Backlog, Definition of Done

The Nexus Integration Team identifies that a team's practices are preventing integration. What is the NIT's most appropriate action?

• AReport the team to senior management for remediation
• BTake over that team's Sprint Planning to fix their practices
• CCoach and support the team to improve the practices that are causing the integration prob…
• DRemove that team from the Nexus until their practices improve

How does having a single Product Goal affect teams in a Nexus?

• AIt limits each team to working on one feature area, reducing flexibility
• BIt unifies all teams toward a common product direction, ensuring their Sprint Goals align…
• CIt requires all teams to complete the Product Goal before any Sprint can begin
• DIt prevents the Product Owner from re-ordering the Product Backlog mid-Sprint

What is the most significant organizational impact of adopting Nexus?

• AOrganizations must restructure into program-level hierarchies with a program manager
• BOrganizations need to support a single Product Owner accountable for one integrated produ…
• COrganizations must standardize on two-week Sprints for all teams in the Nexus
• DOrganizations are required to adopt SAFe alongside Nexus for governance