Crowdly

Increment

Product Backlog

Sprint Backlog

What Product Backlog is?

A wishlist from all stakeholders

A single source of requirements for any changes to be made to the product

An ordered list of everything that might be needed in the product

A messy storage of all thoughts and features to be implemented in a product

What DEEP acronym for Product Backlog stands for?

Distinct, Estimated, Emergent, Prioritized

Detailed Appropriately, Elaborated, Emergent, Prioritized

Detailed Appropriately, Estimated, Emergent, Particular

Detailed Appropriately, Estimated, Emergent, Prioritized

What attributes each Product Backlog Item has?

Order

ROI

Value

Mock-up

Estimate

Description

The Increment is the sum of:

Value of the increments of all previous Sprints

All PBIs that were planned for current Sprint

Product Backlog items completed during a Sprint

Action Items from the Retrospective

Sprint Backlog consists of:

Plan for delivering the product Increment and realizing the Sprint Goal

At least one high priority way in which the team works, identified in the previous

Retrospective meeting

Product Backlog items selected for the Sprint

All high-priority change requests

Definition of Ready helps:

To ensure transparency

To prevent problems before they have a chance to start

To provide clarity to a Product Owner on what it means to create ready backlog items

Definition of Done is ...:

Review and acceptance of PBI from Product Owner

A shared understanding of what it means for work to be complete

Developed, tested and deployed feature

Acceptance Criteria in PBI

What are the outputs of Daily Scrum? (Multiple Answer)

Statuses written on the dashboard

Adjusted plan for the next 24 hours

Status updates sent to all stakeholders

List of known impediments

Maximum length of Daily Scrum is:

30 minutes

15 minutes

10 minutes

It depends on the Scrum team size