Secret ingredients to quality software


Do you know the 3 steps to completing a PBI?

Created on 11 Feb 2016 | Last updated by Sebastien Boissiere on 12 Oct 2020 10:13 PM (6 months ago)

The lifecycle of a PBI can be broken down into 3 steps:

1. Ready

  1. Take the next PBI that was approved by the Product Owner
  2. Is the PBI ready? Check your PBI against your Definition of Ready. "Ready" PBIs must have Acceptance Criteria. A good Definition of Ready also encourages a test-first mentality in requirements e.g. Use Spec Flow (Given, When, Then) and/or create Test Cases and Test Steps first.
  3. Attach and copy the Product Owner's email into the Acceptance Criteria (as per Do you attach and copy emails to the PBI?).
  4. Email notification to the Product Owner - use the @ mention rule
  5. Break down your PBI into tasks.
  6. Don't forget to make a task for testing! (So that it is visible in the task board). Note: You can also customize the kanban board by adding a new column for testing, but we recommend adding a testing task to the PBI instead.

KB customize board columns
Figure: Adding a new "Test" state. This is only visible in the Product Backlog and not the Sprint Backlog

Testing task
Figure: Testing Task added to PBI. This is the board the team will use for 90% of the Sprint, so testing should be clearly visible here

2. Code

  1. From the PBI, create a new branch (so that your work is automatically tagged to the PBI)
  2. On the Kanban Board, move your Task into "In Progress"
  3. Checkout your new branch and start coding!
  4. Code, code, code… (Red, Green, Refactor)
  5. Push your changes, open a Pull Request
  6. If you want feedback early, record a Done Video. E.g. Snagit

3. Done

Is the PBI "Done"? Check your Definition of Done, and then:

  1. Open a Pull Request
  2. Get another engineer in your team to do an "over the shoulder" check of the code
  3. Use Microsoft's "Test and Feedback" Chrome extension to test the app
  4. Make changes based on feedback (and then get more feedback)
  5. Complete the Pull Request! Merge changes to master, this automatically deploys (to either Test, Staging or Prod based on process maturity)
  6. Email notification to the Product Owner – send a Done Email (reply to the original). Big items should have a Done Video
  7. Check the Acceptance Criteria for notes about email attachments (as per Do you attach emails to the PBI?).

Congrats. Your PBI is now ready to be demonstrated during your Sprint Review! (Note: This is also the same process you follow for a Bug work item)

Good Figure: This image includes all the important steps in a PBI lifecycle. Print this "SSW 3 Steps to a PBI pdf" and put it on your 'War Room' wall

Adam CoganAdam Cogan
Eric PhanEric Phan

We open source. This page is on GitHub