Back to Scrum in Practice

Scrum Sprints

5 minutes 5 Questions

Scrum sprints are the heart of Scrum. Sprints are time-boxed events of one month or less during which a potentially releasable subset of the product is created. Sprints provide a structure to deliver value rapidly and receive feedback, they establish a repeatable and predictable rhythm for delivery, and they ensure regular inspection, adaptation, and transparency of progress towards a goal.

Scrum Sprints: A Comprehensive Guide

What is a Scrum Sprint?
A Scrum Sprint is a fixed time period, typically 2-4 weeks, during which a Scrum team works to complete a set amount of work. It is a crucial element of the Scrum framework.

Importance of Scrum Sprints
1. They help manage and control the progress of work.
2. Enables constant feedback and refining of work.
3. Offers opportunities for regular inspection and adaptability.
4. Facilitates a predictable rhythm of work.
5. Supports team cohesion and focus.

How it works?
A Sprint starts with a Sprint Planning meeting where the team identifies the work to be done. The team then works on these tasks and meets daily for a Scrum meeting to discuss progress and barriers. At the end of the Sprint, a Sprint Review and Retrospective are held to inspect the increment and plan improvements.

Exam Tips: Answering Questions on Scrum Sprints
1. Remember the purpose of Sprints.
2. Understand the structure and sequence of Scrum events.
3. Be familiar with the key roles in a Sprint (Product Owner, Scrum Master, Development Team).
4. Know the potential outputs of a Sprint (Product Increment, updated Product Backlog).
5. Understand how adaptive planning and continuous improvement are enabled in Sprints.

Test mode:
Start practice test
PSM I - Scrum in Practice Example Questions

Test your knowledge of Amazon Simple Storage Service (S3)

Question 1

During the Sprint, the team discovers a critical defect that can significantly affect the product. The fix for this defect is not in the current Sprint backlog. As a Scrum Master, what would be your approach?

Correct Answer: Work with the Product Owner to include this item in the Sprint backlog and negotiate other backlog items to meet the Sprint goal.

The correct approach when you discover a critical defect that could significantly impact the product, and it's not part of the current Sprint backlog, is to work with the Product Owner to include this item in the Sprint backlog and negotiate other backlog items to meet the Sprint goal. This is because Scrum values responding to change over following a plan. This does not mean disregarding the plan, but being flexible and adaptable, allowing for changes in the project that would add value to the product. Ignoring the defect because it's not part of the current Sprint and continuing with planned items are not good practice as agile is about early and continuous delivery of valuable software. Similarly, asking the team to work overtime to accommodate the unplanned item without disturbing the Sprint backlog is not sustainable and can introduce the risk of team burnout and decrease their productivity. Finally, cancelling the current Sprint and starting a new one with the defect fix is a last resort option usually considered for significant changes and not defects or issues.

Question 2

During a Sprint, the Development Team discovers that they have over-committed and cannot complete all the items in the Sprint Backlog. What should the Scrum Master do?

Correct Answer: Facilitate a discussion between the Development Team and the Product Owner to negotiate the scope of the Sprint Backlog

The best course of action is for the Scrum Master to facilitate a discussion between the Development Team and the Product Owner to negotiate the scope of the Sprint Backlog. This aligns with the Scrum principles of collaboration, transparency, and adaptability. The Development Team should not work overtime, as it goes against sustainable development practices. Carrying over items to the next Sprint without consulting the Product Owner violates the principle of collaboration and transparency. Dropping lower priority items and focusing only on high priority items should be a decision made in consultation with the Product Owner, not unilaterally by the Development Team or Scrum Master.

Question 3

A Scrum team is ahead of schedule in their Sprint, the Product Owner suggests adding more user stories to the current Sprint. As a Scrum Master, how should you handle this situation?

Correct Answer: Discuss that this goes against Scrum principles, but the Product Owner may add it to the upcoming Sprint.

According to the principles of Scrum, once a Sprint has started, its scope is supposed to be fixed and unchangeable. Therefore, adding more user stories in the middle of a Sprint, even if the team is ahead of schedule, is contrary to these principles. This ensures that the development team can commit to an achievable goal and mitigate unpredictability. For the other answers - including user stories immediately in the current Sprint disrupts the flow of work and undermines commitment. Suspending the current Sprint until the Product Owner has enough user stories for a new Sprint is against the Scrum practice of having set, consistent Sprint lengths. Ignoring the Product Owner goes against the team collaboration principle of Scrum.

Go Premium

Professional Scrum Master I Preparation Package (2024)

  • 2149 Superior-grade Professional Scrum Master I practice questions.
  • Accelerated Mastery: Deep dive into critical topics to fast-track your mastery.
  • Unlock Effortless PSM I preparation: 5 full exams.
  • 100% Satisfaction Guaranteed: Full refund with no questions if unsatisfied.
  • Bonus: If you upgrade now you get upgraded access to all courses
  • Risk-Free Decision: Start with a 7-day free trial - get premium features at no cost!
More Scrum Sprints questions
17 questions (total)
Start 17 question test