Which Scrum Team member should set PBI and Bug work item states?

Which Scrum Team member should set PBI and Bug work item states?

Posted by richard | June 8, 2012 | Scrum, TFS 2010, TFS 2012

This is a fairly common question, usually by teams new to Scrum. The Scrum Guide clearly identifies the roles and their responsibilities. Team Foundation Server does not. It only identifies security groups and permissions.

Teams that have been using Scrum for a while should answer: “Let the team decide”. I’m good with that answer.

For team members that don’t yet know where the rules of Scrum stop and self-organization begins, I provide the following guidance on who should “flip the switch” at each state transition of a PBI or Bug work item type:

  • Anybody on the Scrum Team (or perhaps beyond) should be able to create a PBI or Bug work item (state: New)
  • The Product Owner should be the one to accept a PBI or Bug (state: Accepted)
  • The Product Owner should be the one to remove a PBI or Bug (state: Removed)
  • Anyone on the Scrum Team can set the state to Committed (so long as the Development Team forecasts that work for the Sprint)
  • Anyone on the Scrum Team can set the state to Done (so long as the Product Owner accepts it)

Try this for a while. Get good at Scrum, TFS, and how they work together. As you retrospect and improve, your team will come up with a better approach.

Related Blogs

Posted by richard | March 15, 2017
Create a Professional Scrum process
Visual Studio Team Services' customization capabilities are to a point now where I can write this blog post ... as a rebuttal to any earlier post of my own. Since...
Posted by richard | August 15, 2016
Ordering the Product Backlog by ROI
The Scrum Guide says that the Product Owner is the sole person responsible for managing the Product Backlog and that Product Backlog management includes ordering items in the Product Backlog...
Posted by richard | June 13, 2016
Stakeholder Traceroute
I'm always amazed at how difficult and even impossible it can be for stakeholders to get their ideas into some product backlogs. I've started asking teams to run a stakeholder...