Question 17 - A Scrum Team is at the end of a Sprint. The next Sprint starts:

  • After the Retrospective event of the current sprint

  • After the product increment is released to production

  • After the Sprint Planning

Question 19 - A Scrum Team can have an exclusive first Sprint to prepare Product Backlog which is the sole outcome from that Sprint

  • False

  • True

Overall explanation

  • The only outcome of each Sprint is a potentially releasable Increment of “Done” product.
  • A “Done” increment is required at the Sprint Review.

Question 23 - Who decides what to work on for the next Sprint?

  • The Product Owner

  • The Project Management Office (PMO)

  • The Scrum Master

  • The Product Manager

Overall explanation

  • The Product Owner is the sole person responsible for managing the Product Backlog.

  • Product Backlog management includes:

    • Clearly expressing Product Backlog items;

    • Ordering the items in the Product Backlog to best achieve goals and missions;

    • Optimizing the value of the work the Development Team performs;

    • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,

    • Ensuring the Development Team understands items in the Product Backlog to the level needed.

Question 35 - Multiple Scrum Teams workings on the same project must have the same Sprint start date

  • True

  • False

Overall explanation

  • There is no mandatory rule to have different start dates or the same start date of a sprint through teams

Question 40 -The Sprint length should be:

  • All of these answers are correct.

  • Short enough to be able to synchronize the development work with other business events.

  • No more than one month.

  • Short enough to keep the business risk acceptable to the Product Owner.

Question 41 - What is the accountability of the Product Owner during Sprint 0?

  • Gathering, eliciting, and analyzing the requirements that will be inserted into the Product Backlog

  • Make sure enough Product Backlog items are refined to fill the first 3 Sprints

  • There is no such thing as Sprint 0

  • Determine the composition of the Development Teams so they have the capacity to deliver the completed forecast

  • Make the complete project plan to commit date, budget and scope to the stakeholders

Overall explanation

  • Development Teams deliver an Increment of product functionality every Sprint.
  • This Increment is useable, so a Product Owner may choose to immediately release it.
  • If the definition of "Done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum.

Question 64: When might a Sprint be abnormally terminated?

  • When the Sprint Goal becomes obsolete

  • When the Development Team feels that the work is too hard

  • When it becomes clear that not everything will be finished by the end of the Sprint

  • When the sales department has an important new opportunity

Overall explanation

  • A Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.

  • A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.

Question 72: What is used by the Product Owner to identify unfinished work at the end of the Sprint

  • Testing Standard

  • Definition of “Ready”

  • Coding Standard

  • Definition of “Done”

Overall explanation

  • The definition of “Done” provides the same shared understanding and transparency of what has been done at the end of the Sprint.

Question 77 - When is a Sprint over?

  • When all the tasks are completed

  • When all Product Backlog items meet their definition of "Done"

  • When the time-box expires

  • When the Product Owner says it is done

Overall explanation

  • All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.

Question 98 - Select the true statements. Before starting the first Sprint, what are the prerequisites?

  • A staffed Scrum Team

  • Just enough Product Backlog Items with business ideas for the first Sprint

  • A complete Product Backlog capturing all the detailed product needs

  • A completed System Architecture

  • The availability of the Project Manager

Overall explanation
• The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.

• Enough work is planned during Sprint Planning for the Development Team to forecast what it believes it can do in the upcoming Sprint.

Question 109 - A team should NOT start the first Sprint until the Product Owner has detailed all of the Product Backlog items in the Product Backlog.

  • True

  • False

Overall explanation

  • The earliest development of the Product Backlog lays out the initially known and best-understood requirements.
  • It evolves as the product and the environment in which it will be used evolves and constantly changes to identify what the product needs to be appropriate, competitive, and useful.

Question 118 - A properly functioning Scrum Team will have at least one Release Sprint and may well have several

  • False

  • True

Overall explanation

  • The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created.