The Nexus Guide no longer prescribes the format of Nexus Sprint Retrospective. Is it still necessary to have individual teams' sprint retrospective?

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

Who is accountable for managing Product Backlog in Nexus?

• A.Nexus Integration Team
• B.Product Owner
• C.Development Teams
• D.Scrum Master

Comment: *

Name: *

Email: *

Verification: *

During Sprint Planning, it is identified that Team C will not have enough work due to the dependencies from Team A and Team B.
What should the Nexus team do with Team C?

• A.Assign them the PB items which are on the bottom
• B.Release them from the project until there is enough work
• C.Assign them the work of documentation, testing and Integration
• D.Practice pair-programming so that the members can participate in the development work of Team A and B

Comment: *

Name: *

Email: *

Verification: *

During the Nexus Sprint Review of Sprint 2, some users have complained that the system is performing too slow.
What can the Nexus team do to manage user expectations? Select all that apply.

• A.Work with stakeholders and agree on a tangible requirement
• B.It is too early to judge the performance of the increment
• C.Let the stakeholders use the wireframes and take the feedback
• D.Add the non-functional requirement to Definition of Done

Comment: *

Name: *

Email: *

Verification: *

During Nexus Daily Scrum, a new cross-team issue has surfaced which requires security team's assistance. Who should the team members reach out to?

• A.Stakeholders
• B.Nexus Daily Scrum members should directly reach out to Security team
• C.Product Owner
• D.Scrum Master in the Nexus Integration Team

Comment: *

Name: *

Email: *

Verification: *