TFS Scrum - if bugs and PBIs are treated on same level, shouldn't their work item states be the same?

Question

We are using the scrum template for TFS 2013. Product Backlog Items and Bugs are at the same 'level', so they are both viewed on the backlog and tasks are created as children underneath. Why do PBIs have the states: New, Approved, Committed, Done, Removed, while Bugs have the states: New, In Progress, Done, Closed (which is the same as tasks)?

By treating PBIs and Bugs essentially the same, I would expect that they should have the same states. I'm not sure what 'Done' is supposed to mean as opposed to 'Closed'. I find it confusing that tasks and bugs can be marked 'Done', which is not the same as a PBI marked 'Done'.

I want to change the names of the states for the the PBIs, bugs, and/or tasks to use more consistent naming conventions, but I think I may be misunderstanding what the terms mean.

Answer 1

As Cece mentioned, the out of the box states in Scrum between PBI and Bug are similar. You can use witadmin to change the states of your Bug work item type to match PBIs.

Another option is to use the Kanban board, where you can create a set of columns and map each column to a state of each work item type.

Answer 2

I'm afraid your Scrum Process Template has been customized before. In the default Scrum process template of TFS 2013, PBI and Bug do have the same states: New, Approved, Committed, Done, Removed, while Task has the states: To Do, In Progress, Done, Removed.

The following diagrams show the typical forward progression of PBI, Bug, and Task work items used to track work and code defects for TFS default Scrum process templates:

PBI:

Bug:

Task: