Potentially Shippable

5 minutes 5 Questions

Potentially Shippable is one of the key requirements of the Scrum guide for a Product Increment. Every Increment is additive to all prior ones and must be 'Potentially Shippable', which means it must be in useable condition and meet the Scrum Team’s definition of 'Done'. This does not mean that it must be shipped, but rather it should be capable of being shipped. Making each increment potentially shippable gives the Product Owner the decision to release it and create value at any time.

Guide: Potentially Shippable Product Increment in Scrum

Potentially Shippable Product Increment (PSPI) is a core concept in Scrum framework, it refers to an increment of work that is potentially releasable to users. In other words, it is a fully functioning part of the final product that provides some kind of value to its end users.

Why it is Important: Ensuring each increment is potentially shippable forces Scrum team to constantly align their work with business value and user needs. It helps in maintaining quality as a priority and frequent delivery of valuable product to stakeholders.

How it works: In Scrum, each sprint ends with a potentially shippable product increment. This is not necessarily a product that must be shipped, but it should be at a stage where shipping would be an option.

Exam Tips: Answering Questions on Potentially Shippable: Understand that PSPI does not need to be shipped but it must be in a condition where it could be, if needed. Recognize the role of the definition of 'Done' in determining what 'potentially shippable' means. Continually tie back the concept of PSPI to delivering value to the customer and aligning work with business objectives.
Test mode:
Start practice test

PSM I - Potentially Shippable Example Questions

Test your knowledge of Potentially Shippable

Question 1

You are a Scrum Master for a software company. The Sprint is coming to an end. The team only completed 50% of the sprint Backlog items but everything completed is well-tested and working do you consider it potentially shippable?

Correct Answer: Yes, as long as the completed items meet the Definition of Done and deliver value, they are potentially shippable.

According to Scrum principles, the main criterion for an increment to be considered potentially shippable is that the work done meets the Definition of Done and is of high quality, not necessarily that all items in the Sprint Backlog were completed. It emphasizes delivering value and maintaining quality rather than completing every planned item. Thus, if the completed items are well-tested, working, and meet the Definition of Done, they can be considered potentially shippable despite not all backlog items being completed.

Question 2

The Scrum Team has reached the end of the Sprint, but one of the key features is developed but not well documented. What should you do?

Correct Answer: Do not consider the feature to be potentially shippable until the documentation is complete.

In Scrum, a feature can only be considered potentially shippable if it meets the definition of 'Done.' This definition typically includes necessary documentation to ensure the product or feature can be released to users or maintained properly. Answers suggesting deferring documentation or treating it as a separate backlog item misunderstand the importance of completing work within a Sprint to meet the definition of 'Done.'

Question 3

As a Scrum Master, you realize that one of the features developed during the Sprint is not integrated with the rest of the system. However, it is functional and tested. How would you label this feature at the end?

Correct Answer: Not Potentially Shippable

For a feature to be considered Potentially Shippable, it must be fully integrated and meet the Definition of Done, which includes being functional, tested, and integrated with the rest of the system. If the feature is not integrated, even if it's functional and tested, it cannot be considered Potentially Shippable, as it does not meet all the criteria for completeness. The incorrect options shift focus to terms like 'Technical Debt', 'Definition of Done', and 'acceptance criteria' which, while related, do not correctly address the issue of integration with the system being a requirement for Potentially Shippable Product Increments.

More Potentially Shippable questions
15 questions (total)
Start 15 question test

Other Product Increment in Scrum concepts

Continuous IntegrationIntegrationProduct Backlog RefinementProduct Increment ScopeReview and RetrospectiveScrum Artifacts TransparencyScrum Team CollaborationSustainable PaceTechnical Debt
All Product Increment in Scrum questions · PSM I practice test