Question No : 1
Why would a Nexus choose to have different Sprint length for the teams in a Sprint?

• A.When the increment is low risk
• B.All teams in Nexus must have same Sprint length
• C.When there is risk and uncertainty in the items worked by certain teams
• D.When there are inexperienced members in one team

Show Answers

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 No : 2
Which are the three valid questions that can be discussed during Nexus Daily Scrum?

• A.Was the previous day's work successfully integrated?
• B.What did I do yesterday towards Sprint Goal?

Show Answers

Answer:

Question No : 3
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

• A.Increase the Cross-Team refinement activity duration
• B.Adjust the Definition of Done to make the increment releasable
• C.Ask the Product Owner to extend the Sprint
• D.Reduce the number of Scrum Teams to reduce complexity

Show 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 No : 4
What is the recommended number of teams per Nexus?

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

Show Answers

Answer:
Explanation:
3 to 9 Scrum teams are considered ideal for Nexus.

Question No : 5
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.There is technical debt in the product
• B.Definition of Done has too stringent
• C.Developers are struggling to integrate their work
• D.Nexus Integration Team is not coordinating the work among the developers

Show 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 No : 6
What should be done when one team is consistently performing better than the other teams?

• A.Assign low priority tasks to low performing teams
• B.Release the low performing teams from the Nexus
• C.Changing team composition should be considered

Show Answers

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 No : 7
Who are the mandatory members of Nexus Integration Team?

• A.Business Analyst
• B.Scrum Master
• C.Integration Specialist
• D.Product Owner

Show Answers

Answer:
Explanation:
The Nexus Integration Team consists of Product Owner, Scrum Master, One or more Nexus Integration Team Members

Question No : 8
How many additional events does Nexus have compared to Scrum?

• A.5
• B.2
• C.4
• D.3

Show Answers

Answer:
Explanation:
Nexus has five additional Events: Cross-Team Refinement, Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review, and Nexus Sprint Retrospective.

Question No : 9
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?

• A.No, because NIT membership remains same from Sprint 1 to last Sprint
• B.No, NIT members require several years of experience in Scrum
• C.No, because internal team members cannot be part of NIT
• D.Yes, because Karen is now an experienced team member

Show Answers

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 No : 10
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?

• A.No
• B.Yes

Show Answers

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.