Agile Scrum Master Certification Exam Prep (CSM) - Important Tasks for Sprint

The video tutorial explains the concept of Sprint in Scrum, emphasizing its role as a time-boxed event with a fixed duration. It highlights the importance of maintaining a consistent Sprint backlog and goal, avoiding changes during the Sprint. The tutorial also discusses the negotiation of scope between the product owner and the development team, ensuring that the Sprint backlog remains unchanged. Additionally, it covers the development of user stories within a Sprint and the significance of a clear definition of done to ensure successful project completion.

What is the recommended duration for a Sprint in Scrum?

• Two to three months

• Six to eight weeks

• Four to six weeks

• One to two weeks

Why should the Sprint backlog not be changed once the Sprint has started?

• To accommodate changes in team composition

• To allow for more flexibility in task management

• To maintain the planned workflow and avoid confusion

• To ensure the team can work on new tasks

What should be the focus if a Sprint goal is not achieved?

• Ignore the missed goal

• Change the Sprint backlog

• Replan in the next Sprint

• Alter the current Sprint plan

Who is responsible for handling the product backlog?

• Scrum Master

• Development Team

• Product Owner

• Stakeholders

What is the primary factor in selecting user stories for a Sprint?

• Team preference

• Client's business value

• Ease of implementation

• Random selection

What must be agreed upon at the beginning of a project to ensure work is completed satisfactorily?

• Client feedback

• Team roles

• Definition of done

• Project budget

What happens if a completed item does not meet the 'definition of done'?

• It is discarded

• It is added to the next Sprint

• It is sent to the client for review

• It is demonstrated to the customer