Discover cumulative, sum of all completed Product Backlog items, Done and releasable, optional release decioded by PO

Increment description:

  • An Increment is a sum of all completed Product Backlog items at the end of a Sprint.
  • Each Increment must be Done and releasable.
  • The Product Owner may or may not release a certain Increment, but it should be releasable (shippable).
  • The number of stories in the Product Backlog decreases Sprint by Sprint, as the number of features in the Increments increases.
  • The Increment concept is cumulative meaning that each Increment also contains the features of the previous ones.

Get the book

Definition of Done

Discover shared understanding of done, decided by Scrum Team, might have mulitiple DOD across different team of same project,

DOD description:

  • There should be a shared understanding of what it means for a piece of work to be Done.
  • This definition of Done must be discussed and agreed upon by the Scrum Team at the beginning of the project so that future Increments would be releasable.
  • When multiple Scrum Teams are working on a single project, it might not be possible to use the same definition of Done for all teams (might be working on items of different natures) so¬† each Scrum Team will define its own definition of Done and delivers its items based on that definition.
  • The integration of those definitions of Done should be capable of creating a potentially releasable Increment in the project level.

Get the book

Monitor Product Progress

Discover Product burn-down chart, work left/time, once per Sprint Review, amount of remaining work, uniform distribution line

Monitoring Project Progress description:

  • The Project burn-down chart helps visualize progress of the whole project
  • The Product Owner is responsible to monitor the progress of the whole project toward its goal.
  • This should be done at least once per Sprint Review.
  • The Product Owner determines the amount of remaining work and compares it to the remaining work of the previous Sprints, and forecasts the completion date of the project.
  • All stakeholders should have access to this information.
  • The project burn-down chart shows the amount of remaining work, instead of the amount of completed work; therefore, the line for actual performance goes downward as we proceed and the faster it goes down, the happier we will be!
  • The vertical axis (remaining work) shows the amount of work (which is a sum of all the estimates for each item in the Product Backlog), and the horizontal axis shows the amount of time passed from the beginning of the project or the number of Sprints passed.
  • We usually add another line to acts as our planned progress which represent the uniform distribution of the volume of the work across the initially estimated number of sprints

Get the book

Monitor Sprint Progress

Discover Sprint burn-down chart, Development Team responsibility, likelihood of achieving the Sprint Goal , one per standup

Monitoring Sprint Progress description:

  • Besides the monitoring done for the whole project, we should also monitor the progress of each single Sprint throughout its life.
  • This is the responsibility of the Development Team.
  • It should be done at least once per Daily Scrum.
  • This information is used to calculate the likelihood of achieving the Sprint Goal and completing all items of the Sprint Backlog.
  • The Sprint progress information can be represented by a burn-down chart, and this chart can be a part of the Sprint board, where everyone can see.

Get the book