QUESTION: 9

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.
Since teams are not using a shared environment, what is likely? (choose the best two answers)

The Sprint is too short.
The Nexus has not yet reached the integration phase.
There is no single Integrated Increment.
The Nexus Integration Team is lacking or nonexistent.

Answer(s): C,D

Explanation:

According to the Nexus Guide1, the Nexus Sprint Review is an event where the Nexus presents the Done Integrated Increment that was built over the Sprint and collects feedback from the stakeholders. The Integrated Increment is the combined work of all the Scrum Teams in the Nexus that meets the Definition of Done. The Nexus Guide also states that the Nexus Integration Team is a specialized Scrum Team that provides services and guidance to the Scrum Teams in the Nexus to ensure that the Integrated Increment is produced every Sprint. In the scenario, the teams are not using a shared environment, which implies that they are not integrating their work frequently and effectively. This means that there is no single Integrated Increment that can be inspected and adapted by the stakeholders. This also suggests that the Nexus Integration Team is lacking or nonexistent, or that it is not fulfilling its role of facilitating integration and resolving dependencies. Without a Nexus Integration Team and a shared environment, the Nexus cannot deliver a valuable product Increment that meets the Product Goal. The Sprint length and the integration phase are not relevant to the scenario. The Sprint length is determined by the Nexus based on the complexity and uncertainty of the product, and it should be less than a month. The integration phase is not a separate phase in Nexus, but a continuous activity that happens throughout the Sprint. Therefore, A and B are not correct answers.

Reveal Solution Next Question

QUESTION: 10

The Scrum Teams in a Nexus find they have simply too much work each Sprint to do to deliver a valuable and useful Increment.
What could they try to improve their ability to produce an Increment for the next Sprint?

(choose the best answer)

Reduce the amount of work that the teams pull into the Sprint.
Ask the Nexus Integration Team to extend the Sprint to allow more time for integration.
Reduce the number of Scrum Teams to reduce complexity.
Add another Scrum Team to the Nexus to increase capacity.

Answer(s): A

Explanation:

The best way to improve the ability of the Scrum Teams in a Nexus to produce an Increment for the next Sprint is to reduce the amount of work that the teams pull into the Sprint. This will allow the teams to focus on delivering a high-quality and valuable product Increment that meets the Definition of Done and the Product Goal. Reducing the amount of work also reduces the complexity and dependencies among the teams, which makes integration easier and faster. The other options are not advisable for the following reasons:
Asking the Nexus Integration Team to extend the Sprint to allow more time for integration is not consistent with the Scrum principles and values. The Sprint length should be fixed and consistent throughout the product development, and it should be less than a month. Extending the Sprint would compromise the feedback loop, the transparency, and the adaptability of the Nexus 11.

Reducing the number of Scrum Teams to reduce complexity is not a viable solution, as it would also reduce the capacity and the productivity of the Nexus. The number of Scrum Teams in a Nexus should be based on the size and the scope of the product, and it should not exceed nine teams 11. Reducing the number of teams would also disrupt the existing team dynamics and collaboration. Adding another Scrum Team to the Nexus to increase capacity is not a good idea, as it would increase the complexity and the dependencies among the teams. Adding another team would also require more coordination and communication, which would consume more time and resources. Moreover, adding another team would not necessarily increase the value or the quality of the product Increment 22.

Reveal Solution Next Question

QUESTION: 11

A company has five products and are using Scrum for product delivery.
Which statements represent the best option for how Product Ownership might be structured? (choose the best two answers)

Assign as many Product Owners as needed to communicate expectations and requirements to the Scrum Team.
One Product Owner responsible for each product. Each of these Product Owners may delegate work as needed, but they remain accountable for the value delivered by their product.
One Product Owner responsible for all five products. This Product Owner may delegate work as needed, but the Product Owner remains accountable for the value delivered.
One primary Product Owner and one Product Owner for each product. The primary Product owner delegates all accountability for delivering value to the Product Owners for each product.

Answer(s): B,C

Explanation:

The best option for how Product Ownership might be structured in a company with five products is to have one Product Owner responsible for each product or one Product Owner responsible for all five products. Both of these options are consistent with the Scrum Guide, which states that the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team 11. The Product Owner may delegate work as needed, but they remain accountable for the value delivered. The Product Owner also provides clarity to the team about the product vision, goal, and backlog 11.
The other options are not advisable for the following reasons:
Assigning as many Product Owners as needed to communicate expectations and requirements to the Scrum Team is not a good idea, as it would create confusion, inconsistency, and conflict among the Product Owners and the Scrum Team. The Scrum Guide states that the Product Owner is one person, not a committee 11. Having multiple Product Owners for one product would compromise the transparency, the alignment, and the decision-making of the Scrum Team. Having one primary Product Owner and one Product Owner for each product is also not a good idea, as it would create a hierarchy and a dependency among the Product Owners. The primary Product Owner would have too much authority and responsibility, while the Product Owners for each product would have too little. This would undermine the accountability, the collaboration, and the empowerment of the Product Owners and the Scrum Teams.

Reveal Solution Next Question

QUESTION: 12

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 would you recommend to the two teams that are continually dependent on each other to help them manage their work?

(choose the best answer)

The Nexus Integration Team should be responsible for integrating the work of these two Scrum Teams.
Reorganize these two Scrum Teams so that one is responsible for development and one is responsible for integration.
Merge the two Scrum Teams together.
Ensure the appropriate representatives from both teams are present during Cross- Team Refinement.

Answer(s): D

Explanation:

The best way to help the two teams that are continually dependent on each other to manage their work is to ensure the appropriate representatives from both teams are present during Cross-Team Refinement. Cross-Team Refinement is an optional event in Nexus that allows the Scrum Teams to collaborate and coordinate on the Product Backlog items that have dependencies or require integration 11. By having the representatives from both teams present during this event, they can identify and resolve the dependencies, clarify the requirements, align the expectations, and plan the work for the next Sprint. This will improve the transparency, the quality, and the value of the Integrated Increment.
The other options are not advisable for the following reasons:
The Nexus Integration Team should not be responsible for integrating the work of these two Scrum Teams, as this would create a bottleneck and a hand-off. The Nexus Integration Team is a specialized Scrum Team that provides services and guidance to the Scrum Teams in the Nexus to ensure that the Integrated Increment is produced every Sprint 11. However, the Nexus Integration Team is not accountable for the integration of the work of the individual Scrum Teams, as this is the responsibility of the Scrum Teams themselves 22.
Reorganizing these two Scrum Teams so that one is responsible for development and one is responsible for integration is not a good idea, as this would create a silo and a separation of concerns. The Scrum Teams in a Nexus should be cross-functional and self-organizing, meaning that they have all the skills and abilities to deliver a potentially releasable product Increment every Sprint
11. Separating the development and the integration tasks would compromise the collaboration, the feedback, and the agility of the Scrum Teams.
Merging the two Scrum Teams together is not a viable solution, as this would create a large and unwieldy team. The Scrum Guide states that the optimal size of a Scrum Team is between three and nine members 33. Merging two Scrum Teams together would exceed this limit and create challenges in communication, coordination, and decision-making. Moreover, merging the two teams would not necessarily eliminate the dependencies, as they may still exist within the larger team or with other teams in the Nexus.

Reveal Solution Next Question

Free SPS Exam Braindumps (page: 3)

QUESTION: 9

Explanation:

QUESTION: 10

Explanation:

QUESTION: 11

Explanation:

QUESTION: 12

Explanation: