Scrum-SPS Dumps Scrum-SPS Braindumps

Scrum-SPS Real Questions Scrum-SPS Practice Test Scrum-SPS Actual Questions


Scrum


Scrum-SPS


Scaled Professional Scrum (SPS)


https://killexams.com/pass4sure/exam-detail/Scrum-SPS

Question: 48


How many additional events does Nexus have compared to Scrum?

  1. 5

  2. 2

  3. 4

  4. 3


Answer: A Explanation:

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


Question: 49


What does Nexus Sprint Backlog contain?

  1. All the Product Backlog items selected by all teams for that Sprint

  2. Only the Product Backlog items which have cross team dependency

  3. Only the Product Backlog items which Nexus Integration Team must work on


Answer: A Explanation:

A Nexus Sprint Backlog is the composite of Product Backlog items from the Sprint Backlogs of the individual Scrum Teams.


Question: 50


The purpose of Nexus Daily Scrum is to make integration issues Transparent. True or False?

  1. FALSE

  2. TRUE


Answer: B Explanation:

The purpose of the Nexus Daily Scrum is to make integration issues Transparent so that necessary actions can be taken to resolve such issues.


Question: 51

Who has to attend the Nexus Sprint Retrospective?

  1. Representatives of each Scrum Team

  2. Product Owner, Scrum Master and Customer

  3. Every Nexus member

  4. Depends on the Nexus team


Answer: D Explanation:

The purpose of the Nexus Sprint Retrospective is to plan ways to increase quality and effectiveness across the whole Nexus. The Nexus inspects how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done. In addition to individual team improvements, the Scrum Teamsâ™ Sprint Retrospectives complement the Nexus Sprint Retrospective by using bottom-up intelligence to focus on issues that affect the Nexus as a whole. Nexus Guide no longer prescribes the format of the Nexus Sprint Retrospective. The format depends on the Nexus team and they will work towards achieving the objective of the event. It is clear from the Nexus guide that individual scrum teams’ retrospectives will also be held. A Nexus team may decide that every member should attend the Nexus Sprint Retrospective if they think it is beneficial.


Question: 52


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?

  1. Assign them the work of documentation, testing and Integration

  2. Practice pair-programming so that the members can participate in the development work of Team A and B

  3. Assign them the PB items which are on the bottom

  4. Release them from the project until there is enough work


Answer: B Explanation:

In Nexus, it is a real possibility that one of the teams does not have enough work due to dependencies. Pair Programming is a great practice in this kind of situation.

Question: 53


What is true about Product Owner’s accountability in Nexus? Select all that apply.

  1. A second Product Owner is needed

  2. Scope of work increases

  3. Product Owner’s accountability does not change from Scrum

  4. Accountability of a product delivery shifts to Nexus Integration Team


Answer: B,C

Explanation:


The Product Owner’s accountability does not change from Scrum; the scope of the work is simply more complex. There is always one Product Owner in a Nexus and he/she is accountable for product delivery.


Question: 54


What is true about Nexus Sprint Planning? Select two best answers.

  1. Nexus Sprint Goal is crafted during Nexus Sprint Planning

  2. It is better if all members of Nexus can attend to avoid communication issues

  3. It is time boxed to 8 hours for a 1 month Sprint

  4. Nexus Sprint Planning replaces individual teams’ Sprint Planning


Answer: A,B Explanation:

There is no time box for Nexus Sprint Planning. It is anticipated that it’ll take longer in the initial Sprints of a product development. It is recommended for all members to attend it to avoid communication issues. Nexus Sprint Goal is also crafted during Nexus Sprint Planning.


Question: 55


Can a specialist outside of Nexus join Nexus Integration Team? Yes or No?

  1. No

  2. Yes


Answer: B Explanation:

Nexus Integration Team members may come from outside the Scrum Teams from other parts of the organization. They provide unique expertise that the Scrum Teams lack.


Question: 56


Increment can be released mid-Sprint if necessary. True or False?

  1. TRUE

  2. FALSE


Answer: A Explanation:

If Nexus has a releasable product/increment, it can be released any time. No need to wait until the end of the Sprint.


Question: 57

Which event is present in Scrum but not in Nexus?

  1. Sprint Review

  2. Daily Scrum

  3. Sprint Planning

  4. Sprint Retrospective


Answer: A Explanation:

Individual Team Sprint Review is removed in Nexus. Since Scrum Teams in a Nexus work together to produce a single Integrated Increment, that Integrated Increment should be reviewed as a whole.


Question: 58


Who are the members of Nexus Integration Team? Select all that apply.

  1. Project Manager

  2. Customer

  3. Product Owner

  4. Scrum Master

  5. Scrum Team members


Answer: C,D,E Explanation:

Product Owner, Scrum Master, Few Scrum Team members are part of Nexus Integration Team. There is no Project Manager in Scrum/Nexus. Customer is never part of Scrum Team.


Question: 59


What is Nexus?

  1. Methodology

  2. Philosophy

  3. Framework

  4. Prescriptive approach


Answer: C Explanation:

Nexus is a framework that enables multiple teams to work together to deliver one product.


Question: 60


Who is responsible for clearing the technical debt?

  1. Product Owner

  2. Stakeholders

  3. Developers

  4. Nexus Integration Team

  5. Scrum Master


Answer: C Explanation:

Developers are responsible to clear the technical debt as they own the code.


Question: 61


Who is responsible for Definition of Done in Nexus?

  1. Development Team Members

  2. Scrum Master

  3. Nexus Integration Team

  4. Product Owner


Answer: C Explanation:

The Nexus Integration Team is responsible for a definition of Done that can be applied to the Integrated Increment developed each Sprint.


Question: 62


Can a Product Owner be part of Nexus Integration Team? Yes or No?

  1. No

  2. Yes


Answer: B Explanation:

Product Owner, Scrum Master, Few Scrum Team members are part of Nexus Integration Team.


Question: 63


When compared to Scrum, which additional artifact does Nexus have?

  1. Nexus Team Backlog

  2. Definition of Done

  3. Nexus Product Backlog

  4. Nexus Sprint Backlog


Answer: D

Explanation:


Nexus Sprint Backlog is the new artifact added in Nexus. It is the Nexus plan for the Sprint.


Question: 64


Who coaches and guides the Scrum Team in the application of Nexus?

  1. Product Owner

  2. Project Manager

  3. Nexus Integration Team

  4. Scrum Integration Team


Answer: C Explanation:

The Nexus Integration Team (Nexus Integration Team) is the new accountability added to Nexus. It exists to promote and provide Transparent accountability for integration in a Nexus. Nexus Integration Team coaches and guides the scrum teams in the application of Nexus. Nexus Integration Team never does the integration work. Even in Nexus, Product Owner owns the Product Backlog.