MCQ on Agile Ceremonies

What is the primary goal of the Sprint Planning ceremony?

• Define the sprint backlog and plan the work for the upcoming sprint

• Review the previous sprint's burn-down chart

• Demonstrate the increment to stakeholders

• Allocate team members to specific roles

Which artifacts or inputs must the team review before starting Sprint Planning?

• Product backlog, team capacity, and Definition of Done

• Only the release roadmap

• Sprint retrospective minutes

• Company org chart

Who are the mandatory participants in Sprint Planning, and what roles do they play?

• Product Owner (defines "what"), Development Team (defines "how"), Scrum Master (facilitates)

• Scrum Master (makes all decisions), Stakeholders (observe), Development Team (reports status)

• Development Team (plans alone), Product Owner (optional), Scrum Master (optional)

• All company employees, Product Owner (approves), QA (allocates test cases)

How is the sprint backlog created and estimated during Sprint Planning?

• The team selects high-priority items from the product backlog and estimates them collaboratively, often in story points

• The Product Owner assigns tasks to developers and estimates effort in hours

• The Scrum Master writes tasks and uses past velocity to assign points

• Individual team members choose tasks and estimate privately

What timebox is typically allocated for Sprint Planning in a one-month sprint?

• 8 hours

• 1 hour

• 4 hours

• 30 minutes

What three questions does each team member answer during a Daily Stand-Up?

• What did I do yesterday? What will I do today? What impediments do I face?

• What are my deliverables? Who will test my work? When is the release?

• Did I meet my targets? Who is absent? What are the risks?

• What feedback did I get? What do I estimate next? What meetings do I have?

Why is it important to keep the Daily Stand-Up timeboxed to 15 minutes?

• To maintain focus, minimize interruptions, and respect everyone's time

• To allow deep discussion on each impediment

• To give the Scrum Master more control

• To reduce the number of daily status emails

How does the team use the Daily Stand-Up to identify and address impediments?

• Team members call out blockers, then the Scrum Master or the team agrees on next steps

• The Product Owner solves all impediments immediately

• Impediments are noted and ignored until the next Retrospective

• QA documents impediments for monthly review

Who facilitates or leads the Daily Stand-Up, and why?

• The Scrum Master, to keep the meeting on track and remove obstacles

• The Product Owner, to prioritize tasks

• Any team member, rotating daily

• A stakeholder, to hold the team accountable

What difference does it make to hold the Daily Stand-Up at the same time and place every workday?

• Improves consistency, habits, and attendance

• Causes scheduling conflicts

• Limits participation to those physically present

• Reduces transparency