Agile Scrum Master Certification Exam Prep (CSM) - Timeboxing

The video tutorial explains the role of Sprints in Scrum, emphasizing timeboxing and its importance in project management. It covers the structure and purpose of various meetings, including Sprint planning, review, retrospective, and daily standups. The tutorial highlights the roles of the Scrum master and product owner in facilitating these processes and ensuring project success.

What is the primary role of the Scrum Master during a Sprint?

• To write user stories

• To manage the budget

• To approve the final product

• To coordinate and guide the team

How long is a typical Sprint advised to be?

• One to six hours

• One to six months

• One to six weeks

• One to six days

What is the main focus of a Sprint planning meeting?

• To finalize the project budget

• To plan and prioritize the work for the Sprint

• To create a detailed project timeline

• To review the completed work

What is the purpose of the Sprint Review meeting?

• To discuss team performance

• To review and validate the completed work

• To plan the next Sprint

• To allocate resources for the next Sprint

During a Sprint Review, who decides whether the user stories are accepted or rejected?

• The Product Owner

• The Project Manager

• The Scrum Master

• The Development Team

What is the main goal of a Retrospective Sprint meeting?

• To plan the next Sprint

• To finalize the project budget

• To allocate tasks for the next Sprint

• To learn from past mistakes and improve

What are the three questions addressed in a daily standup meeting?

• What is the project budget? What is the timeline? What resources are needed?

• What did I do yesterday? What will I do today? What obstacles are in my way?

• What is the project scope? What are the risks? What are the deliverables?

• Who is responsible for what? What is the deadline? What is the budget?