SPS Exam Dumps Fast-Track Your Scrum Success and Certification

1. Scrum SPS Scaled Professional Scrum (SPS) QUESTION & ANSWERS Visit Now: https://www.scrumdumps.com

2. QUESTION: 1 Which two statements best describe a Nexus Sprint Review? Select the two best answers Option A : It is when all teams must demo their work. Option B : It replaces individual Scrum Team Sprint Reviews. Option C : It is when feedback is given on the Integrated Increment. Option D : It is a container for each individual Scrum Team's Sprint Review. Correct Answer: B,C Explanation/Reference: A Nexus Sprint Review replaces individual Scrum Team Sprint Reviews, because the entire Integrated Increment is the focus for capturing feedback from stakeholders. It may not be possible to show all completed work in detail. Techniques may be necessary to maximize stakeholder feedback Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 2 You have been assigned as the Scrum Master of six new Scrum Teams that will build one product. What conditions should you strive for in this scenario? (choose the best two answers) Option A : There should be six Product Owners, one for each Scrum Team. Option B : There should be six Product Owners, one of whom is chief Product Owner. Option C : The product has one Product Backlog. Option D : There should be only one Product Owner who is accountable for the success of the product. Option E : Each Scrum Team should have a separate Product Backlog. Correct Answer: C,D Explanation/Reference: When six new Scrum Teams are working on one product, they should form a Nexus, which is a framework for scaling Scrum 11.

3. A Nexus has a single Product Owner who is accountable for maximizing the value of the product and the work performed and integrated by the Scrum Teams 1122. Therefore, statement D is correct. A Nexus also works off a single Product Backlog, which is an ordered list of the work to be done by the Scrum Teams in the Nexus 11. The Product Backlog has a single source of requirements and priorities for the product, and it is managed by the Product Owner 1122. Therefore, statement C is also correct. Statements A, B, and E are incorrect because they imply that each Scrum Team has its own Product Owner and Product Backlog, which would create confusion, inconsistency, and duplication of work. Having multiple Product Owners and Product Backlogs would also undermine the transparency and alignment that are essential for scaling Scrum 1122. Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 3 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) Option A : The Nexus Integration Team should complete the dependent work ahead of the Sprint for the teams Option B : Reorganize team members between the teams to eliminate cross-team dependencies. Option C : Extend the Sprint so that the teams can have more time to complete the dependent work. Option D : Reorder Product Backlog items to better accommodate dependencies. Correct Answer: B,D

4. Explanation/Reference: 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 Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 4 What are three benefits of self-managing Scrum Teams? (choose the best three answers) Option A : Increased rule compliance. Option B : Increased self-accountability. Option C : Increased creativity. Option D : Increased commitment. Option E : Increased accuracy of estimates. Correct Answer: B,C,D Explanation/Reference: Self-managing Scrum Teams are teams that internally decide who does what, when, and how, rather than being directed by others outside the team 11. Self-managing Scrum Teams have the following benefits: Increased self-accountability: Self-

5. managing Scrum Teams are accountable for delivering a potentially releasable product Increment every Sprint that meets the Definition of Done and the Product Goal 22. They are also accountable for following the Scrum values and principles, and for inspecting and adapting their work and process 33. By being accountable for their own decisions and actions, self-managing Scrum Teams are more responsible, transparent, and quality-oriented. Increased creativity: Self-managing Scrum Teams have the autonomy and the empowerment to choose how best to accomplish their work, rather than being constrained by predefined methods or instructions 44. They also have the opportunity to experiment, learn, and innovate, as they are encouraged to try new ideas and approaches to solve complex problems [5]. By having the freedom and the support to be creative, self-managing Scrum Teams are more productive, adaptive, and valuable. Increased commitment: Self-managing Scrum Teams have the ownership and the involvement in their work, as they are part of the planning, execution, and review of the product development [6]. They also have the trust and the collaboration among the team members, as they share a common goal and vision, and respect each other’s skills and abilities [7]. By having the sense of belonging and the teamwork, self-managing Scrum Teams are more motivated, engaged, and satisfied. Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 5 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) Option A : There will be more and more work to inspect so teams will need their own individual Sprint Reviews. Option B : Quality will degrade as the teams delay creating a single Integrated Increment. Option C : Empiricism will suffer as the teams cannot produce a shared velocity. Option D : Ability to adapt will suffer as the stakeholders continue to disengage and not give feedback.

6. Correct Answer: B,D Explanation/Reference: 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.

7. 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. Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 6 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) Option A : Reserve the last few days of the Sprint for testing and integration. Option B : Enforce a Definition of Done across the entire Nexus that includes integration. Option C : Have the Nexus Integration Team integrate all the work as early as possible. Option D : Have a Sprint dedicated to integration. Correct Answer: B

8. Explanation/Reference: 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

9. 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. Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 7

10. In the first part of Nexus Sprint Planning, representatives from the each of the 8-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. There are especially two teams that have a lot of dependent work. What should the Scrum Teams do to effectively deal with their dependencies? Option A : All the answer listed here. Option B : Increase Product Backlog Refinement in order to create more clarity around the work that needs to be completed. Option C : Merge the two Scrum Teams together that have the most dependencies with each other. Option D : Institute quarterly meetings for planning out all dependencies between teams. Correct Answer: B Explanation/Reference: Ideally, the Product Backlog should be adequately refined with dependencies identified and removed or minimized prior to Nexus Sprint Planning. However New dependencies may emerge during Nexus Sprint Planning. QUESTION: 8 The Product Owner decides on how many Product Backlog items should be assigned to a Teams Sprint Backlog. Option A : False Option B : True Correct Answer: A Explanation/Reference: The Sprint Backlog is created during the beginning of the Sprint. The Development Team works with the Product Owner to pull in the work, into their individual Sprint Backlogs. The Sprint Backlog captures all the work which the Development Team identifies as necessary, to meet the Sprint Goal. Developers keep adding tasks during the Sprint, so, the Sprint Backlog keeps getting updated. The Sprint Backlog is the Development Team's plan for the current Sprint. This plan is not detailed upfront. Only the Development Team can change its Sprint. Download from Here: https://www.scrumdumps.com/SPS-exam-questions

11. QUESTION: 9 What does the Nexus framework consist of? Select the four best answers Option A : Rules Option B : Increments Option C : Artifacts Option D : Events Option E : Inspect Option F : Roles Correct Answer: A,C,D Explanation/Reference: Nexus is a framework consisting of roles, events, artifacts, and rules that bind and weave together the work of approximately three to nine Scrum Teams working on a single Product Backlog to build an Integrated Increment that meets a sprint goal. QUESTION: 10 True or False: Scrum Teams must report back to the Nexus Integration Team right after their individual Daily Scrums. Option A : True Option B : False Correct Answer: B Explanation/Reference: Scrum Teams do not have to report back to the Nexus Integration Team right after their individual Daily Scrums. 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 Scrum Teams in the Nexus 14. The Nexus Daily Scrum is an event where the Nexus Integration Team and one or two representatives from each Scrum Team meet to inspect the current state of the Integrated Increment and identify any integration issues or dependencies 12. The Nexus Daily Scrum takes place before the individual Daily Scrums of the Scrum Teams 13. The purpose of the Nexus Daily Scrum is to coordinate any challenges and dependencies of the day that all teams should be aware of, not to report back to the Nexus Integration Team 12. The individual Daily Scrums of the Scrum Teams are focused on planning how to fix the integration problems and achieve the Sprint Goal 13. Therefore, the statement is false

12. Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 11 How does the Nexus Daily Scrum relate to the Daily Scrum In each Scrum Team? Option A : Work that is identified during the Nexus Daily Scrum is then taken back to individual Scrum Teams for planning inside their Daily Scrum events Option B : These events are completely separate because at the Nexus Daily Scrum only cross-team members identify the issues Option C : Nexus Daily Scrum is the Scrum of Scrums for the daily Scrums Option D : All the answers listed Correct Answer: A Explanation/Reference: Work that is identified during the Nexus Daily Scrum is then taken back to individual Scrum Teams for planning inside their Daily Scrum events QUESTION: 12 The Nexus Integration Team consists of professionals who: Select the three best answers Option A : Are not allowed to work as Development Team members in Scrum Teams. Option B : Develop and Test Code. Option C : Are skilled in the use of tools, various practices, and the general field of systems engineering. Option D : Ensure the Scrum Teams within the Nexus understand and implement the practices and tools needed to detect dependencies, and frequently integrate as artifacts. Option E : Coach the Individual Scrum Teams on the necessary development, infrastructural, or architectural standards required by the organization to ensure the development of quality Integrated Increments. Correct Answer: A,C,D

13. Explanation/Reference: The Nexus integration Team consists of professionals who are skilled in the use of tools, various practices, and the general field of systems engineering. Nexus Integration Team Members ensure the Scrum Teams within the Nexus understand and implement the practices and tools needed to detect dependencies, and frequently Integrate all artifacts. Nexus Integration Team Members are responsible for coaching and guiding the Scrum Teams in a Nexus to acquire, implement, and learn these practices and tools. Additionally, the Nexus Integration Team coaches the individual Scrum Teams on the necessary development, infrastructural, or architectural standards required by the organization to ensure the development of quality Integrated Increments. Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 13 A company has two products. Which of the following Is an acceptable way of forming Scrum teams? Select the two best answers Option A : There should be a Chief Product Owner and one Product Owner for each product Option B : There should be one Product Owner supported by a Junior Product Owner Option C : There must be a single Product Owner for each product Option D : There can be a single Product Owner across two products however a Single Product cannot have more than one Product Owner Correct Answer: C,D Explanation/Reference: Only One Product Backlog and Only One Product Owner can exist for a Product (Regular Scrum framework or in Nexus). Multiple Scrum Teams work on the Same Product Backlog. Thus, the same Product Owner would participate In the Nexus Sprint Planning sessions and Team Specific Sprint Planning sessions, as needed. Different Development Teams working on the same Product (in Nexus) can: •Have different Sprint Lengths. •Have different Scrum Masters. •Have only one Product Owner. •Have only one Product Backlog. A Product owner can act as Product Owner for more than one Products however this Is not recommended. QUESTION: 14

14. 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) Option 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. Option B : During Nexus Sprint Planning, ensure that all Scrum Teams understand the Nexus Sprint Goal. Option 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. Option D : During Nexus Sprint Planning, ask each Scrum Team to create a Sprint Goal that describes the purpose of the Sprint. Correct Answer: B

15. Explanation/Reference: 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. Download from Here: https://www.scrumdumps.com/SPS-exam-questions QUESTION: 15 What is the purpose of the 2nd part of Nexus Sprint Retrospective? Option A : Each Scrum Team holds their own Sprint Retrospective Option B : To discuss what went well during the Sprint Option C : To identify the one item teams should discuss during their individual Sprint Retrospective Option D : To identity issues that impact multiple teams Correct Answer: A

16. Explanation/Reference: The Retrospective consists of three parts: Part 1: Nexus Retrospective: Representatives from all the Scrum teams meet to Identify issues that have impacted more than a single Scrum team. The purpose is to make shared issues transparent to all Scrum Teams. Part 2: Individual Scrum Team Sprint Retrospectives: Each Scrum Team holds their own Sprint Retrospective as described in the Scrum framework. They can use Issues raised from the Nexus Retrospective as input to their team discussions. The individual Scrum Teams should form actions to address these issues during their individual Scrum Team Sprint Retrospectives. Part 3: Synchronize: Third part is an opportunity for appropriate representatives from the Scrum Teams to meet again and agree on how to visualize and track the identified actions. A Nexus consists of multiple cross-functional Scrum Teams working together to deliver a potentially releasable Integrated increment by the end of each Sprint. Download from Here: https://www.scrumdumps.com/SPS-exam-questions