How track backlog items origin using scrum?

Question

I would like to track, for each backlog item, which event originated it. For instance: "Original briefing", "Meeting Jan", "Meeting Feb" ...

Using scrum, what is the correct way to track the origin for each backlog item?

I'm using visual studio online to manage my scrum project.

Answer 1

Scrum says nothing about how to track where backlog items come from. In fact, relatively little is said in the Scrum Guide as to what information should be included in a Product Backlog Item and how that information should be formatted. A Product Backlog Item is required to have a description, an ordering, an estimate, and a measure of value.

I've never used the Visual Studio project management tools, but nearly every other issue tracker that I've used allows for a textual description of the issue and you can put metadata about the source in there. Some tools allow for "commenting" on issues, and that might be suitable since it's still tracked, but not as in-your-face as the description. Others allow you to customize the fields and you can add people or events associated with a given backlog item.

I would wonder if this is necessary. If this information isn't necessary, it is wasteful to gather, store, and deal with it for every ticket. Although relatively easy to do, if it doesn't add value to you or your customers or allow you to meet some kind of contractual or legal obligation, you shouldn't be doing it.

Answer 2

If you prescribe to the format I've seen many user stories follow:

As as... I want... so that...

You can usually get at least some idea of where the backlog item came from.

Beyond that, this is often covered in the grooming/planning session. If you're unsure where a task came from (and need to know in order to proceed), keep it on the backlog and groom it before adding it to a sprint.