Do you know the 3 steps to completing a PBI?
Last updated by Tylah Kapa [SSW] 3 months ago.See historyA PBI (Product Backlog Item) is a term commonly used in Agile project management and software development to represent a unit of work or an item in the Product Backlog, which is a prioritized list of features, enhancements, or fixes to be addressed in a project.
From a developer's viewpoint, the lifecycle of a PBI can be broken down into 3 steps:
Before it's ready
Got an email with tasks or bugs? Add them to the Product Backlog as PBIs as soon as possible!
Next, check the PBI against the Definition of Ready.
1. PBI is Ready
You have a backlog of PBIs (tasks, features, and fixes) which are already prioritized and approved by the Product Owner
- Take the next PBI in the list by assigning it to yourself
- Break down that PBI into clear and actionable tasks
2. Time to Code
This step depends on the complexity and nature of the task, especially if the PBI involves intricate coding or extensive testing to meet the defined Acceptance Criteria.
- From the PBI, create a new branch (so that your work is automatically tagged to the PBI)
- On the Kanban Board, move your Task into "In Progress"
- Checkout your new branch and code, code, code... (remember to Red, Green, Refactor)
- Open a Pull Request and get another engineer in your team to do an "over the shoulder" check of the code
- Record a Done Video so you get your ducks in a row for the explanation to the Product Owner, and so they give you earlier feedback.
- Make changes based on feedback (and then get more feedback)
- Check your Definition of Done and complete the Pull Request!
3. Done
This should be easiest part!
- Close off the PBI by replying 'Done' inside the PBI and also in the email thread. As per when to send a 'done' email in Scrum
Congrats, your PBI is now ready to be demonstrated during your Sprint Review!