True
False
Rate this question:
To be able to reprimand the team when they don’t need their velocity goal for the Sprint.
To know what the team will deliver over the next three Sprints.
To have complete transparency into what has been done at the end of each Sprint.
To predict the team’s productivity over time.
Rate this question:
True
False
Rate this question:
When it becomes clear that not everything will be finished by the end of the Sprint.
When the Sprint Goal becomes obsolete.
When the sales department has an important new opportunity.
When the Development Team feels that the work is too hard.
Rate this question:
True
False
Rate this question:
Turn Product Backlog items into an Increment of potentially releasable product functionality.
Complete the project within the date and cost as calculated by the Product Owner.
Do all of the development work, expect for specialized testing that requires additional tools and environments.
Rate this question:
Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it.
Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.
Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.
Wait until you have a technical writer on your Development Team to take care of this.
The Increment presented at the Sprint Review does not reflect what she thought she had asked for.
She isn’t working full time with the Scrum team.
Developers leave the Team.
The acceptance tests don’t appear to be complete.
Rate this question:
To take time to judge the validity of the project.
To inspect the product Increment with the stakeholders and collect feedback on next steps.
To review the Scrum Team’s activities and processes during the Sprint.
To build team spirit.
Rate this question:
Subject matter experts.
Architects.
The Scrum Master.
Development Team managers.
The Development Team.
Rate this question:
It must be established before Sprint Planning in order to begin planning.
A Sprint Goal is not mandatory in Scrum.
It should have been created in the previous Sprint during Product Backlog refinement.
During Sprint Planning.
At any time during the Sprint.
Rate this question:
The Product Owner demands it.
Rooms are hard to book and this lets it be booked in advance.
The place can be named.
The consistency reduces complexity.
Rate this question:
At least 7.
3 to 9.
7 plus or minus 3.
9.
Rate this question:
Release burndown diagram.
Burdown chart.
Feature burn-up.
Critical Path Analysis.
Refactoring.
Project Gantt chart.
None of the above.
Rate this question:
Annually.
Daily.
Quarterly.
Frequently.
Rate this question:
The Stakeholders.
The Development Team or its members.
The Scrum Master.
The Product Owner.
Rate this question:
True
False
Rate this question:
To make sure every team member answers the three questions.
He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.
To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.
To gather status and progress information to report to management.
Rate this question:
Scrum Master.
Product Owner.
Development Team member.
Project Manager.
None of the above.
Rate this question:
Ask the Product Owner to assign the people to teams.
Ask the Developers to divide themselves into teams.
Create teams based on their skills across multiple layers (such as database, UI, etc.).
Rate this question:
It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
It is a mechanism to control the Development Team’s activities during a Sprint.
It is used to congratulate the Development Team if it did what it forecast, or to punish the Development Team if it failed to meet its forecast.
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
Rate this question:
Immediately after the conclusion of the previous Sprint.
When the Product Owner is ready.
Immediately following the next Sprint Planning.
The Monday following the Sprint Review.
Rate this question:
Management gives an update at the start of each Daily Scrum.
The Product Owner represents their opinions.
The Scrum Master speaks on their behalf.
The Development Team self-manages and is the only management required at the Daily Scrum.
Rate this question:
True
False
Rate this question:
Keeping track of and estimating all undone work to be completed in a separate Sprint.
Updating Sprint tasks properly in the electronic tracking tool.
Reporting Sprint progress to the stakeholders daily.
Doing all work needed to meet the definition of “Done”.
Rate this question:
User stories.
Tasks.
Use Cases.
Tests.
Any of the above (or others) which are a decomposition of the selected Product Backlog items.
Rate this question:
During the Sprint Planning meeting.
During the Sprint.
Prior to the Sprint Planning meeting.
At the beginning of the project.
Rate this question:
Sprint Review.
Release Planning.
Daily Scrum.
Sprint Retrospective.
Refinement Meeting
Rate this question:
Assign tasks with the Scrum team.
Monitor the progress of the Development Team.
Remove impediments.
Ensure the Product Owner attends all Scrum events.
Facilitate inspection and adaptation opportunities as requested or needed.
Escalate team conflicts to functional line managers.
Rate this question:
Inform the Product Owner at the Sprint Review, but prior to the demonstration.
Find another Scrum Team to give the excess work to.
As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.
Reduce the definition of “Done” and get all of the Product Backlog items “Done” by new definition.
Rate this question:
Sprint Retrospective.
Members must stand up at the Daily Scrum.
Sprint Burndown Chart.
Release Planning.
All of the above.
Rate this question:
True
False
Rate this question:
A) The Project Manager.
B) The Product Owner.
C) The Scrum Master.
D) The Development Team.
E) All of the above.
Rate this question:
False.
True.
True, accordingly to what was committed to the stakeholders.
False, capacity and commitment are the Project manager’s responsibility.
True, but only after confirmation by the resource manager that the Team has enough capacity.
False, the Scrum Master does that.
Rate this question:
Stakeholders for the Sprint Review.
Product Backlog ordering.
When to release, based on its progress.
Sprint length.
How to best accomplish its work.
Rate this question:
The need to have enough work to keep all Development Team members busy.
The benefit of Development Teams figuring out a solution for themselves.
The ability of the Development Teams to produce integrated Increments.
The desire to maintain a stable velocity.
Rate this question:
The Chief Product Owner determines the new team structures and assignements.
Managers collaborate to assign individuals to specific teams.
Existing teams propose how they would like to go about organizing into the new structure.
Bring all the developers together and let them self-organize into Development Teams.
Managers personally re-assign current subordinates to new teams.
Rate this question:
Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.
Ask the Product Owner to send the manager the report.
Tell the Development Team to figure it out themselves.
Create and deliver the report to the manager herself.
Tell the Development Team to fit the report into the Sprint Backlog.
Rate this question:
Update the project plan with stakeholders.
Work with the QA departments on the Increment of the current Sprint.
There are no such activities. The next Sprint starts immediately after the current Sprint.
Refine the Product Backlog.
Rate this question:
Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
Add them to the definition of “Done” so the work is taken care of every Sprint.
Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
Put them on a separate list on the Scrum board, available for all to see.
Rate this question:
True
False
Rate this question:
Present the Product Owner with an ordered Product Backlog to use.
Suggest the product Owner extend the Sprint, so he can have more time to order the Product Backlog.
Suggest that the Development Team does the ordering to be sure that it is a feasible ordering of work.
Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.
Encourage the Product Owner to work with the Development Team to see which items technically are fastest to implement.
Rate this question:
There should be six Product Owners, reporting to a chief Product Owner.
The product has one Product Backlog.
There should be six Product Owners, one for each Scrum Team.
There should be only one Product Owner.
Each Scrum Team should have a separate Product Backlog.
Rate this question:
Who are the subject matter experts on each team?
Who are going to be the team leads?
How will we make sure all teams have the right amount of expertise?
What is the right mixture of senior and junior people on each team?
Rate this question:
All development work and at least some testing.
As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done”.
A proportional amount of time on analysis, design, programming, testing, and documentation.
As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.
Rate this question:
The Scrum process, and how it was used during the Sprint.
Coding and engineering practices.
Sprint results.
All of the above
Rate this question:
How the team collaborates.
Documenting acceptance criteria for items in the next Sprint.
Identifying high priority process improvements for the next Sprint.
The order of items in the Product Backlog.
Rate this question:
The Product Backlog only has work for the next 2 Sprints.
The Product Backlog is managed using a web-based-tool.
The Product Backlog is ordered.
The Product Backlog is available to all stakeholders.
Each product Backlog item has a MoSCoW priority.
Rate this question:
Quiz Review Timeline (Updated): Mar 22, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.