We are in the process of rethinking the way we use Mingle and are putting together a new Mingle Template.
I thought I would document what we have done here to see if it sparks debate or if anyone has any suggestions for improvement.
One of the issues we have had previously is that if a defect or task needed to move over to the next sprint or into the backlog, without taking the story with it, we couldn't move it.
We decided to give us flexibilty that we would seperate out the Epics and Stories from specific work items (tasks and defects... stuff the devs are working on). In effect making the Stories release agnostic.
So we have two trees in Mingle, Requirements and Delivery.
Requirements looks like:
>>>>>> Acceptance Criteria
The delivery tree looks like:
>>>>>> Work Item
So for example, if we have two defects on a story, one a blocker and one a workaround. We want to keep both but only ship the blocker in the current release. The workaround goes into a backlog but the story can still ship.
In addition to the above we then use groups and transitions to add some degree of control to the process, only allowing cards to move and transition in certain predifined ways.
Would be interested to hear people views on this and whether people see any issues with it or have better ways to model this.
All the best