#133 – Delivery Every Sprint

The Scrum Guide defines the Sprint as “the heartbeat of Scrum, where ideas are turned into value” in the form of one or more ‘done’ Increments of the product. In many organizations, Scrum and Sprints are used as a way of delivering increments (with a lowercase ‘i’) of the product that are not value-adding—i.e., they break up a big project into blocks that are not releasable or value-adding on their own, so the actual release only happens in the end when all blocks of the product have been built.

When slicing a large product development effort (or ‘project’), have a think about what problem you’re trying to solve and identify an MVP that actually solves part of it. Thus, it’ll be easier to slice Increments, so they can be delivered throughout Sprints, which ensures that empiricism is supported, and decisions are based on the feedback at, e.g., Sprint Reviews.