2024 Valid SPS Real Exam Questions (Updated) 100% Dumps & Practice Exam
[UPDATED 2024] Scrum SPS Questions Prepare with Free Demo of PDF
Scrum SPS Exam is intended for individuals who have already achieved the Scrum Master (CSM) or Product Owner (CSPO) certification and have experience working with Scrum in large-scale environments. SPS exam assesses candidates' knowledge of the Nexus Framework, which is a framework for scaling Scrum and managing dependencies across multiple teams. It also evaluates their ability to apply Scrum principles, practices, and values in complex and scaled situations.
NEW QUESTION # 78
Which is the event to make integration issues Transparent?
- A. NIT Meeting
- B. Nexus Daily Scrum
- C. Nexus Sprint Review
- D. Nexus Sprint Retrospective
Answer: B
NEW QUESTION # 79
Stakeholders are interested in understanding the progress of Nexus without having to get into too many details.
Which tool can achieve this?
- A. Product Backlog Tree map
- B. Nexus Sprint Backlog
- C. Product Backlog
- D. Burndown chart
Answer: A
NEW QUESTION # 80
Teams want to integrate the code only before the Nexus Sprint Review.
What can be the result of this? Select all that apply.
- A. There may be too little time to resolve integration issues
- B. Integrated Increment may not be available in time
- C. There may be too many code conflicts while integration
- D. It will save Nexus members time
Answer: A,B,C
NEW QUESTION # 81
Nexus Daily Scrum replaces the individual team's Daily Scrum. True or False?
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 82
Definition of Done is always same for Nexus and all individual Scrum Teams. True or False?
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 83
Can a Product Owner be part of Nexus Integration Team? Yes or No?
- A. No
- B. Yes
Answer: B
NEW QUESTION # 84
During Nexus Daily Scrum, a new issue has surfaced which can be resolved without outside help. Who should resolve the issue?
- A. Nexus Daily Scrum Members
- B. Scrum Team members
- C. Scrum Master
- D. Nexus Integration Team members
Answer: B
NEW QUESTION # 85
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.
Which of the following two strategies would be most effective in dealing with their dependencies?
(choose the best two answers)
- A. During Nexus Sprint Planning, have appropriate representatives from each team in the Nexus briefly meet to discuss dependencies for the upcoming Sprint. This conversation will help their individual team's Sprint Planning.
- B. Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve the dependencies.
- C. Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event.
Discover, document, and resolve dependencies during this time. - D. Discover and document dependent work during Cross-Team Refinement of the Product Backlog, so teams are aware of dependencies before Nexus Sprint Planning. This will allow Nexus Sprint Planning to focus on resolving dependencies for the upcoming Sprint.
Answer: A,D
Explanation:
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 events in the Nexus framework is the Nexus Sprint Planning, which is used to coordinate the activities of all teams in the Nexus for a single Sprint 11.
In Scenario B, the Nexus is developing a complex product with different parts that only certain teams can work on. There are also 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 teams. Dependencies are the relationships between the work items that affect the order, timing, or outcome of the work 22. Dependencies can cause delays, rework, waste, and lower quality 22. Therefore, it is important to identify and resolve dependencies as early and as often as possible 22.
The two strategies that would be most effective in dealing with the dependencies are:
Discover and document dependent work during Cross-Team Refinement of the Product Backlog, so teams are aware of dependencies before Nexus Sprint Planning. This will allow Nexus Sprint Planning to focus on resolving dependencies for the upcoming Sprint. This is answer A. This is a valid strategy because Cross-Team Refinement is an activity where representatives from each team in the Nexus meet to decompose and refine the Product Backlog items into smaller pieces of work that can be delivered by a single team or multiple teams 11. By doing this, the teams can discover and document the dependent work that needs to be done by other teams or external parties 11. This will help the teams to be aware of the dependencies before the Nexus Sprint Planning and to prepare for them 11. This will also allow the Nexus Sprint Planning to focus on resolving the dependencies for the upcoming Sprint, rather than spending time on identifying them 11.
During Nexus Sprint Planning, have appropriate representatives from each team in the Nexus briefly meet to discuss dependencies for the upcoming Sprint. This conversation will help their individual team's Sprint Planning. This is answer C. This is a valid strategy because Nexus Sprint Planning is an event where the Nexus, consisting of the Product Owner and appropriate representatives from each team, meet to plan the Sprint 11. The purpose of Nexus Sprint Planning is to coordinate the activities of all teams in the Nexus for a single Sprint 11. The result of Nexus Sprint Planning is a Nexus Sprint Goal that aligns with the Product Goal and a Nexus Sprint Backlog that contains the work to be done by the teams to achieve the Nexus Sprint Goal 11. During Nexus Sprint Planning, the representatives from each team can briefly meet to discuss the dependencies for the upcoming Sprint and how to resolve them 11. This conversation will help their individual team's Sprint Planning, where they can create their own team Sprint Goal and team Sprint Backlog that support the Nexus Sprint Goal and the Nexus Sprint Backlog 11.
The other two answers are not correct because:
Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve the dependencies. This is answer B. This is not a valid strategy because the Nexus Integration Team is not the owner or the controller of the Nexus Sprint Backlog. 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 1[1][5]. The Nexus Integration Team facilitates the Nexus Sprint Planning, but does not order or dictate the Nexus Sprint Backlog 1[1][5]. The Nexus Sprint Backlog is owned and managed by the Nexus, not by the Nexus Integration Team 1[1][5]. The Nexus Integration Team helps the teams to identify and resolve the dependencies, but does not control or impose them 1[1][5].
Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event. Discover, document, and resolve dependencies during this time. This is answer D. This is not a valid strategy because gathering all people in the Nexus into a 48-hour Nexus Sprint Planning event is not feasible, efficient, or effective. The Nexus Sprint Planning is not meant to be a long and exhaustive event that involves all people in the Nexus 11. The Nexus Sprint Planning is meant to be a short and focused event that involves only the Product Owner and appropriate representatives from each team in the Nexus 11. The Nexus Sprint Planning is not meant to be the only time to discover, document, and resolve dependencies 11. The Nexus Sprint Planning is meant to be the time to coordinate the activities of the teams for the upcoming Sprint and to create a Nexus Sprint Goal and a Nexus Sprint Backlog 11. The discovery, documentation, and resolution of dependencies should be done continuously throughout the Sprint, not only during the Nexus Sprint Planning 11.
NEW QUESTION # 86
A five team Nexus is developing a purchase order application. There are several dependencies and Nexus faced a lot of challenges in managing them.
How should they conduct their Nexus Sprint Planning to minimize such difficulties due to the dependencies?
- A. Bring in specialists from outside Nexus to guide the Developers
- B. Utilize refinement sessions to highlight the dependencies and visualize them for all the developers to see during the Nexus Sprint Planning
- C. Nexus Integration Team should assign the work since they are accountable for managing the dependencies
- D. Nexus should hold separate Sprint Planning for each team
Answer: B
NEW QUESTION # 87
Which is NOT a valid artifact in Nexus?
- A. Nexus Sprint Backlog
- B. Integrated Increment
- C. Definition of Done
- D. Product Backlog
Answer: C
NEW QUESTION # 88
Select the valid commitments in Nexus
- A. Nexus Sprint Goal
- B. Definition of Done
- C. Product Goal
- D. Integrated increment
Answer: A,B,C
NEW QUESTION # 89
Requirement number 22 is being worked by Team C in a Nexus. Stakeholders are expecting this key feature to be demonstrated in the upcoming Nexus Sprint Review. Just 2 days prior to the review, the team identified a defect in one of the testing scenarios. It has been determined that Team C doesn't have the skillset to resolve the defect in such a short time. Select two BEST possible options the Nexus team can take to resolve the situation.
- A. Postpone the requirement to next Sprint
- B. NIT Scrum Master can look for specialists outside the Nexus who have the skills to resolve the issue
- C. If a resource in other teams in Nexus has the skillset to resolve the issue, they should be brought in to NIT and the whole NIT can work on the issue
- D. Find the resources who have the skills and extend the Sprint to provide sufficient time to resolve the issue
Answer: B,C
NEW QUESTION # 90
During the first 2 Sprints of a product development, Team A's velocity is 10 points whereas Team B's velocity is 20 points.
Which team is performing better?
- A. Team A is performing better
- B. Team's performance cannot be determined by comparing the velocity of another team
- C. Team B is performing better
Answer: B
NEW QUESTION # 91
Development Teams may have different length of Sprints as long as the Sprint boundaries align. True or False?
- A. FALSE
- B. TRUE
Answer: B
NEW QUESTION # 92
What is the purpose of Nexus Sprint Retrospective?
(choose the best answer)
- A. Plan ways to increase quality and effectiveness across the whole Nexus.
- B. To inspect how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done.
- C. All of the above.
- D. To complement the Scrum Teams' Sprint Retrospectives by using bottom-up intelligence to focus on issues that affect the Nexus as a whole.
Answer: C
Explanation:
The purpose of Nexus Sprint Retrospective is all of the above, meaning that it aims to:
Plan ways to increase quality and effectiveness across the whole Nexus. The Nexus Sprint Retrospective is a formal opportunity for a Nexus to inspect and adapt itself and create a plan for improvements to be enacted during the next Sprint to ensure continuous improvement 11.
To inspect how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done. The Nexus Sprint Retrospective follows the same format and principles as the Scrum Team Sprint Retrospective, but at a larger scale. The Nexus inspects the aspects of the product development that affect the Nexus as a whole, such as the collaboration, the integration, the dependencies, the quality, and the value 22.
To complement the Scrum Teams' Sprint Retrospectives by using bottom-up intelligence to focus on issues that affect the Nexus as a whole. The Nexus Sprint Retrospective does not replace the Scrum Teams' Sprint Retrospectives, but rather enhances them by using the input and output from the individual teams to identify and address the shared challenges and opportunities 33.
NEW QUESTION # 93
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)
- A. There should be six Product Owners, one for each Scrum Team.
- B. There should be six Product Owners, one of whom is chief Product Owner.
- C. Each Scrum Team should have a separate Product Backlog.
- D. There should be only one Product Owner who is accountable for the success of the product.
- E. The product has one Product Backlog.
Answer: D,E
Explanation:
When six new Scrum Teams are working on one product, they should form a Nexus, which is a framework for scaling Scrum 11. 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.
NEW QUESTION # 94
What is the technical debt?
- A. Technical Debt may represent additional cost a team may incur due to poor design of code
- B. The money invested on the infrastructure of the project
- C. The money spent on the project so far
- D. The money sponsor will lose if the project fails
Answer: A
NEW QUESTION # 95
5 teams are working in a Nexus to develop a new product. So far, their Sprint length has been 2 weeks. Going forward, work done by Team C has high risk and uncertain aspects.
What should the team do to ensure success?
- A. Reduce the Sprint length to one week for Team C
- B. Increase the Sprint length to four weeks for Team C
- C. Reduce the Sprint length of all the teams to one week
- D. Add additional members to Team C
Answer: A
NEW QUESTION # 96
During the first Nexus Daily Scrum, members realize they need to build a common tool to enable continuous integration.
Which should be the next steps?
- A. This requirement should be discussed with Product Owner
- B. This requirement to build continuous integration tool should be added to Product Backlog
- C. This doesn't qualify to be a Product Backlog item. Teams must add it to Nexus Sprint Backlog
- D. Team should request Nexus Integration Team to perform the work required
Answer: A,B
NEW QUESTION # 97
Adding additional resources to Nexus will result in the value that is being delivered. True or False?
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 98
True or False: All Scrum Team members must attend the Nexus Daily Scrum.
- A. True
- B. False
Answer: B
Explanation:
The answer is false because not all Scrum Team members are required to attend the Nexus Daily Scrum. According to the Online Nexus Guide1, the Nexus Daily Scrum is an event for appropriate representatives from individual Scrum Teams to inspect the current state of the Integrated Increment and to identify integration issues or newly discovered cross-team dependencies. The appropriate representatives are those who can best collaborate and communicate the progress and impediments of their Scrum Teams, and who can make and influence decisions regarding the integration and delivery of the product. The number and selection of the representatives may vary depending on the context and needs of the Nexus 234. The Nexus Daily Scrum does not replace the Daily Scrum of each Scrum Team, which is still held by all the Developers of the team to plan their work for the day 5.
NEW QUESTION # 99
Who is an appropriate person to represent an individual team in Nexus Daily Scrum?
- A. Customer
- B. A developer working on an item which has cross team dependencies
- C. Scrum Master
- D. Product Owner
Answer: B
NEW QUESTION # 100
......
Scrum SPS certification program and the Certified Scaled Professional Scrum (SPS) Exam are essential for professionals who want to master the skills required to scale Scrum in their organizations. It is a rigorous certification program designed by Scrum.org, recognized globally, and highly valued by organizations that are looking to scale their Scrum practices. Passing the exam requires a deep understanding of Scrum principles, practices, and their application in a scaled environment, and it is ideal for professionals who are already certified in Scrum and have experience working in a Scrum environment.
SPS Deluxe Study Guide with Online Test Engine: https://actualtests.vceengine.com/SPS-vce-test-engine.html
