2024年最新の本日更新された最新のSPSのPDFにはSPSテスト限定無料！ [Q74-Q90]

2024年最新の本日更新された最新のSPSのPDFにはSPSテスト限定無料！

完全版最新の問題集PDFで最新SPS試験問題と解答

Scrum SPS（認定スケールドプロフェッショナルスクラム）認定試験は、スケールドスクラムプロジェクトの実装と管理に関する候補者の知識と専門知識をテストするために設計された、世界的に認知された認定プログラムです。この認定は、スクラム方法論と実践の権威であるScrum.orgによって提供されています。SPS認定は、大規模なスクラムプロジェクトに関与しており、そのようなプロジェクトを管理するための知識とスキルを向上させたいプロフェッショナルに最適です。

 

質問 # 74
Which statements best describe a Nexus Sprint Review?
(choose the best two answers)

• A. It is a container for each individual Scrum Team's Sprint Review.
• B. It is when individual Scrum Teams demo their work.
• C. It replaces individual Scrum Team Sprint Reviews.
• D. It provides feedback on the Integrated Increment.

正解：C、D

解説：
The Nexus Sprint Review is an event that occurs at the end of the Sprint where the Nexus, which is a group of approximately three to nine Scrum Teams working on the same product, presents the Integrated Increment to the stakeholders and collects feedback 12. The Integrated Increment is the combined work of all the Scrum Teams in the Nexus that meets the Definition of Done and the Nexus Sprint Goal 1. The purpose of the Nexus Sprint Review is to inspect the Integrated Increment and adapt the Product Backlog based on new learnings 1. Therefore, statement A is correct.
The Nexus Sprint Review replaces individual Scrum Team Sprint Reviews because the focus is on the entire Integrated Increment rather than the work of each team 12. The Nexus Sprint Review is not a container for each individual Scrum Team's Sprint Review, nor is it when individual Scrum Teams demo their work. These statements imply that the Nexus Sprint Review is a collection of separate Sprint Reviews, which is not the case. The Nexus Sprint Review is a single event that involves all the Scrum Teams and stakeholders in the Nexus 12. Therefore, statement B is also correct, and statements C and D are incorrect.

質問 # 75
Can a specialist outside of Nexus join Nexus Integration Team? Yes or No?

• A. No
• B. Yes

正解：B

質問 # 76
What does not happen during the Nexus Sprint Retrospective?

• A. Nexus team may revise their Definition of done
• B. Nexus meets to identify the issues that affected multiple teams
• C. Nexus discusses and decides on how to visualize and track the identified actions
• D. Individual teams conduct their own Scrum of Scrums

正解：D

質問 # 77
What is the recommended number of teams per Nexus?

• A. 3 to 9
• B. 4 to 10
• C. 3 to 12
• D. 2 to 5

正解：A

質問 # 78
Multiple teams on a Nexus are working on the same code and there are lot of conflicts during the code merge. This problem can be avoided using Trunk-based development. True or False?

• A. FALSE
• B. TRUE

正解：B

質問 # 79
Who is accountable for a releasable integrated Product being delivered at least once at the end of every Sprint?

• A. Scrum Master
• B. Product Owner
• C. Every Team member
• D. Nexus Integration Team

正解：D

質問 # 80
What is true about Nexus Sprint Goal? Select all that apply.

• A. Every Nexus member should understand the Nexus Sprint Goal and should work towards achieving it
• B. It replaces the Sprint Goal of individual team
• C. It is the objective for the Sprint
• D. It is the sum of all the work and Sprint Goals of the Scrum Teams within the Nexus

正解：A、C、D

質問 # 81
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)

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

正解：C

解説：
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.

質問 # 82
When compared to Scrum, which additional artifact does Nexus have?

• A. Nexus Product Backlog
• B. Definition of Done
• C. Nexus Sprint Backlog
• D. Nexus Team Backlog

正解：C

質問 # 83
Scrum Master of one of the team can also act as a Scrum Master in Nexus Integration Team. True or False?

• A. FALSE
• B. TRUE

正解：B

質問 # 84
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. Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve the dependencies.
• B. Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event.
  Discover, document, and resolve dependencies during this time.
• C. 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.
• D. 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、D

解説：
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.

質問 # 85
How does Technical Debt impact the product?

• A. It'll take longer to solve the existing bugs
• B. It'll get difficult to add new features
• C. It leads to false assumptions about the state of the product
• D. It'll get difficult to get additional funding for the product

正解：A、B、C

質問 # 86
What is the purpose of Nexus Sprint Planning? Select two best answers

• A. Create a plan for upcoming Sprint
• B. Ensure all teams have enough work
• C. Coordinate the activities between the Scrum teams
• D. Finalize the product's architecture

正解：A、C

質問 # 87
Who participates in Nexus Daily Scrum?

• A. Appropriate representatives from individual Scrum Teams
• B. Scrum Masters & Team leads
• C. Product Owner, Scrum Master & Integration team
• D. All the Nexus Members

正解：A

質問 # 88
From the list below, what is the most important concern for multiple Scrum Teams when they are working from the same Product Backlog?
(choose the best answer)

• A. Minimizing dependencies between teams.
• B. Meeting original scope projections.
• C. Making sure there is enough work for everyone on every team.
• D. Clear definition of requirements.

正解：A

解説：
The most important concern for multiple Scrum Teams when they are working from the same Product Backlog is minimizing dependencies between teams. Dependencies are the relationships or constraints that exist between the work items or the teams that affect the delivery of the product 11. Dependencies can cause delays, rework, waste, and quality issues, and they can reduce the agility and value delivery of the Scrum Teams 2233. Therefore, minimizing dependencies between teams is a critical concern for scaling Scrum effectively 112233.
Statement A is incorrect because meeting original scope projections is not a primary concern for multiple Scrum Teams working from the same Product Backlog. Scrum does not prescribe a fixed scope for the product, but rather embraces change and adaptation based on feedback and learning 44. The Product Backlog is a dynamic and emergent artifact that reflects the current understanding of the product vision, goals, and requirements 44. The Product Owner is responsible for managing the Product Backlog and ordering the items in a way that maximizes the value of the product and the work of the Scrum Teams 44. Therefore, meeting original scope projections is not a relevant or realistic concern for scaling Scrum.
Statement C is incorrect because clear definition of requirements is not the most important concern for multiple Scrum Teams working from the same Product Backlog. While having clear and well-defined requirements is desirable and beneficial for the Scrum Teams, it is not always possible or necessary in a complex and uncertain environment 44. Scrum does not require detailed upfront specifications, but rather encourages empirical discovery and experimentation through frequent delivery and feedback 44. The Product Backlog items are refined and clarified by the Product Owner and the Developers as they collaborate and learn more about the product and the users 44. Therefore, clear definition of requirements is not the most critical concern for scaling Scrum.
Statement D is incorrect because making sure there is enough work for everyone on every team is not the most important concern for multiple Scrum Teams working from the same Product Backlog. Scrum does not focus on maximizing the utilization of the Scrum Team members, but rather on maximizing the value of the product and the work of the Scrum Teams 44. The Scrum Teams are self-organizing and cross-functional, which means they can decide how to do their work and have all the skills needed to create a potentially releasable Increment 44. The Scrum Teams pull work from the Product Backlog in agreement with the Product Owner, and they commit to delivering an Integrated Increment that meets the Nexus Sprint Goal 1144. Therefore, making sure there is enough work for everyone on every team is not the most essential concern for scaling Scrum.

質問 # 89
Select two correct statements about the Scrum Master in Nexus Integration Team.

• A. The Scrum Master of an individual team can act as a Scrum Master in NIT
• B. The NIT Scrum Master must be a Scrum Master for at least one of the Scrum Teams
• C. The same person can act as a Scrum Master for many Scrum Teams in a Nexus
• D. The NIT Scrum Master must coach the other NIT members to become self-organizing

正解：A、C

質問 # 90
......

無料SPS試験問題SPS実際の無料試験問題：https://www.passtest.jp/Scrum/SPS-shiken.html

無料SPS試験を簡単に100%合格できる試験問題集：https://drive.google.com/open?id=1VXL19xKfepxtdtG8a9xCem0y97iI5Q-P