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.

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

XS✔ ◾ [⚠️ TESTING Don't merge] #7362

Closed
wants to merge 4 commits into from
Closed
Changes from 2 commits
Commits
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
2 changes: 1 addition & 1 deletion rules/3-steps-to-a-pbi/rule.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ 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.
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.

JackDevAU marked this conversation as resolved.
Show resolved Hide resolved
From a developer's viewpoint, the lifecycle of a PBI can be broken down into 3 steps:

Expand Down