How to Create PBI and Bug Templates in DevOps

Team Fusion has multiple POs for the SCEM project and was having trouble with the consistency of the PBIs. To help with this, we created PBI and Bug Templates.

Screenshots

PBI Template
Bug Template

Content

Most of the content was taken from the Agile CoE’s Scrum Ceremonies Cheat Sheets (see attachments).

 

 

PBI Fields

Field

Value

Field

Value

Description

As a role, I want to action, so that benefit.

Delete this line and everything below.

PBI Examples

  • As a recruiter, I want to post new jobs, so that applicants can find those jobs via search.

  • As a job seeker, I want to limit who sees my resume, so that I have privacy.

Notes

  • Include screenshots and links whenever possible.

  • PBI Template taken from: https://www.visual-paradigm.com/scrum/3c-and-invest-guide/

  •  

    Follow the INVEST Guidelines

    • Independent – Each User Story should represent a distinct and independent set of business values such that, were it released on its own, it would deliver incremental value over the previous state.

    • Negotiable – While the end-goal may be clearly described, the methods by which that goal is achieved should be negotiable – between the Product Owner and the Development Team, the Product Owner and the Customer, or any other involved stakeholders – so as to prevent unrealistic constraints on the feature or functionality.

    • Valuable – The business value of any User Story should be readily recognizable by reading the story, and each story should represent some sort of value to a specific user type.

    • Estimable – We must have enough information that we can properly size a story so that we may properly plan and commit to our work. (But no more!)Small – User Stories should be small enough that they are able to be completed within a sprint.

    • Testable – All members of the team need a clear and precise way to verify whether or not a User Story has been completed.

Acceptance Criteria

This PBI will be considered complete when:

  1. Acceptance Criteria 1.

  2. Acceptance Criteria 2.

  3. Acceptance Criteria 3.

  4. Etc.

Delete this line and everything below.

Notes

  • All members of the team need a clear and precise way to verify whether or not a PBI has been completed.

  • Include screenshots and links whenever possible.

Bug Fields

Field

Value

Field

Value

Repro Steps

When I action, the expected result is expected, but the actual result is actual.

Links

  1. Copy and paste the URL(s) from your browser's address bar when the error occurred.

Screenshots

  1. Please include at least one screenshot; more are always helpful.

Reproduction Steps

  1. If not obvious from the Links and Screenshots above, please include steps on how to reproduce this bug.

System Info

Acceptance Criteria

This PBI will be considered complete when:

  1. Acceptance Criteria 1.

  2. Acceptance Criteria 2.

  3. etc.

How to Capture a Template

  1. Create a new PBI or bug and fill it as desired.

  2. Click the following sequence:

How to Edit a Template