NEXUS ETUDIANTS

How should multiple Scrum Teams deliver a done, useful, and valuable Increment in a Sprint? (choose the best answer)

• Each Scrum Team provides a unique done Increment that includes the team's added functionality

• Each Scrum Team delivers done Increments of its own area of responsibility. These Increments are integrated into a whole product during stabilization prior to release.

• Functionality not integrated with the work of other Scrum Teams may be delivered as unintegrated Increments. This demonstrates the value created by the Scrum Teams unable to completely integrate their Increments.

• Each Sprint, all Scrum Teams have a done Increment that integrates with all of the other done Increments from all other Scrum Teams on the initiative. The sum of all Increments is the Increment for that product.

What is the most important concern for multiple Scrum Teams when they are working from the same Product Backlog? (choose the best answer)

• Clear definition of requirements.

• Minimizing dependencies between Scrum Teams.

• Meeting original scope projections.

• Making sure there is enough work for everyone on every team.

The purpose of the Nexus Sprint Backlog is: (choose the best two answers)

• To plan the product release.

• To visualize all Product Backlog items.

• To make dependencies transparent to the Scrum Teams.

• To provide a view of dependent Product Backlog items in a Sprint.

Using Scrum ensures that adding more resources to a project proportionally increases the value delivered.

• True

• False

A Nexus Daily Scrum: (choose the best two answers)

• Is the same as a Scrum-of-Scrums.

• Is only for the Nexus Integration Team to plan their work for the next 24 hours.

• Is an opportunity to make integration issues transparent.

• Provides a single meeting where all teams can update the Sprint Backlog.

• Provides input into each team's individual Daily Scrums, so that each Scrum Team can better plan their work until their next Daily Scrum.

What are two ways that Developers can ensure a good application architecture? (choose the best two answers)

• The Developers focus only on adding functionality. The architecture will take care of itself as the Developers add functionality.

• The Scrum Team uses a Sprint 0 to create infrastructure that will be needed later.

• The Developers have a set of guiding architecture principles that every Developer understands and follows when building the product.

• Architecture is an ongoing discussion between Developers who are implementing current Sprint Backlog items.

All Scrum Team members must attend the Nexus Daily Scrum.

• True

• False

Developers may also serve on the Nexus Integration Team.

• True

• False

What is the purpose of the Nexus Sprint Retrospective? (choose the best answer)

• To plan ways to increase quality and effectiveness across the whole Nexus.

• To discuss what went well during the Sprint.

• To identify dependencies between teams.

• To identify the one item teams should discuss during their individual Sprint Retrospective.

Complex products are often decomposed into components. These components may be represented as activities, workflows, functions, features, capabilities, and other similar nomenclature. How does this product decomposition affect the way that multiple Scrum Teams work together to deliver the products? (choose the best answer)

• People are assigned to Scrum Teams based on their expertise and the skills needed to develop each component. Hardening Sprints ensure time for resolving dependencies between teams.

• How the organization discusses and plans the work of creating the components will be reflected in the implementation of that product.

• There is one Scrum Team for each component whose job is to coordinate dependencies, work allocation, integration, and testing.

• Meta-Scrum Teams of up to two hundred people are formed. They then map themselves into appropriately sized Scrum Teams for actual product development. This may change every Sprint. Each Meta-Scrum Team manages its own decomposition and integration needs.