How a Product Backlog should be ordered?

• Based on the size of the items

• Based on the risk of the items

• Based on the float of the items

• Based on the value of the items

What is a Product Backlog?

• It is a living artifact of product requirements that exists and evolves as long as a product exists.

• It is a formally approved list of requirements to be implemented over a set period.

• It is a detailed list of functionality from which the Development Team draws items, to be complemented by a separate Technology Backlog managed by the Development Team.

• It is a list of references to Use Case documents that are stored in a central repository. The references should be viewable and clickable by anybody to enhance transparency.

What are the Scrum Artifacts and who owns each one? (pick all that are correct)

• Product Backlog - owned by the Product Owner

• Sprint Backlog - owned by the Development Team

• Increment - owned by the Development Team

• Monitoring of Progress Towards Goal - owned by the Product Owner

• Monitoring of Sprint Progress - owned by the Development Team

What is the purpose of the Sprint

• To complete all tasks in the Sprint

• To produce a done increment of working product

• To complete all tasks with the highest priority

Who are responsible for creating user stories?

• Product Owner

• Dev Team

• Manager

• Customer

• CEO

We should add ... when we create a user story.

• Acceptance Criteria

• Sprint Backlog

• Documentation

• Product Backlog

• Definition of Done

How should we write a user story?

• As a [why], I want [what], because [who]

• As a [what], I want [why], because [who]

• As a [what], I want [who], because [why]

• As a [who], I want [what], because [why]

Who creates the Definition of "Done"?

• The Product Owner as he/she is responsible for the product

• The Scrum Master as he/she is responsible for the Development Team's productivity

• The Scrum Team , in a collaborative effort where the result is the common denominator of all members' definitions

The definition of "Done" describes the work that must be completed for every Product Backlog item before it can be deemed releasable. What should the Development Team do when, during the Sprint, it finds out that a problem outside of their control blocks them from doing all this work?

• Immediately raise the issue to the Scrum Master as an impediment.

• Complete the work that can be done on as much scope as possible and use the Sprint Review to plan the rest with the stakeholders.

• Complete the work that can be done on as much scope as possible and complete the rest during the "hardening" sprints at the end of the release.

• Cancel the Sprint.

• Stop using Scrum.

What does 1 story point equate to?

• One day's worth of development work from concept to completion.

• One hour worth of development work from concept to completion.

• An abstract measurement of the simplest, baseline amount of effort, complexity, and risk a User Story presents on average and relative to type of work the Development Team typically does.

• An absolute 100% accurate measurement of how much effort it will take for the Development Team to deliver a story without question.