In Scrum, an Increment is a concrete stepping stone towards the Product Goal. It is a forward step towards a goal or vision. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. The entire Scrum team is accountable for creating a valuable, useful Increment for every Sprint. In order to provide value, the Increment must be usable. Multiple Increments may be created within a Sprint, and the sum of the Increments is presented at the Sprint Review, thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint, and the Sprint Review should never be considered a gate to releasing value. Work cannot be considered part of an Increment unless it meets the Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality standards required for the product. The Scrum team is responsible for deciding what they need that can be considered as an Increment. The Product Increment is advantageous to all the Scrum project roles, as it helps stakeholders and the Product Owner assess the current ROI from the functionality that is attainable by the customer at each Sprint end.