Discover Increment, sum of all completed PBI, updated version, request changes, sprint goal, cancel a Sprint

Sprint description:

  • Each Scrum project delivers the final product after a number of cycles, which are called Sprints.
  • An Increment is the sum of all Product Backlog items completed so far in a project and this Increment keeps getting bigger after each Sprint.
  • An Increment is developed in each Sprint, which is a potentially releasable part of the final product.
  • An Increment is the updated version of the previous Increment with new features and functionalities, which may or may not be actually released (put into use), but should always be potentially releasable.
  • Customers usually request changes when they see the Increment (during the Sprint Review), and we note these new requests in the Product Backlog.
  • Sprint is a time-boxed event, with a fix duration (set at the beginning of the project and do not change it frequently or occasionally). Sprints are usually fixed for one month or less (usually 2 to 4 weeks) as any longer would increase risk and complexity,
  • The sprint goal is to deliver the final product item by item, inside the Sprints; we do not want to split a single Product Backlog item among several Sprints.
  • The Product Owner has the authority to cancel a Sprint, usually when the Sprit Goal becomes obsolete, due to changes in the Product Backlog, strategies or approaches. When a Sprint is cancelled, the items that are Done will be reviewed and accepted, and the rest of the items (not started or partly complete) will be put back into the Product Backlog to be done in the future.

Sprint rules:
Scrum have a set of constraints designed to make it possible to focus and get things done including:

  • The Sprint Backlog items should not be changed once the Sprint is started
  • The Sprint Goal should not be changed.
  • The composition of the Development Team should not change during a Sprint.
  • The Product Owner and the Development Team might try to clarify and re-negotiate the scope as more is learned about the items to be delivered, but will not change the Sprint Backlog.
  • Each item (story) in the Product Backlog should normally be completed in a single Sprint as this is much easier to manage.
  • The Product Owner and the Development Team select a number of items from the top of the Product Backlog, that have already been prioritized by the Product Owner, and aim to get them Done (100% complete).
  • The Sprint Backlog items should be completed matching the definition of Done when the Sprint is over, and create an Increment.
  • A definition of Done should be agreed at the beginning of the project, and no item should be identified as Done, unless it fits the definition (even if 99.999% completed) as it would not be part of the Increment and it would not be demonstrated to the customer at the Sprint Review.

Get the book

Scrum Artifacts

Discover Product Backlog, User Stories, DOR, Sprint Backlog, Increment, DOD, Product progress, Sprint progress

Scrum artifacts of management activities are created to increase transparency of information related to ]project delivery and provide opportunities for inspection and adaptation.
There are six artifacts in Scrum:

  • Product Backlog: an ordered list of everything , aka all of the stories, that might be needed in the final product
  • Sprint Backlog: selected items (stories) from the Product Backlog to be delivered through a Sprint, along with the Sprint Goal and plans for delivering the items, aka the tasks needed to complete the Sprint Goal
  • Increment: set of all the Product Backlog items completed so far in the project, up to the end of a certain Sprint
  • Definition of Done: shared understanding of what it means for a story to be considered complete
  • Monitoring Project  Progress: performance measurement and forecast for the whole project
  • Monitoring Sprint Progress: performance measurement and forecasts for a single Sprint

Get the book