I am using the Mingle Agile Hybrid template for my Mingle projects.

Currently I am creating a separate project for each of our Project namespaces. These namespaces are created to contain aspects of our development that have different scope, team composition or velocities. This produces different Mingle projects such as MYCO.Frameworks.Messaging, MYCO.Frameworks.Workflow, MYCO.Application.Client, MYCO.Application.Server, MCYCO.Shared.Utility, etc.

However, I frequently need to represent dependencies between cards in these different projects and track them within a single Mingle (jingle?) project. However the head of the trees in each project seems to reference the project as root. That is, there is a ceiling above the Feature level in the card hierarchy.

There doesn’t seem to be a way to represent all of these namespaces within a more consolidated project with its sub-namespaces as separate subprojects.

I would like to be able to use the tree configuration mechanism to define a structure like: [root project] /sub-project /maybe another sub-project … /Feature/Story/Scenario/Test

Alternatively, I would like to be able to define dependencies between cards in different projects and report on different projects in a consolidated manner.

Nice to have: As a third item, I’d also like to configure a tree to allow for multiple types of cards at each level so I could do something like this: /feature/story/Scenario or Task/Test

Thanks,

Kimball

As a stop-gap, I attached tags to all the cards referencing the different namespaces within a single Mingle project (call it a ‘pr-ingle’?).

At least I can see things if I have to, but how does Thoughtworks handle it?

Thanks,

Kimball

So what would happen if I added a new Card Type for Projects and Sub-projects?

And then I added a new ‘Project tree’ for project/sub-project organization. And configure the Tree to have a card hierarchy like Project\Subproject\feature\story\scenario\task?

Then I start thining maybe it would be reasonable to add a Team card type and a Team Tree and create another layer on top of the basic feature\story\scenario\task hierarchy.

Isn’t this somehow ‘breaking the model’ with regards to the Agile and Scrum templates?

Too much zingle in the Mingle?