TFS – PBI ‘Done’ state

Last post 07:18 am March 31, 2014
by Martin Hinshelwood
4 replies
Author
Messages
06:36 pm March 27, 2014

We are using TFS. When we move PBI’s from the Product Backlog to the Sprint Backlog we change the state from Approved to Committed.

When do we have to change the state to Done?
In the Sprint Review meeting when the product owner declares the PBI Done?
Or during the sprint when all tasks for the PBI are Done?

05:49 am March 28, 2014

Hi Franck,

We have 2 sorts of “done”.

“IT Done” which is done according to the teams Definition of Done. And we have “Business Done” when it is approved by the Product Owner. What you’ll see is that it will usually take “IT Done” to iterate a couple of times before it is “Business Done”.

Can imagine there are difference ways, but this is how we have evolved to as team.

10:55 pm March 30, 2014

In our case PBI is done when the PO said so. :-)

11:08 pm March 30, 2014

I would go with Josh, PO has the final say in marking a PBI as DONE. However team should not wait till sprint review for doing a demo to PO, they should do it as soon as they mark all tasks as completed so that any quick feedback ca be incorporated. The sprint review is not just for PO but for other stakeholders, your customer and end users etc.. what if one of the critical end user was expecting something different and it could have been implemented if a pre-review walk thru had been given to PO

Cheers
Sanjay

07:18 am March 31, 2014

You should move your Item to Done when it meets your pre-agreed definition of Done and acceptance criteria are met. As the PO is both responsible and accountable for the understanding of the PBI's by the Development Team these should ~accurately represent what they want.

I prefer for the Development Team to be given the freedom to innovate uninterrupted within the bounds of the Sprint Backlog & Sprint Goal. At the Sprint Review, or even during the Sprint, the PO's feedback can be expressed as PBI's and ordered on their backlog. If something is really important to change they can have a conversation with the Development Team and see if the change can be swapped in for something that they have not started yet. There would, however, be no guarantees. If the market or idea has changed that significantly the PO is free to cancel the Sprint and start over.

I love having the PO involved all the way thorough the Sprint, however the Development Team needs the gumption to be able to say 'no' for this to work.