Hi,
I've a question about the time you close the Stories.
To have the burn down really reflect the process of the sprint content, the stories have to be closed, otherwise the story-points wont be burned, and the burn-down want go down.
But usually the developer only sets the story to resolved and on sprint end (demo/review) the PO is closing the story when he accepts it - but doing so, will reflect in an inappropriate burn-down.
How do you handle this?
Use two boards.
The developer's board should have a last column that means "development is done" - the dev team has moved on to writing/fixing other stuff.
The PO acceptance and resolution is irrelevant to the developer's burn-down. Give the PO another board with three (or more) columns - a "development needed/in progress/tests failed" to the left, a "needs acceptance" type column in the middle and "Accepted" to the right. The burn-down on that it mostly irrelevant because it's representing testing and acceptance, not development work, but it does allow the developers to burn down properly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.