Free Scrum SPS Exam Actual Questions

The questions for SPS were last updated On Nov 18, 2024

Question No. 1

Scenario A: Nexus Sprint Review with Five Scrum Teams

There are five Scrum Teams working on a product. During the Nexus Sprint Review, the teams

present the results of the Sprint. After introductions, each team takes time to present their work

for inspection by individually showing the new features they have built. They are not using a

shared environment. The stakeholders do not provide much feedback. The event ends and

people filter out of the room.

What could help this Nexus create a single Integrated Increment for inspection at the Nexus

Sprint Review?

(choose the best answer)

Show Answer Hide Answer
Correct Answer: B

The Nexus framework is a way of scaling Scrum for multiple teams working on a single product. The Nexus framework uses Scrum as its building block and extends it only where necessary to minimize and manage dependencies between teams 11. The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the teams in a Nexus 11. One of the key artifacts in the Nexus framework is the Integrated Increment, which is the integrated aggregation of all work completed by all the Scrum Teams in a Nexus 11.

In Scenario A, the Nexus Sprint Review is not conducted effectively. The teams are not using a shared environment to demonstrate the Integrated Increment, but rather showing their individual work. This means that the stakeholders cannot see the whole product and how it works together. The teams are also delaying the integration of their work, which can lead to quality issues, technical debt, and increased complexity 11. The stakeholders do not provide much feedback, which means that the Nexus cannot adapt to the changing needs and expectations of the customers and users. The event ends without any clear outcomes or next steps.

What could help this Nexus create a single Integrated Increment for inspection at the Nexus Sprint Review is:

Enforce a Definition of Done across the entire Nexus that includes integration. This is answer B. This is a valid answer because the Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product 11. The Definition of Done is used to assess when work is complete on the product Increment 11. The Definition of Done is defined by the Nexus and applies to all the work done by the Scrum Teams in the Nexus 11. The Definition of Done should include integration as one of the criteria, which means that the work done by the teams should be integrated frequently and continuously throughout the Sprint 11. By enforcing a Definition of Done that includes integration, the Nexus can ensure that the Integrated Increment is usable and potentially releasable, which means it meets the quality standards and expectations of the stakeholders 11.

The other three answers are not correct because:

Reserve the last few days of the Sprint for testing and integration. This is answer A. This is not a valid answer because reserving the last few days of the Sprint for testing and integration is not a good practice. It implies that the teams are not testing and integrating their work throughout the Sprint, but rather doing it at the end of the Sprint. This can lead to quality issues, technical debt, and increased complexity 11. It also reduces the time available for inspection and adaptation, which are essential for empiricism and agility 11.

Have the Nexus Integration Team integrate all the work as early as possible. This is answer C. This is not a valid answer because the Nexus Integration Team is not the only one responsible for integrating all the work. The Nexus Integration Team is a role that consists of the Scrum Master, the Product Owner, and other members who are responsible for coordinating, coaching, and supervising the integration of the work done by the teams in the Nexus 11. The Nexus Integration Team facilitates the integration of the work, but does not do it for the teams 11. The teams are responsible for integrating their own work and delivering a potentially releasable Increment of product value in each Sprint 11.

Have a Sprint dedicated to integration. This is answer D. This is not a valid answer because having a Sprint dedicated to integration is not consistent with Scrum or Nexus. Scrum and Nexus require that the teams deliver a potentially releasable Increment of product value in each Sprint 11. Having a Sprint dedicated to integration means that the teams are not delivering any value or receiving any feedback in that Sprint 11. It also means that the teams are accumulating technical debt and complexity that will make integration more difficult and risky 11.


Question No. 2

Which statements best describe a Nexus Sprint Review?

(choose the best two answers)

Show Answer Hide Answer
Question No. 3

Scenario B: Six Team Nexus with complex dependencies

A six team Nexus is developing a complex product, with different parts of the product that only

certain Scrum Teams can work on. In fact, there are some highly specialized individuals outside

the Nexus that are required for some of the work. In past Sprints the Nexus encountered

challenges dealing with the many dependencies between Scrum Teams.

Some individual Scrum Teams in this Nexus have said that they do not see how the work they

are doing is contributing to the product's progress. What is the best remedy for this situation?

(choose the best answer)

Show Answer Hide Answer
Correct Answer: B

The best remedy for this situation is to ensure that all Scrum Teams understand the Nexus Sprint Goal. The Nexus Sprint Goal is a commitment that describes the purpose that will be achieved by the Nexus during the Sprint. It aligns with the Product Goal and provides coherence and focus for the work of the Scrum Teams. By understanding the Nexus Sprint Goal, the Scrum Teams can see how their work contributes to the product's progress and value delivery 1234.

The other answers are not effective for this situation because:

A . During Nexus Sprint Planning, have all the teams plan the Sprint together in one room, so they can see what other teams are working on. This answer is not sufficient because it does not address the root cause of the problem, which is the lack of a clear and shared purpose for the Sprint. Having all the teams plan the Sprint together may help them coordinate their work and identify dependencies, but it does not necessarily help them understand how their work relates to the product's progress and value.

C . Ask the Scrum Master to explain to the teams that the Product Owner can choose which features to work on, as she has the final say. This answer is not helpful because it does not foster collaboration and alignment among the Scrum Teams. It also undermines the self-organization and empowerment of the Scrum Teams, and reduces their ownership and accountability for the work. The Product Owner is responsible for managing and ordering the Product Backlog, but the Scrum Teams are responsible for selecting and delivering the work for the Sprint.

D . During Nexus Sprint Planning, ask each Scrum Team to create a Sprint Goal that describes the purpose of the Sprint. This answer is not optimal because it does not ensure that the Scrum Teams have a common objective and direction for the Sprint. Each Scrum Team may have a different Sprint Goal that may or may not align with the Nexus Sprint Goal and the Product Goal. This may lead to confusion, inconsistency, and sub-optimization of the product delivery.


Question No. 4

Scenario A: Nexus Sprint Review with Five Scrum Teams

There are five Scrum Teams working on a product. During the Nexus Sprint Review, the teams

present the results of the Sprint. After introductions, each team takes time to present their work

for inspection by individually showing the new features they have built. They are not using a

shared environment. The stakeholders do not provide much feedback. The event ends and

people filter out of the room.

If this pattern of Nexus Sprint Reviews continues for multiple Sprints, what may be the effects?

(choose the best two answers)

Show Answer Hide Answer
Correct Answer: B, D

The Nexus Sprint Review is an event where the Nexus, consisting of multiple Scrum Teams, presents the Integrated Increment to the stakeholders for inspection and feedback 1. The Integrated Increment is the sum of all the work done by the Scrum Teams in a Sprint that meets the Definition of Done 1. The purpose of the Nexus Sprint Review is to inspect the outcome of the Sprint, discuss the progress toward the Product Goal, discuss any changes in the environment, and collaborate on what to do next 2.

In Scenario A, the Nexus Sprint Review is not conducted effectively. The teams are not using a shared environment to demonstrate the Integrated Increment, but rather showing their individual work. This means that the stakeholders cannot see the whole product and how it works together. The teams are also delaying the integration of their work, which can lead to quality issues, technical debt, and increased complexity 1. The stakeholders do not provide much feedback, which means that the Nexus cannot adapt to the changing needs and expectations of the customers and users. The event ends without any clear outcomes or next steps.

If this pattern continues for multiple Sprints, the effects may be:

Quality will degrade as the teams delay creating a single Integrated Increment. This is answer B. By not integrating their work frequently and continuously, the teams will face more challenges and risks in ensuring that the product is functional, reliable, and usable. The teams will also miss the opportunity to validate their assumptions and learn from the feedback on the Integrated Increment 1.

Ability to adapt will suffer as the stakeholders continue to disengage and not give feedback. This is answer D. By not engaging the stakeholders in a meaningful dialogue and collaboration, the Nexus will lose the insight and direction that the feedback provides. The Nexus will also risk building the wrong product or features that do not meet the needs and expectations of the customers and users. The stakeholders will also lose trust and confidence in the Nexus and the product 2.

The other two answers are not correct because:

There will be more and more work to inspect so teams will need their own individual Sprint Reviews. This is answer A. This is not a valid effect because the Nexus Sprint Review replaces the individual Scrum Team Sprint Reviews 1. The Nexus Sprint Review is not a time for each team to present their work, but rather for the Nexus to present the Integrated Increment. The teams should not need their own Sprint Reviews, but rather focus on integrating their work and delivering a valuable product 1.

Empiricism will suffer as the teams cannot produce a shared velocity. This is answer C. This is not a valid effect because velocity is not a measure of empiricism. Empiricism is the principle of making decisions based on observation, inspection, and adaptation 1. Velocity is a measure of the amount of work done by a team or a Nexus in a Sprint. Velocity is not a mandatory artifact or metric in Scrum or Nexus, and it does not reflect the quality or value of the work done 1.


Question No. 5

Scenario C: Dependencies and Product Backlog items

During Nexus Sprint Planning, representatives from each of the 9-member Scrum Teams

identify many dependencies. This makes it hard for them to choose the work they could pull

into their individual teams for the next Sprint. No matter how they reorganize the Product

Backlog items, they continually find more or new dependencies.

What techniques could help this Nexus manage their dependencies effectively?

(choose the best two answers)

Show Answer Hide Answer
Correct Answer: B, D

When a Nexus, which is a group of approximately three to nine Scrum Teams working on the same product, faces many dependencies during Nexus Sprint Planning, it can use some techniques to manage them effectively. One technique is to reorganize team members between the teams to eliminate cross-team dependencies. This can be done by forming feature teams or component teams based on the nature of the work and the skills required. By doing so, the Nexus can reduce the need for coordination and integration across teams, and increase the autonomy and ownership of each team 1122. Therefore, statement B is correct.

Another technique is to reorder Product Backlog items to better accommodate dependencies. This can be done by applying dependency management techniques such as dependency mapping, dependency inversion, dependency breaking, and dependency prioritization. By doing so, the Nexus can identify, visualize, resolve, and minimize the dependencies that affect the delivery of the Integrated Increment, which is the combined work of all the Scrum Teams in the Nexus that meets the Nexus Sprint Goal 334455. Therefore, statement D is also correct.

Statement A is incorrect because it implies that the Nexus Integration Team, which is a group of people who are accountable for ensuring the integration and delivery of the Integrated Increment, should do the dependent work ahead of the Sprint for the teams. This would create a bottleneck and a single point of failure, as well as undermine the self-organization and collaboration of the Scrum Teams 1122. Statement C is incorrect because it suggests that the Nexus should extend the Sprint so that the teams can have more time to complete the dependent work. This would violate the Scrum principle of time-boxing, which ensures that the Nexus delivers value frequently and incrementally, and inspects and adapts its process regularly 1122.