Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

3-steps-to-a-pbi - make it more generic and add seo #8513

Merged
merged 1 commit into from
May 8, 2024
Merged

3-steps-to-a-pbi - make it more generic and add seo #8513

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 13 additions & 12 deletions rules/3-steps-to-a-pbi/rule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,10 @@
---
type: rule
title: Do you know the 3 steps to completing a PBI?
seoDescription: Master the 3 essential steps of PBI management with SSW's expert
guide. From readiness to coding and finalization, streamline your Agile
processes for maximum efficiency. Learn more and enhance your project
management skills today.
uri: 3-steps-to-a-pbi
authors:
- title: Adam Cogan
Expand All @@ -24,9 +28,7 @@ redirects:
created: 2013-08-30T06:33:21.000Z
archivedreason: null
guid: 1de9df77-9b69-4242-b648-e08e5980e9a6

---

A 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:
Expand All @@ -52,21 +54,20 @@ You have a backlog of PBIs (tasks, features, and fixes) which are already priori

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](/acceptance-criteria).

1. From the PBI, create a new branch (so that your work is automatically tagged to the PBI)
2. On the Sprint board, mark your task as into "In Progress"
3. Checkout your new branch and code, code, code... (remember to [Red, Green, Refactor](/reply-done-plus-added-a-unit-test))
4. Open a Pull Request and get another engineer in your team to do an ["over the shoulder"](/over-the-shoulder) check of the code
5. Record a [Done Video](/record-a-quick-and-dirty-done-video) so you get your ducks in a row for the explanation to the Product Owner, and so they give you earlier feedback
6. Make changes based on feedback (and then get more feedback)
7. Check your [Definition of Done](/definition-of-done) and complete the Pull Request!
8. Deploy your code 🚀
1. On the Sprint board, move your PBI into "In Progress"
2. Create a new branch and code, code, code... (remember to [Red, Green, Refactor](/reply-done-plus-added-a-unit-test))
3. Open a Pull Request and get another engineer in your team to do an ["over the shoulder"](/over-the-shoulder) check of the code
4. Record a [Done Video](/record-a-quick-and-dirty-done-video) so you get your ducks in a row for the explanation to the Product Owner, and so they give you earlier feedback
5. Make changes based on feedback (and then get more feedback)
6. Check your [Definition of Done](/definition-of-done) and complete the Pull Request!

### 3. Done

This should be easiest part!

1. Reply 'Done' inside the PBI and also in the email thread, as per [when to send a 'done' email in Scrum](/done-do-you-know-when-to-send-a-done-email-in-scrum)
Note: Remember to [close PBIs, tasks and goals with context?](/close-pbis-with-context)
1. Make sure your code is deployed 🚀
2. Reply 'Done' inside the PBI and also in the email thread, as per [when to send a 'done' email in Scrum](/done-do-you-know-when-to-send-a-done-email-in-scrum)
Note: Remember to [close PBIs, tasks and goals with context?](/close-pbis-with-context)
3. Close the PBI

Congrats, your PBI is now ready to be demonstrated during your Sprint Review!
Expand Down
Loading