[2024年06月]更新のScrum SPS公式認定ガイドPDF
試験SPS Certified Scaled Professional Scrum (SPS)
Scrum SPS認定は、スクラムのスケールにおける熟練度を示す資格として、世界的に認知されています。この認定は、認定プロフェッショナルがスクラムのプラクティスを熟知し、大規模なソフトウェア開発プロジェクトを効果的に管理できることを雇用主に保証します。この認定は、プロフェッショナルにとって競争力のあるエッジを提供し、信頼性を高め、収益性を向上させることができます。
SPS試験は、スクラムトレーニングと認定の大手プロバイダーであるscrum.orgによって管理されています。 SPS試験を受けるには、候補者がプロのスクラムマスター（PSM）またはプロのスクラム製品所有者（PSPO）認定を完了している必要があります。試験は困難であり、候補者は、複雑な環境でのスクラムとその応用を深く理解することが期待されています。 SPS試験に合格した人は、スケーリングスクラムの専門知識のマークとしてグローバルに認識されている認定スケーリングプロフェッショナルスクラム（SPS）認定を獲得します。
質問 # 11
How many parts are in Nexus Sprint Retrospective?
- A. 0
- B. 1
- C. Depends on the Nexus team
- D. 2
正解：C
質問 # 12
Select two correct statements about the Scrum Master in Nexus Integration Team.
- A. The same person can act as a Scrum Master for many Scrum Teams in a Nexus
- B. The Scrum Master of an individual team can act as a Scrum Master in NIT
- C. The NIT Scrum Master must be a Scrum Master for at least one of the Scrum Teams
- D. The NIT Scrum Master must coach the other NIT members to become self-organizing
正解：A、B
質問 # 13
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)
- A. The Sprint is too short.
- B. The Nexus Integration Team is lacking or nonexistent.
- C. The Nexus has not yet reached the integration phase.
- D. There is no single Integrated Increment.
正解：B、D
解説：
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.
質問 # 14
Who coaches the individual Scrum Teams on the necessary skills required to produce DONE integrated increment?
- A. Self-organizing teams do not require coaching
- B. Product Owner
- C. Scrum Master
- D. Nexus Integration Team
正解：D
質問 # 15
What is the output of the Cross-Team Refinement event?
- A. Updated team structure
- B. Refined Sprint Backlog
- C. Nexus Sprint Goal
- D. Refined Product Backlog
正解：D
質問 # 16
Product Owner is responsible for Definition of Done in Nexus. True or False?
- A. TRUE
- B. FALSE
正解：B
質問 # 17
What should be done when one team is consistently performing better than the other teams?
- A. Release the low performing teams from the Nexus
- B. Changing team composition should be considered
- C. Assign low priority tasks to low performing teams
正解：B
質問 # 18
How should multiple Scrum Teams deliver a valuable and useful Increment in a Sprint?
(choose the best answer)
- A. Each Sprint, all Scrum Teams complete work that integrates with all of the other work from other Scrum Teams on the initiative.
- B. Functionality not integrated with the work of other Scrum Teams may be delivered as unintegrated Increments to demonstrate the value created by the Scrum Teams
- C. Each Scrum Team delivers done Increments of its own area of responsibility. These Increments are integrated into a whole product during stabilization prior to release.
- D. Each Scrum Team provides a unique done Increment that includes the team's added functionality.
正解：A
解説：
unable to completely integrate their Increments.
Explanation:
The best way for multiple Scrum Teams to deliver a valuable and useful Increment in a Sprint is to complete work that integrates with all of the other work from other Scrum Teams on the initiative. This means that the Scrum Teams collaborate and coordinate their work to produce a single Integrated Increment that meets the Definition of Done and the Product Goal. The Integrated Increment is the combined work of all the Scrum Teams that is potentially releasable and provides value to the customers and stakeholders 11.
The other options are not correct for the following reasons:
Each Scrum Team delivering done Increments of its own area of responsibility and integrating them into a whole product during stabilization prior to release is not a good idea, as it violates the Scrum principles and values. The Scrum Guide states that the Scrum Team delivers a product Increment that is usable and valuable at the end of every Sprint, not at the end of the release 22. Delaying the integration until the stabilization phase would compromise the transparency, the feedback, and the adaptability of the Scrum Teams.
Each Scrum Team providing a unique done Increment that includes the team's added functionality is not a good idea, as it does not ensure that the product Increment is integrated and consistent across the initiative. The Scrum Guide states that the product Increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints 22. If each Scrum Team provides a unique Increment, they may not be aligned with the Product Goal and the Definition of Done, and they may create conflicts or dependencies with other Scrum Teams.
Functionality not integrated with the work of other Scrum Teams being delivered as unintegrated Increments to demonstrate the value created by the Scrum Teams unable to completely integrate their Increments is not a good idea, as it does not ensure that the product Increment is done and valuable. The Scrum Guide states that the product Increment must be usable and meet the Definition of Done 22. If some functionality is not integrated with the work of other Scrum Teams, it may not be usable or valuable to the customers and stakeholders, and it may introduce technical debt or quality issues.
質問 # 19
During the Nexus Sprint Retrospective, it was discovered that a team has not been conducting their individual Daily Scrum's over the past few weeks. Who is accountable for ensuring the Nexus framework is understood and enacted?
- A. Product Owner
- B. Nexus Integration Team
- C. Scrum Master on the Nexus Integration Team
- D. Developers
正解：C
質問 # 20
3 teams are working in a Nexus on development of a mobile application that will support existing customers who were using only the website so far. They are half way through the backlog and their estimation techniques are mostly accurate. Each team's performance has been consistent. During Sprints 5 and 6, all the teams worked only on the backlog items related to the screens in the app. Their velocity was as follows: Team A (20,20), Team B (5,6) and Team C (18,16).
Is there a need to review the skill sets of Team B with respect to screen development and take necessary steps for their improvement?
- A. Yes
- B. No
正解：A
質問 # 21
Which statements best describe a Nexus Sprint Review?
(choose the best two answers)
- A. It provides feedback on the Integrated Increment.
- B. It replaces individual Scrum Team Sprint Reviews.
- C. It is a container for each individual Scrum Team's Sprint Review.
- D. It is when individual Scrum Teams demo their work.
正解：A、B
解説：
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.
質問 # 22
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 to make integration issues transparent
- C. It is an optional event in Nexus
- D. It is held before teams' Daily Scrum
正解：A、B、D
質問 # 23
Developers may also serve on the Nexus Integration Team. True or False?
- A. FALSE
- B. TRUE
正解：B
質問 # 24
Who is accountable for a releasable integrated Product being delivered at least once at the end of every Sprint?
- A. Product Owner
- B. Scrum Master
- C. Every Team member
- D. Nexus Integration Team
正解：D
質問 # 25
How many product backlogs should be maintained in a Nexus?
- A. One per team
- B. Depends on the product
- C. One
- D. Two per team
正解：C
質問 # 26
In a Nexus, it is agreed that the representatives from each team will participate in the Nexus Sprint Planning to select the Product backlog items for the sprint. They were struggling to find the items with fewer dependencies. There are especially three teams that have a lot of dependent work.
What should the Nexus do to avoid this problem going forward?
- A. Reorganize the teams that often have work with a lot of dependencies
- B. Increase the Cross-Team refinement activity duration
- C. Instruct the Nexus Integration Team to perform the product backlog refinement
- D. Merge the teams that often have work with a lot of dependencies
正解：B
質問 # 27
Nexus Sprint Goal replaces the Individual Teams' Sprint Goal. True or False?
- A. TRUE
- B. FALSE
正解：B
質問 # 28
Which are the valid artifacts in Nexus? Select all that apply.
- A. Sprint Backlog
- B. Nexus Sprint Backlog
- C. Product Backlog
- D. Integrated Increment
正解：A、B、C、D
質問 # 29
What is the purpose of Nexus Sprint Retrospective?
(choose the best answer)
- A. All of the above.
- B. Plan ways to increase quality and effectiveness across the whole Nexus.
- C. To complement the Scrum Teams' Sprint Retrospectives by using bottom-up intelligence to focus on issues that affect the Nexus as a whole.
- D. To inspect how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done.
正解：A
解説：
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.
質問 # 30
......
無料SPS試験問題集試験点数を伸ばそう：https://jp.fast2test.com/SPS-premium-file.html