Skip to content

SMART Product Backlog Items

In a second post on writing a good quality PBI we’re looking at the SMART acronym.

Where we used INVEST to write an effective User Story and Acceptance Criteria, consider using SMART holistically as a final check. Cross-referencing the elements of a PBI such as DoD, the team’s velocity and the iteration goal.

Remember, we are not going to produce any other documentation for this PBI and everyone is able to see what we’ve written. Make it count! When clarifications are needed, don’t start an email thread or chat, record your conversation in whatever issue tracker you use. (Jira, Azure DevOps, or even a Post-It note stuck on an index card!).