PBI and Bug Work Flow (DevOps)

Owned by Justin Green (Unlicensed)
May 22, 2020
2 min read

The following is the suggested workflow for PBI’s and Bugs in DevOps, from New to Done.

PRODUCT BACKLOG (NEW)
All PBI's and bugs created by the product owner and team will be listed in the product backlog. Product backlog is managed, refined, and ordered by the product owner based on product design and development priorities. All items listed should be clearly linked to a business outcome via Epics and Features.

New product backlog items are not ready for sprint until the scope, acceptance criteria, effort and business value are discussed with and agreed upon by the team.

READY FOR SPRINT (APPROVED)
Item has a clear description, acceptance criteria, business value, and work-effort estimate. Item is now sprint-ready and can be added to the Sprint Backlog during the next Sprint Planning event.

SPRINT BACKLOG (COMMITTED)
Bugs and PBI's in this state are being actively worked on by the Scrum Team during its current Sprint. Team should always work on the highest priority Bug or PBI, shown at the top of the Sprint Backlog, to ensure that delivered business value is maximized for the sprint.

When all acceptance criteria and Definition of Done are met:

  • Add "VERIFY" tag to ticket to have P.O. verify that ticket has met Definition of Done.

  • Set PBI/Bug state to Done.

DONE
Items set to Done are assumed to have met all acceptance criteria. P.O. will verify that the definition of done was met for the PBI or bug. If any issues are found after the ticket is set to Done, the P.O. will create a new related Bug or PBI and discuss with the team immediately or at the next Sprint Refinement/Planning session.