What is the main goal of Sprint Planning?

• Refine the backlog

• Assign bugs to testers

• Decide what can be delivered and how

• Report progress to stakeholders

Who attends Sprint Planning?

• Only the Scrum Master and Product Owner

• Scrum Team and Stakeholders

• Developers and Product Owner

• The entire Scrum Team

Which of the following is usually defined during Sprint Planning?

• Definition of Done

• Sprint Goal

• Release Schedule

• Resource Allocation

Can Product Backlog Items be added during Sprint Planning?

• No, the backlog must be frozen before the meeting

• Yes, if they are small enough

• Yes, if they are well-defined and agreed upon

• Only after stakeholder approval

What guides the Development Team in selecting how many items to pull into the Sprint?

• Sprint length

• Team motivation

• Product Owner’s preference

• Team’s past velocity and capacity

What is the first topic addressed in Sprint Planning?

• Assigning tasks to developers

• Reviewing the Sprint Goal

• Estimating new backlog items

• Updating the burndown chart

What is the output of Sprint Planning?

• Updated Product Backlog

• List of impediments

• Sprint Backlog

• Burnup chart

Which statement is true about selecting items for the Sprint?

• The Scrum Master decides

• The Product Owner decides

• The Development Team decides

• Stakeholders decide

When selecting Product Backlog Items for a sprint, what should the team consider first?

• The items with the smallest story points

• The items with the highest business value

• The items assigned by the Scrum Master

• The items requested by stakeholders in the last meeting

Why should capacity be considered in Sprint Planning?

• To estimate story points

• To avoid overcommitting

• To update velocity

• To finalize release dates