SPS Free Exam Questions and Answers PDF Updated on Dec-2024
Latest SPS Exam Dumps Recently Updated 204 Questions
NEW QUESTION # 55
Nexus Sprint Goal replaces the Individual Teams' Sprint Goal. True or False?
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 56
Select all the true statements about Nexus.
- A. There should be separate Product Owner per team
- B. There is always one Product backlog in a Nexus
- C. There is always one Product Owner in a Nexus
- D. There is always one Scrum Master in a Nexus
Answer: B,C
NEW QUESTION # 57
How often should the Nexus Sprint Backlog be adjusted?
- A. Only during Sprint Planning
- B. Once a week
- C. At least every Nexus Daily Scrum
Answer: C
NEW QUESTION # 58
Nexus Integration team has defined a Definition of Done with 5 point criteria. One of the Sprint Team, want to use only 3 of them for their team's Definition of Done. Is this allowed?
- A. Yes
- B. No
Answer: B
NEW QUESTION # 59
Who should step in to resolve integration issues?
- A. Product Owner
- B. Nexus Integration Team
- C. Scrum Master
- D. Individual Team
Answer: B
NEW QUESTION # 60
What is the output of the Cross-Team Refinement event?
- A. Refined Product Backlog
- B. Refined Sprint Backlog
- C. Updated team structure
- D. Nexus Sprint Goal
Answer: A
NEW QUESTION # 61
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 many code conflicts while integration
- B. It will save Nexus members time
- C. There may be too little time to resolve integration issues
- D. Integrated Increment may not be available in time
Answer: A,C,D
NEW QUESTION # 62
All the development team members need not attend Nexus Daily Scrum. True or False?
- A. FALSE
- B. TRUE
Answer: B
NEW QUESTION # 63
What is the purpose of Nexus Integration Team?
- A. To own the Product Backlog
- B. To coach and guide the Scrum Teams to improve their ability to produce an increment
- C. To ensure that a done Integrated Increment is produced at least once a Sprint
- D. To do the integration work
Answer: B,C
NEW QUESTION # 64
Select two correct statements about the Scrum Master in Nexus Integration Team.
- A. The NIT Scrum Master must coach the other NIT members to become self-organizing
- B. The Scrum Master of an individual team can act as a Scrum Master in NIT
- C. The same person can act as a Scrum Master for many Scrum Teams in a Nexus
- D. The NIT Scrum Master must be a Scrum Master for at least one of the Scrum Teams
Answer: B,C
NEW QUESTION # 65
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 sponsor will lose if the project fails
- D. The money spent on the project so far
Answer: A
NEW QUESTION # 66
A Nexus Daily Scrum:
(choose the best two answers)
- A. Is only for the Nexus Integration Team to plan their work for the next 24-hours.
- B. Provides a single meeting where all Scrum Teams can update the Sprint Backlog.
- C. Is the same as a Scrum-of-Scrums.
- D. Is an opportunity to make integration issues transparent.
- E. Provides input into each Scrum Team's individual Daily Scrums to help them better plan their days work.
Answer: D,E
Explanation:
The best answers for this question are:
C). Provides input into each Scrum Team's individual Daily Scrums to help them better plan their days work. This answer is correct because the Nexus Daily Scrum is an event that helps the Scrum Teams in a Nexus to coordinate their work and identify any integration issues or dependencies that may affect their progress toward the Nexus Sprint Goal. The appropriate representatives from each Scrum Team attend the Nexus Daily Scrum and share relevant information and feedback that can help their teams plan their work for the next 24 hours 112233.
E). Is an opportunity to make integration issues transparent. This answer is also correct because the Nexus Daily Scrum is an event that enables the Scrum Teams in a Nexus to inspect the current state of the Integrated Increment and to make any integration issues or newly discovered cross-team dependencies transparent. The Nexus Daily Scrum also provides a forum for the Scrum Teams to collaborate and resolve any integration challenges or impediments that may arise during the Sprint 112244.
The other answers are not correct for the following reasons:
A). Provides a single meeting where all Scrum Teams can update the Sprint Backlog. This answer is not accurate because the Nexus Daily Scrum is not a meeting where all Scrum Teams update the Sprint Backlog, but rather an event where appropriate representatives from each Scrum Team inspect the Integrated Increment and identify integration issues or dependencies. The Sprint Backlog is updated by each Scrum Team during their own Daily Scrum, which is a separate event from the Nexus Daily Scrum 1155.
B). Is the same as a Scrum-of-Scrums. This answer is not true because the Nexus Daily Scrum is not the same as a Scrum-of-Scrums, which is a common practice for coordinating multiple Scrum Teams that is not part of the Scrum framework. The Nexus Daily Scrum is a specific event defined by the Nexus framework, which is a minimal extension of Scrum that enables multiple Scrum Teams to work together on a single product. The Nexus Daily Scrum has a clear purpose, structure, and outcome that differs from a Scrum-of-Scrums 112233.
D). Is only for the Nexus Integration Team to plan their work for the next 24-hours. This answer is not correct because the Nexus Daily Scrum is not only for the Nexus Integration Team, but also for the appropriate representatives from each Scrum Team in the Nexus. The Nexus Integration Team is a special Scrum Team that facilitates the integration and delivery of the work done by the other Scrum Teams, but it does not plan the work for them. The Nexus Daily Scrum is an event that helps all the Scrum Teams in the Nexus to coordinate their work and identify any integration issues or dependencies 1155.
NEW QUESTION # 67
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. 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.
- B. 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.
- C. Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event.
Discover, document, and resolve dependencies during this time. - D. Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve the dependencies.
Answer: A,B
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 # 68
Who is accountable for a releasable integrated Product being delivered at least once at the end of every Sprint?
- A. Product Owner
- B. Nexus Integration Team
- C. Scrum Master
- D. Every Team member
Answer: B
NEW QUESTION # 69
Select two correct statements about Scrum of Scrums and Nexus Daily Scrum?
- A. Scrum of Scrums is held before the individual teams' Daily Scrum
- B. Nexus Daily Scrum is held prior to the individual teams' Daily Scrum
- C. Nexus Daily Scrum is held after the individual teams' Daily Scrum
- D. Scrum of Scrums is held after the individual teams' Daily Scrum
Answer: B,D
NEW QUESTION # 70
What is true about Nexus Daily Scrum? Select all that apply.
- A. It helps individual teams to plan their work based on the latest cross-team issues and dependencies
- B. It is an optional event in Nexus
- C. It is held before teams' Daily Scrum
- D. It is to make integration issues transparent
Answer: A,C,D
NEW QUESTION # 71
The Nexus Team has failed to meet the Nexus Sprint Goal for two sprints in a row.
What are the possible reasons for this? (Select two best answers)
- A. Developers are struggling to integrate their work
- B. Nexus Integration Team is not coordinating the work among the developers
- C. There is technical debt in the product
- D. Definition of Done has too stringent
Answer: A,C
NEW QUESTION # 72
Select two true statements about Product Backlog Tree map.
- A. The colour or shading represents the completeness
- B. The sizes of the boxes represent the size of a Product Backlog item
- C. It is a chart which looks like a tree
- D. It is a tool to show the dependency between the Product Backlog items
Answer: A,B
NEW QUESTION # 73
Who are the mandatory members of Nexus Integration Team?
- A. Business Analyst
- B. Product Owner
- C. Integration Specialist
- D. Scrum Master
Answer: B,D
NEW QUESTION # 74
What is the purpose of Nexus Sprint Retrospective?
(choose the best answer)
- A. To complement the Scrum Teams' Sprint Retrospectives by using bottom-up intelligence to focus on issues that affect the Nexus as a whole.
- B. Plan ways to increase quality and effectiveness across the whole Nexus.
- C. All of the above.
- D. To inspect how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done.
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 # 75
What is true about Product Owner's accountability in Nexus? Select all that apply.
- A. Accountability of a product delivery shifts to Nexus Integration Team
- B. Scope of work increases
- C. A second Product Owner is needed
- D. Product Owner's accountability does not change from Scrum
Answer: B,D
NEW QUESTION # 76
Which events are present and mandatory in Nexus but not in Scrum? Select all that apply. Daily Scrum Sprint Retrospective Sprint Review Cross-Team Refinement (Correct) Nexus Sprint Planning (Correct)
Answer:
Explanation:
Nexus has five additional Events: Cross-Team Refinement, Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review, and Nexus Sprint Retrospective.
NEW QUESTION # 77
As part of the Nexus Sprint Retrospective, the team should address if there is technical debt in the product. True or False?
- A. FALSE
- B. TRUE
Answer: B
NEW QUESTION # 78
Which are the three valid questions that can be discussed during Nexus Daily Scrum?
- A. What did I do yesterday towards Sprint Goal?
- B. Was the previous day's work successfully integrated?
Answer: B
NEW QUESTION # 79
......
The SPS certification exam covers a wide range of topics related to scaling Scrum, including how to implement and manage Scrum across multiple teams, how to integrate Scrum with other frameworks, and how to use metrics and data to evaluate team performance. Candidates must demonstrate their understanding of these concepts by passing a rigorous exam that tests their knowledge and skills. Upon passing the exam, candidates receive the SPS certification, which demonstrates their expertise in scaling Scrum and their commitment to continuous learning and improvement.
Scrum SPS (Certified Scaled Professional Scrum) Certification Exam is a certification program designed for individuals who are looking to demonstrate their expertise in scaling Scrum across multiple teams and organizations. Certified Scaled Professional Scrum (SPS) certification is offered by Scrum.org, which is a leading global organization in the field of Scrum and Agile methodologies. The Scrum SPS Certification Exam is a comprehensive and challenging exam that requires candidates to have a deep understanding of the principles and practices of scaling Scrum.
Scrum SPS Real 2024 Braindumps Mock Exam Dumps: https://dumpspdf.free4torrent.com/SPS-valid-dumps-torrent.html