Rules

Secret ingredients to quality software

Edit
Info

Do you always work in priority order, unless there’s a good reason not to?

Created on 08 Nov 2012 | Last updated by Tiago Araujo on 08 Nov 2012 03:17 PM (over 8 years ago)

Although the team will always strive to complete all the items on the sprint backlog within the sprint, it’s not uncommon for them to not finish all of them. If this is the case, you want to at least make sure that the PO's (Product Owner)’s most important items are done.

Whenever you are choosing your next task, always work from the top down, only skipping items if there is a dependency or another good reason why a lower item needs to be done first.

priority order
Figure: a good example of a team working in priority order. Mid-way through the sprint, the top items have been completed, the middle items are being worked on, and the bottom items have yet to be looked at

Damian BradyDamian Brady

We open source. This page is on GitHub