
2024 Realistic SPS Dumps are Available for Instant Access
Download Exam SPS Practice Test Questions with 100% Verified Answers
NEW QUESTION # 36
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 practices could this Nexus try in order to conduct Nexus Sprint Planning more effectively?
(choose the best two answers)
- A. Ensure all Scrum Teams and outside experts are available during the Nexus Sprint Planning event and have a way of quickly communicating with each other.
They should try to be together in the same room or use technology that makes it seem as if they are in the same room. - B. Plan one Scrum Team's Sprint at a time before moving on to the next team. This way you can account for time zone differences and can communicate dependencies across all teams.
- C. Visualize the known dependencies in the Product Backlog for all to see. As Scrum Teams select work for the Sprint, they can easily check for any dependent work and communicate with other teams.
- D. Have the Nexus Integration Team select the work for each of the individual Scrum Teams. This allows the Nexus Integration Team to control the dependencies.
Answer: A,C
Explanation:
The purpose of Nexus Sprint Planning is to coordinate the activities of all Scrum Teams within a Nexus for a single Sprint 1. To do this effectively, the Nexus needs to have a clear understanding of the dependencies between the teams and the work items, and to communicate and collaborate with each other and any outside experts as needed. Therefore, the best practices for this Nexus are:
A). Ensure all Scrum Teams and outside experts are available during the Nexus Sprint Planning event and have a way of quickly communicating with each other. They should try to be together in the same room or use technology that makes it seem as if they are in the same room. This practice enables the Nexus to have a shared understanding of the Product Backlog, the Product Goal, and the Nexus Sprint Goal, and to resolve any issues or questions that may arise during the planning. It also allows the Nexus to leverage the expertise of the outside specialists who are required for some of the work 2.
D). Visualize the known dependencies in the Product Backlog for all to see. As Scrum Teams select work for the Sprint, they can easily check for any dependent work and communicate with other teams. This practice helps the Nexus to identify and manage the dependencies between the teams and the work items, and to optimize the flow of value delivery. It also supports transparency and alignment within the Nexus 3.
The other two practices are not effective for this Nexus because:
B). Plan one Scrum Team's Sprint at a time before moving on to the next team. This way you can account for time zone differences and can communicate dependencies across all teams. This practice is not optimal because it does not allow the Nexus to plan the Sprint as a whole, and to adjust the work allocation and sequence based on the dependencies and the Nexus Sprint Goal. It also creates delays and inefficiencies in the planning process, and reduces the collaboration and feedback opportunities among the teams 4.
C). Have the Nexus Integration Team select the work for each of the individual Scrum Teams. This allows the Nexus Integration Team to control the dependencies. This practice is not consistent with the Nexus framework, which states that the Nexus Integration Team does not select the work for the Scrum Teams, but rather facilitates the integration and delivery of the work done by the Scrum Teams. It also undermines the self-organization and empowerment of the Scrum Teams, and reduces their ownership and accountability for the work 1.
NEW QUESTION # 37
Product Owner and Scrum Master come to a conclusion that they will not be able to show all the features in the integrated increment to the customers due to time, location, geographical issues.
What is the best approach?
- A. Select the most important features and show them
- B. Extend the Sprint Review time box so that all features can be shown
- C. Only the features which are shown to the customer must be released
Answer: A
NEW QUESTION # 38
A Nexus has 5 teams. Kevin and Oscar are the Scrum Masters of Team A and B respectively. They had technical experience in their previous jobs. While forming the NIT, Product Owner felt that it would be ideal to have both of them.
Is it allowed to have 2 individual teams' Scrum Masters in NIT?
- A. Yes. Even though they are the Scrum Masters of individual teams, they can act as members in NIT
- B. Yes, but only one of them can be a NIT Scrum Master
- C. No, NIT cannot have Scrum Masters of individual teams
- D. Yes, but neither of them can ever take a role of NIT Scrum Master
Answer: A,B
NEW QUESTION # 39
Which statements best describe a Nexus Sprint Review?
(choose the best two answers)
- A. It replaces individual Scrum Team Sprint Reviews.
- B. It provides feedback on the Integrated Increment.
- C. It is a container for each individual Scrum Team's Sprint Review.
- D. It is when individual Scrum Teams demo their work.
Answer: A,B
Explanation:
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.
NEW QUESTION # 40
How many Scrum Masters can there be in Nexus?
- A. There is no need of Scrum Master in Nexus
- B. Max 1 Scrum Master per team
- C. Only one Scrum Master for whole Nexus
- D. Min 1 Scrum Master per team
Answer: B
NEW QUESTION # 41
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. Nexus should hold separate Sprint Planning for each team
- C. Nexus Integration Team should assign the work since they are accountable for managing the dependencies
- D. Utilize refinement sessions to highlight the dependencies and visualize them for all the developers to see during the Nexus Sprint Planning
Answer: D
NEW QUESTION # 42
Which event is present in Scrum but not in Nexus?
- A. Sprint Review
- B. Daily Scrum
- C. Sprint Retrospective
- D. Sprint Planning
Answer: A
NEW QUESTION # 43
True or False: A Nexus Integration Team is responsible for actually doing the integration work during the Sprint.
- A. True
- B. False
Answer: B
Explanation:
A Nexus Integration Team is not responsible for actually doing the integration work during the Sprint. 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. The Nexus Integration Team helps the Scrum Teams to coordinate, coach, and supervise the application of Nexus and the operation of Scrum, but it does not take over their work or accountability 33. Therefore, the statement is false.
NEW QUESTION # 44
Nexus Daily Scrum replaces the individual team's Daily Scrum. True or False?
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 45
Select the valid activities performed by the Nexus Integration Team
- A. Coach the developers on techniques and best practices
- B. Merging the individual teams' increment into integrated increment
- C. Developing tools that may help the developers in integrating their work
- D. Validate the work done by developers against the Definition of Done
Answer: A,C
NEW QUESTION # 46
Which event precedes Individual teams' Daily Scrum?
- A. Cross-Team Refinement
- B. Nexus Daily Scrum
- C. Nexus Sprint Backlog adjustment
- D. Nexus Sprint Planning
Answer: B
NEW QUESTION # 47
Changes to the core Scrum framework are needed to be successful with Scrum at large scale. True or False?
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 48
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 # 49
How does Technical Debt impact the product?
- A. It leads to false assumptions about the state of the product
- B. It'll take longer to solve the existing bugs
- C. It'll get difficult to get additional funding for the product
- D. It'll get difficult to add new features
Answer: A,B,D
NEW QUESTION # 50
Nexus Integration Team can step in and do some actual work in case of emergencies. True or False?
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 51
Select two correct statements about Scrum of Scrums and Nexus Daily Scrum?
- A. Scrum of Scrums is held after the individual teams' Daily Scrum
- B. Scrum of Scrums is held before the individual teams' Daily Scrum
- C. Nexus Daily Scrum is held prior to the individual teams' Daily Scrum
- D. Nexus Daily Scrum is held after the individual teams' Daily Scrum
Answer: A,C
NEW QUESTION # 52
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 Nexus Integration Team is lacking or nonexistent.
- B. There is no single Integrated Increment.
- C. The Sprint is too short.
- D. The Nexus has not yet reached the integration phase.
Answer: A,B
Explanation:
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.
NEW QUESTION # 53
A Nexus with five Scrum Teams has been created to build one product. Who has to coordinate the work with other teams in the Nexus?
- A. Lead Developer on a Team should coordinate with other teams
- B. Product Owner
- C. Scrum Master should teach the Developers that it is their responsibility to work with other teams
- D. Nexus Integration Team, because they are responsible for cross-team dependencies
Answer: C
NEW QUESTION # 54
Definition of Done is always same for Nexus and all individual Scrum Teams. True or False?
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 55
The Nexus Guide no longer prescribes the format of Nexus Sprint Retrospective. Is it still necessary to have individual teams' sprint retrospective?
- A. Yes
- B. No
Answer: A
NEW QUESTION # 56
Membership of the Nexus Integration Team remains same through out the product development. True or False?
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 57
All the Scrum Teams in a Nexus should have the same Sprint start date
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 58
......
Positive Aspects of Valid Dumps SPS Exam Dumps! : https://www.dumpsking.com/SPS-testking-dumps.html
