When to close stories- to have a usefull burndown


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?

1 answer

1 accepted

1 vote
Accepted answer

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.

That was it!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,008 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you