Getting Started with Scrum - Step 13: Implement the Sprint Backlog Items

The video tutorial explains the process of implementing assigned items in a Sprint, highlighting the distinction between Product Backlog Items and Sprint Backlog Items. Developers pick tasks from the Sprint board, aiming to meet the Sprint Goal, which can be a collective or individual target. By the end of the Sprint, a product increment is created and demoed to the customer. Feedback is gathered and added to the product backlog for future consideration. The focus is on developers executing these tasks.

What are user stories referred to as when they are part of the Product Backlog?

• Sprint Backlog Items

• Product Backlog Items

• User Story Items

• Development Backlog Items

During the implementation phase, what is expected regarding the time taken to complete tasks?

• It should be less than the estimated time

• It should match the estimated time from Sprint Planning

• It should exceed the estimated time

• Time is not a concern during implementation

What can the Sprint Goal be?

• A single goal for the entire team or individual goals

• A goal that is not related to the Sprint

• A goal that changes daily

• A goal only for the team leader

What is a product increment?

• A new version of the product

• A set of new features or a requirement addressed in the Sprint

• A minor bug fix

• A complete overhaul of the product

What happens if the customer provides feedback on the product increment?

• The feedback is ignored

• The feedback is compiled and added to the product backlog

• The feedback is immediately implemented

• The feedback is discarded