Do you know when you use @ mentions in a PBI?
  v8.0 Posted at 24/09/2020 4:43 PM by Ulysses Maclaren
When the Product Owner verbally requests a change to a PBI, how do you update the PBI to reflect the change and also keep track of the conversation?

You could send yourself a "​To Myself" email and update the PBI description accordingly, but only those people included in the email chain are aware of the conversation.

Figure: Bad Example – don't use emails to update tasks

Instead, what you should do is use the discussions feature in the PBI and mention the user using "@<username>". 
The benefits of using comments are:​

  • Quick and easy, no need to compose an email
  • History is visible to anyone looking at the PBI (with email, if you don’t cc them, they wouldn’t have a clue)
  • Easy to see all important notes/comments in one place instead of digging through email

Azure DevOps​ PBIs

Figure: Good Example – Using @ mentions in Azure DevOps discussion
Figure: Good Example – Email still gets sent to the users who are mentioned in the discussion, so they can still chime in if any details are incorrect

GitHub Issues

Figure: Good Example – Using @ mentions in Git​Hub​

Related ​Links

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address: