Your browser does not support JavaScript! Potentially Shippable Product Increment - Scrum Inc
  • Google
  • RSS

Increment or Potentially Shippable Product

An Increment (sometimes referred to as a 'Potentially Shippable Product') is the value delivered for the customer via the Product Backlog Items completed during a Sprint. Each Increment should interface seamlessly with all prior Increments and stand alone as a distinct addition of value to the Product. While more than one Increment may be created in a Sprint, all work must meet the Definition of Done to be considered complete. Last but not least, each Increment represents a concrete step towards realizing the Product Goal.

Estimated time for this course: 1 minute
Audience: Beginner
Suggested Prerequisites: Scrum Framework

Upon completion you will:

  • Understand what is a Potentially Shippable Product increment
  • Know why you deliver Potentially Shippable Product every Sprint
  • Qualify for Scrum Alliance SEUs and PMI PDUs. See FAQ for details
Potentially Shippable Product Increment Overview:

Teams can gather feedback fast and accelerate their creative process by providing users with a working product. To achieve the feedback loop every Sprint, the team delivers an increment at each Sprint Review. To ensure functioning products at the end of each sprint, it is important to remember the following key points:

- A team should be made up of cross-functional members who possess all skills needed to fulfill the Sprint Backlog
- Quality Product Backlog items with explicit Definitions of Ready and Done are present
- Definition of Done is the commitment of the Increment
- A Product Owner can vertically slice backlog into functional aspects and prioritize it based on customer value

Commitment: of the Increment: Definition of Done

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the Definition of Done, an Increment is born. The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration. If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. The Developers (anybody who is working on the sprint increment) are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.

6 Agile Ways To Increase Employee Engagement

employee support

Organizations who utilize Agile ways of working experience a 20-30% improvement in employee engagement. Engage, Equip & Empower your employees.

learn more button click here

Topics:

Stay Connected

Stay Connected

Sign up to receive the latest Scrum news, special offers, and our monthly newsletter.

You have Successfully Subscribed!

Shares