Create a grouping / categorising mechanism for product backlog
There isn't a good way to group or categorize items on the product backlog at the moment. Especially when starting up a new project, this means the backlog is huge and you'll probably need some sort of way to keep track of everything. There's areas, but those don't show on the product backlog. There's linkin items, but that also affects prioritising in way you don't want it to.
Some kind of tagging system would be nice. Suppose you could tag your workitems with categories (the way SharePoint tagging works is quite powerfull). Those categories could then be used to filter, search or group items on the product backlog. Product owners would be pleased I think, since this makes it a lot easier to keep track of everything.
In TFS 2013 we have added the portfolio management capability to TFS, which enables your requested scenario. If you want to learn more about portfolio management, see http://msdn.microsoft.com/en-us/library/vstudio/dn237341.aspx.
In addition you can also use the work item tags to categorize your items further. We have just announced the ability in VIsual Studio Online to query on tags, which makes it even more valuable.
TFS Program Manager
Kaitlyn Moore commented
This is not sufficient -- because of the way the Epic/Feature/Story tree is independent of the backlog ordering view, I'm still unable to see groups of backlogs in a view where I can work in priority order. Beyond that, we use Tags for releases, since a release is not always correspondent to a set of iterations, when we have a multi-branch environment.
Please create a grouping/categorizing method in the product backlog view for tags. As a product owner, I would love to view my teams backlog, grouped by Tag. This would enable me to work with my stakeholders through each backlog item, in logical conceptual chunks.
Fokko Veegens commented
I think this is implemented right now in TFS 2012 Update 2 (which is about to go live...)
Stefan Rauch commented
Richard Hundhausen commented
While you can't group or filter by them, you can add additional columns, such as the area path, to the Backlog. Check out http://msdn.microsoft.com/en-us/library/hh739073(v=vs.110).aspx#columns for more information.
Fokko Veegens commented
I agree on being able to see Areas in the product backlog. As a user I want to be able to configure the columns showed in the product backlog, so I can add the Area path.
Dylan Smith commented
If we adopt a tagging system, I'd like to see things like Areas and Iterations become just another tag also (hierarchical tags?) for consistency and simplicity.
(This gets my vote too - but I have no votes)
The reason I want it is to enable me to use TFS to create a roadmap for a project.
Currently there is no option for creating a roadmap containing the large stories (“Epics”)
So please on the PBI add checkbox “Epic”. Even better give us the ability to add tags (with a built in one called “Epic”)
Then back on the backlog, in the left navigation, add a node “Roadmap” that shows “Epics”. This will be useful to put on the boardroom wall to help implement this rule http://rules.ssw.com.au/Management/RulesToBetterScrumUsingTFS/Pages/WarRoom.aspx
This has my vote as well but I am out of votes...
Having Areas on the Product Backlog as a filter option would be great