I've been casting about though for things that I can measure with Mingle that tell me something about the higher level state of the project. Mingle easily gives us a clear picture of release and iteration progress, and obviously measuring velocity is then a breeze. But what about above that level? In particular, since we're working on a open-ended project, there's no ultimate finish line, so there's no firm 'distance yet to cover' in terms of either features or time. This is as much a project management question as a Mingle one, but I thought I'd see if anyone is using Mingle to ask useful questions at that level for such a project.
A couple I've thought of are:
- New tickets added to backlog vs tickets closed, example
- Rate of new defects vs new enhancements
Thanks for any input.
Chris
Comments
2 comments
Hi Chris,
Great question. The Mingle team is looking at some of these higher-level concepts for an upcoming release, so any input on what people are looking for is appreciated.
The daily history chart that was introduced in 3.2 should be able to help answer the two examples you mentioned. For example, the following daily history chart is an example we used on the Mingle team's Mingle project to chart all bugs vs. closed bugs for four years of Mingle data:
{{We have since added a story (not yet implemented) to allow the "end-date" parameter to be TODAY so that the report will stay up to date.
-Jay
We're still on 3.1, I'll definitely take a look when we upgrade.
Please sign in to leave a comment.