Increment

5 minutes 5 Questions

An Increment in Scrum is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints. At the end of a Sprint, the new Increment must be 'Done,' which means it is in a usable condition and meets the Scrum Team’s definition of 'Done'. An increment is a step towards a v…

Guide on Increment concept in Scrum

The 'Increment' is a core concept of Scrum and is essential to its understanding.

What is it?
The Increment in Scrum refers to the sum of all the Product Backlog items completed during a Sprint combined with the increments of all previous Sprints. It is essentially a step towards achieving a product.

Why is it important?
The importance of the Increment lies in its role in creating a potentially releasable (deliverable) product increment by the end of a Sprint. This allows stakeholders to see the progress made, facilitates feedback, and keeps the product continually moving forward.

How it works?
In Scrum, the goal is to achieve a potentially releasable product increment by the end of each sprint. The team selects items from the Product Backlog, turn these into an Increment of potentially shippable product functionality.

Exam Tips: Answering Questions on Increment
While answering questions regarding Increment, ensure that you understand that an Increment is a step towards the final product and represents all the work that has been completed to date. This understanding is essential for answering questions correctly. Also, familiarize yourself with terms like 'potentially shippable' and 'Product Backlog', as they often appear in exam questions associated with the Increment.

Remember that the Increment provides frequent observable outcomes, a fundamental Scrum Principle. Keep these tips in mind, and answering questions on Increment will be a breeze!

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

CSM - Increment Example Questions

Test your knowledge of Increment

Question 1

When a Scrum Team identifies an opportunity to improve the product through an Increment that requires integration of a new technology not originally estimated for, what should be their course of action?

Adopt the new technology after reassessing its impact on the product Increment and consulting with the Product Owner. Immediately integrate the new technology without assessing its impact, as all improvements are beneficial. Suggest the Product Owner to include the technology in the next Sprint for thorough evaluation before proceeding. Continue with the current plan to avoid risking the delivery timeline, discussing the new technology as a potential future enhancement.

Correct Answer: Adopt the new technology after reassessing its impact on the product Increment and consulting with the Product Owner.

In Scrum, when an opportunity to improve the product arises, the Scrum Team should carefully assess the implications of this change, particularly with regards to new technologies. The most correct course of action is to adopt the new technology after reassessing its impact on the current Increment and consulting with the Product Owner. This approach ensures that any decision made is in the best interest of the product's success and is aligned with the Product Owner's vision and priorities. Consulting with the Product Owner ensures that the team is aligned with the product's goals and roadmap, and reassessing the impact helps the team understand the implications on the timeline, budget, and quality of the product. The other options are less suitable because continuing with the current plan without considering the new technology might lead to missed opportunities for improvement. Immediately integrating new technology without assessing its impact can be risky and might introduce unnecessary complications or delays. Suggesting the Product Owner to include the technology in the next Sprint for thorough evaluation before proceeding might delay the benefits of the new technology and does not consider the immediate reassessment and consultation needed with the Product Owner.

Question 2

The increment is finished and includes a functionality that needs a bit more polishing to reach 'done' standard. Should it be included in the increment review meeting?

Yes, it should be included in the increment review meeting to gather feedback and discuss the remaining work to achieve 'done'. No, items not meeting the 'done' criteria should be held back until the next Sprint begins for re-assessment. Items that are nearly done can be considered for inclusion, but the team should first hold a refinement session to estimate the additional effort required, potentially adjusting the Sprint backlog before the review. Yes, but it should only be briefly mentioned with more focus on the fully completed items to not detract from the achievements of the Sprint.

Correct Answer: Yes, it should be included in the increment review meeting to gather feedback and discuss the remaining work to achieve 'done'.

The Sprint Review Meeting is an opportunity to inspect the Increment and adapt the Product Backlog if needed. It is important to present the work as it currently stands, including items that might require additional polish. This allows stakeholders to give feedback on all aspects of the Increment, facilitating transparency, and providing valuable insights into what is considered 'done', encouraging collaboration on the progress toward the project goals.

Question 3

Following the review of an increment, the team receives several change requests. However, there’s a considerable disagreement among stakeholders about these changes. What action should be taken?

The Product Owner should consider the feedback and prioritize the changes in the Product Backlog according to the product's goals and roadmap. Hold a stakeholder meeting where each stakeholder presents their case for or against the changes, and then the entire Scrum Team votes to decide which changes to implement. This approach fosters transparency and stakeholder involvement, ensuring that all voices are heard before the Product Owner makes the final prioritization. The Scrum Team should create a separate backlog for the disputed changes and revisit them after completing the current Product Backlog. The Development Team should vote on which changes to implement first, based on their understanding and technical expertise.

Correct Answer: The Product Owner should consider the feedback and prioritize the changes in the Product Backlog according to the product's goals and roadmap.

In the Scrum framework, the Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team. This includes ordering items in the Product Backlog to best achieve goals and missions. While stakeholder input is valuable and should be considered, it is ultimately the Product Owner's responsibility to assess and prioritize the changes based on the product's goals and roadmap, ensuring that the team remains focused and effective.

🎓 Unlock Premium Access

Certified ScrumMaster + ALL Certifications

🎓 Access to ALL Certifications: Study for any certification on our platform with one subscription
3861 Superior-grade Certified ScrumMaster practice questions
Unlimited practice tests across all certifications
Detailed explanations for every question
CSM: 5 full exams plus all other certification exams
100% Satisfaction Guaranteed: Full refund if unsatisfied
Risk-Free: 7-day free trial with all premium features!

Start Your Free 7-Day Trial