Do you use meaningful PBI titles?

Last updated by Tiago AraΓΊjo [SSW] about 1 month ago.See history

Product Backlog Items (PBIs) are the cornerstone of a well-oiled project. They track features, bugs, tasks, and much more. When a developer or Product Owner is looking through the backlog, it's important that - at a glance - they can read the titles of PBIs and have a decent understanding of them.

So what separates a good PBI title from a bad one?

Video: Do you use meaningful PBI titles? | Luke Cook | SSW Rules (5 min)

Note: Usually, we use the term PBI to encompass all types of backlog items, including those related to DevOps, Trello, GitHub, or any other platform.

How to create meaningful, yet efficient titles?

Without a meaningful title, you need to drill down into the details. If your backlog is substantial, it quickly becomes time-consuming and tedious to drill into each and every item to see what it's about. Even worse... next time you visit the backlog, chances are you won't remember the details and will have to re-read every PBI again!

Fix menu bug

Figure: Bad example – What bug? How important is this?

❗️ IMPORTANT πŸ› BUG | Menu disappears on mobile devices

Figure: Good example - "Important" emoji and text to bring attention to the PBI's importance, "Bug" emoji and text to indicate the PBI type, with a clear description of the issue

❌ Don't

  • Be generic (e.g. "Fix bug in site")
  • Write a novel in the title
  • Ignore the importance of urgent PBIs

βœ… Do

  • Be specific (e.g. "{{ AREA }} | {{ BEHAVIOUR }}"). See our rule to order of instructions
  • Prefix - Identify its urgency (e.g. ❗️ IMPORTANT)
  • Prefix - Identify the type (e.g. πŸ› BUG)
    Note: Bugs are special case - they should have greater visibiliy
  • Use emojis. See our rule on emojis in Scrum

Good PBI titles examples

Using this structure: {{ EMOJI FOR PBI TYPE }} {{ BUSINESS AREA TOUCHED }} | {{ SHORT DESCRIPTION }}

Bugs:

πŸ› Newsletter form | returns HTTP 500

Features:

✨ Newsletter form | Validate email address

UI/Styling:

πŸ’„ Header | Update site header with new logo

DevOps/Infra:

πŸ‘·β€β™‚οΈ DevOps | Add ephemeral deployment slots for PRs

Urgent tasks:

❗️ IMPORTANT πŸ›πŸ‘·β€β™‚οΈ SysAdmin | Northwind app inaccessible through company VPN


Other examples:

πŸ› Invoices | Invoice totals are rounded incorrectly

βš’οΈ Infrastructure | Implement staging deployment pipeline

✨ Clients page | Add create/edit client fields

Great titles are also important on Pull Requests, and email subjects.

Emojis

Love them or hate them, emojis have become a staple in the development world. As the old saying goes... "a picture is worth a thousand words". You can use emojis (responsibly!) to categorize PBIs/Issues/PRs/Emails, as well as bring attention to important items in a way that is easily interpreted by other people.

Regardless of whether or not you choose to adopt the emoji language, you should always be mindful of the title's text.

Always ask yourself: "Can a developer (or Product Owner) interpret the task and its importance without needing to dive into the details?"

We open source. Powered by GitHub