Quiz 5

• Who is responsible for upkeeping the Sprint Backlog?

  • The Stakeholders

  • The Development Team

  • The Scrum Master

  • The Product Owner

• What information is documented in the Sprint Backlog?

  • A detailed list of PBI's to be completed during a Sprint

  • The Company's marketing deadlines

  • A general list of prioritized feature for the product

  • A list of items that were already completed during the previous Sprint

• A team selects a Product Backlog Item (PBI) for the Sprint Backlog. What must a team do to finish the Product Backlog Item it selects?

  • Analyze, design, program, test and document the PBI.

  • As much as can be done in the Sprint before the deadline.

  • When Scrum Master states Backlog item is done.

  • As much as is required to satisfy the definition of 'done'.

• A customer requested that as part of the teams' Definition of Done, the development team include a report summarizing functionality added and defects found and fixed for MVPs created during a Sprint. The team agreed that this would help to enhance customer participation by encouraging customer feedback during the Sprint Review. Who would be best positioned to prepare this type of report?

  • The Scrum Master and the Product Owner

  • The Product Owner and the Customer

  • The Product Owner and the Development Team

  • The Scrum Master and the Development Team

• Who is responsible for upkeeping the Product Backlog?

  • The Development Team

  • The Product Owner

  • The Stakeholders

  • The Scrum Master

• This term identifies the historical measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. It is calculated at the end of the Sprint by summing up the Points for all fully completed User Stories.

  • Velocity

  • Predictability

  • Capacity

  • Statement of Work

• In a Scrum project, when would a requirement get added to the Product backlog?

  • When the customer requests a new requirement.

  • When the team works on it for a particular release.

  • When testing of the item from Sprint backlog fails.

  • When it has been developed, but cannot yet be released.