In our teams we are having the problem that our tests are performed a bit after the actual development is done. The effect of this is that the burndown is not burning, since it is based on the fact that the issues needs to be CLOSED in order to give burn on the burndown.
We have a lot of things that are DONE but they are not tested until x days ahead.
Is there any way to reconfigure the Agile Gadget to burn down on DONE instead of CLOSED status and give the developer part and maybe the testpart separately?
check this post. It may help you.
AFAIK the Greenhopper deinition of done is defined by the rightmost colum of your board. Maybe you could map the DONE status to that column aswell.
So, if we were to map "Resolved" to the Closed column (where status Closed is mapped) the Agile Gadget would burn when a status would be set to Resolved?
But how ever I am trying to figure this out, I end up with having TEST one step back in the process? "To-Do : In Progress : Test : Closed/Done"
That would mean that an issue needs to be moved back in the board to be tested after it has been resolved?
And, is this really applicable in the Classic Agile Gadget? Not just the Rapid Board Scrum Gadget?
Maybe you should split your board into one board for development and one for testing. The rightmost column of the boards define the done status for the burndown, so you can generate a burndown for development and (from the other board) a burndown for testing.
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot