Test Online Free Scrum SPS Exam Questions and Answers
Practice a live sample before buying full access. This page keeps the free SPS question set organized by page so visitors and search engines can reach the canonical -questions.html URL directly.
Why would a Nexus choose to have different Sprint length for the teams in a Sprint?
Answer: Explanation:
Sprint length is usually determined based on risk and uncertainty. When a team is working on riskier requirements, Sprint length is shorter to ensure frequent validation. Teams in a nexus need not have same Sprint length as long as Sprint boundaries align i.e. there is one common day where all the teams end their Sprint.
Question 2Selectable Answer
Which are the three valid questions that can be discussed during Nexus Daily Scrum?
Answer:
Question 3Selectable Answer
The Scrum teams in Nexus are struggling to create a DONE increment every Sprint. The scope is being adjusted often due to newly discovered dependencies and complications.
What could they do to increase the probability of producing an integrated increment for the next Sprint? Select two best answers
Answer: Explanation:
Cross-Team Refinement of the Product Backlog reduces or eliminates cross-team dependencies within a Nexus. The Product Backlog must be decomposed so that dependencies are transparent, identified across teams, and removed or minimized. It helps the Scrum Teams forecast which team will deliver which Product Backlog items and It identifies dependencies across those teams.
Question 4Selectable Answer
What is the recommended number of teams per Nexus?
Answer: Explanation:
3 to 9 Scrum teams are considered ideal for Nexus.
Question 5Selectable Answer
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)
Answer: Explanation:
Technical Debt impacts the product and team in several ways. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways. It leads to false assumptions about the current state of the systems specifically of an
increment being releasable at the end of a Sprint. Definition of Done is a commitment agreed by the Nexus team and all the work must adhere to it.
Question 6Selectable Answer
What should be done when one team is consistently performing better than the other teams?
Answer: Explanation:
Among the listed options, moving some of the team members from better performing teams to low performing teams can be very helpful in this situation.
Question 7Selectable Answer
Who are the mandatory members of Nexus Integration Team?
Answer: Explanation:
The Nexus Integration Team consists of Product Owner, Scrum Master, One or more Nexus Integration Team Members
Question 8Selectable Answer
How many additional events does Nexus have compared to Scrum?
Answer: Explanation:
Nexus has five additional Events: Cross-Team Refinement, Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review, and Nexus Sprint Retrospective.
Question 9Selectable Answer
Karen was new to Scrum when the product development started. After 7 Sprints, she gained a lot of experience as a team member and would like to join the Nexus Integration Team. Is she a good candidate to be part of NIT?
Answer: Explanation:
The Nexus Integration Team consists of Product Owner, Scrum Master , One or more Nexus Integration Team Members. Composition of the Nexus Integration Team may change over time to reflect the current needs of a Nexus.
Question 10Selectable Answer
NIT has worked with various teams and concluded the Definition of Done criteria. One of the teams is working on UI part which has to support 3 languages.
As the team feels NIT's Definition is not enough for their work, they would like to add an additional check in their Definition of Done. Is it allowed?
Answer: Explanation:
Individual Scrum Teams may choose to apply a more stringent Definition of âœDoneâ• within their own teams, but cannot apply less rigorous criteria than agreed for the Increment.
Question 11Selectable Answer
What are the possible side effects of teams not integrating their work often? Select two best answers
Answer: Explanation:
Scrum Teams should integrate the code as often as possible to avoid too many code conflicts. Dealing with code conflicts increases the development effort and reduces the productivity.
Question 12Selectable Answer
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?
Answer: Explanation:
Sprint length is usually determined based on risk and uncertainty. When a team is working on riskier requirements, Sprint length is shorter to ensure frequent validation. Reducing the Sprint length of Team C is the right option. Teams in a nexus need not have same Sprint length as long as Sprint boundaries align i.e. there is one common day where all the teams end their Sprint. Reducing the Sprint length for all teams is not needed as they have been performing well with the 2 week model. Adding additional team members to Team C and continuing with 2-week Sprint doesn't necessarily reduce risk or guarantee results.
Question 13Selectable Answer
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?
Answer: Explanation:
In general, velocities should not be used to compare the teams. Scenario in the question clearly indicates that the teams are matured and their estimation techniques are pretty accurate. Team B's velocity was considerably low in Sprint 5 and 6. Hence, there is a need to look into the team members and their skill sets related to screen development. Necessary steps like changing team formation, pair programming can be adapted in the future sprints to improve their skillset.
Question 14Selectable Answer
Development Teams may have different length of Sprints as long as the Sprint boundaries align. True or False?
Answer: Explanation:
Development Teams need not have same Sprint length. It can be different as long as the Sprint boundaries align i.e. there is one common day where all the teams end their Sprint. For e.g.: Team A is following 1 week Sprint, Team B is following 2 week Sprint. At the end of two weeks, both teams will finish their Sprints (Team A 2 Sprints, Team B 1 Sprint). This will help the team integrate the increment
Question 15Selectable Answer
How does Technical Debt impact the product?
Answer: Explanation:
Technical Debt impacts the product and team in several ways. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways. It leads to false assumptions about the current state of the systems specifically of an increment being releasable at the end of a Sprint.
