SPS Practice Test
In Nexus, all Scrum Teams have the same Sprint length.
True
False
The Nexus Sprint Review replaces the Sprint Review in each individual Scrum Teams.
True
False
From the list below, what is the most important concern for multiple Development Teams when they are working from the same Product Backlog?
Meeting original scope projections
Clear definition of requirements
Minimizing dependencies between teams
Making sure there's enough work for everyone on every team.
How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?
The Product Owner decides.
The Development Teams pull in work in agreement with the Product Owner.
The Development with the highest velocity pulls Product Backlog items first.
Each Scrum Team takes an equal number of items.
The Product Owner should provide each team with its own Product Backlog.
What are two ways that architecture and infrastructure are handled in Scrum?
They are discussed during Product Backlog refinement and are developed only along with selected functionality.
They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small.
They are built by a separate team through the creation of an architectural runway.
They are discussed, determined, and documented before the actual feature development Sprints.
How should multiple Scrum Teams deliver a "Done" potentially releasable increment in a Sprint?
Each Scrum Team provides a unique "Done" increment that includes the Team's added functionality
The 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. The sum of all increments is the increment for that product
Each Scrum Team delivers "Done" increment of its own area of responsibility. These increments are integrated into a whole product during stabilization prior to release.
The purpose of a Nexus Sprint Retrospective is to: (Choose the best two answers)
Enable bottom-up intelligence to improve how the teams in a Nexus are working together
Allow for inspection and adaptation of both individual Scrum Teams and a Nexus
Provide a single meeting to inspect and adapt how all teams work together
Provide a forum for management to see how the Nexus is performing
What are the purposes of the Nexus Sprint Planning? Select three.
The sequence of work across teams is adjusted
All Nexus Sprint Backlog items are estimated in detail
Cross team dependencies are detected
The Nexus Sprint Goal is formulated
Can Scrum Teams use own Definition of Done within a Nexus?
Yes, they can, but the criteria should be more rigorous than agreed for the Increment.
No
Yes and all Scrum Teams should use the that DoD.
May the members of the Nexus Integration Team also work on the Scrum Teams in that Nexus?
Yes, but priority must be given to the work for the Nexus Integration Team
No, members of the Nexus Integration Team should not work for the Scrum Teams
Yes, but priority must be given to the work for the Scrum Team
A company has 6 major products using Scrum Teams. Select two best options for Product Ownership
One and only one. This Product Owner may delegate to others for specific value, capabilities and functionalities within each product
As many as needed to communicate expectations and requirements with Development Teams
One Product Owner is reasonable for each Product. This Product Owner may delegate to others for specific value, capabilities and functionality within the product.
A six team Nexus is developing Web-based application. There are different parts of the application that only certain Scrum teams can work on. In fact, there are some highly specialized individuals outside the Nexus that are required for some of the work. In past Sprints the Nexus encountered challenges dealing with the many dependencies between Scrum Teams. Which of the following two strategies would be most effective in dealing with their dependencies?
Discover and document dependencies during Product Backlog refinement, so teams are aware of dependencies before Nexus Sprint Planning. This will allow Nexus Sprint Planning to focus on resolving dependencies for the upcoming Sprint.
Gather all people in the Nexus into a 48-hour Nexus Sprint Planning event. Discover, document and resolve dependencies during this time
Have the Nexus Integration Team order the Nexus Sprint Backlog. They should control and resolve the dependencies.
During Nexus Sprint Planning, have appropriate representatives from each team in the Nexus briefly meet to discuss dependencies for the upcoming Sprint. This conversation will help their individual team's Sprint Planning meetings.
What are the best ways to improve productivity of all Scrum teams? Choose three.
Appropriately distribute domain knowledge between the Scrum Teams
Reduce overlapping of requirements
Remove or minimize dependencies of software and test artifacts
Add a Nexus expert into each Scrum Team
Organize a training on the Nexus framework for all developers
A 5-team Nexus works on a Product. During the Nexus Sprint Review, the teams present the results of the Sprint. After introduction, each team takes time to present their work for inspection by individually showing the new features they have built. They are not using a shared environment and the stakeholders do not provide much feedback. If this pattern of Nexus Sprint review continues for many Sprints, what may be the effects? (Choose 2 best answers)
Ability to adapt will suffer as the stakeholders continue to disengage and not give feedback
Technical debt will build as the teams delay integrating their work into a single integrated increment.
There will be more and more work to inspect so teams will need their own individual Sprint Reviews
Empiricism will suffer as the teams can't produce a shared velocity
What is the purpose of a Scrum of Scrums?
Align plans for different Scrum Teams by bringing the Scrum Masters together every day.
Meet to report to stakeholders.
Align Product Backlogs of related products by bringing their Product Owners together.
Share cross-team experiences of different Scrum Masters.
Align plans of different Development Teams working on the same product
{"name":"SPS Practice Test", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"In Nexus, all Scrum Teams have the same Sprint length., The Nexus Sprint Review replaces the Sprint Review in each individual Scrum Teams., From the list below, what is the most important concern for multiple Development Teams when they are working from the same Product Backlog?","img":"https://www.quiz-maker.com/3012/images/ogquiz.png"}
More Quizzes
ENGLISH DICTATION
1269
Do you have any recommendations in new papers today?
100
U know me?
11610
Which Sanderson Sister Are You?
940
What LCCU character are you?
147106
Pig Heart Boy
1050
Meeting Expectations
420
BCC September Quiz
1160
Quarterly Quiz Q4 2017 - France Retail & BSI
31160
Anatomie quiz
2811400
US Gov Midterm Test
49240
How well do you know me
14713