How to set up Feature Releases/Sprints using Variables/Cards/Properties?




  • Avatar
    Suzie Prince

    Hi Victor

    Welcome. Thanks for your post.

    Have you taken a look at any of the templates that are shipped with Mingle? If not I suggest you take a look at the Scrum template. This has a similar structure to that that you describe and represents one of our suggested configurations but can be modified to more closely fit your needs.

    I also suggest you take a look at this help about Exploring Mingle as it explains more about how the card metaphor works and how you can use cards to represent releases.

    Please take a look and let us know if you need further assistance.


    - Suzie

    Comment actions Permalink
  • Avatar

    Victor, one small tip for you. You can group cards in a grid view by their assignment in a sprint tree. The trick is to make sure the grid view is using your sprint tree, and then filter the view so that it shows only the story cards.

    The "group by" drop down will now show a property which is the relationship property. You need to group the story cards by the sprint card they are parented to. So that relationship will appear something like "Sprint Planning - Sprint".

    The cards will then be grouped by their parents (the Sprint Cards) in Grid view.

    Use the "Lane Headings > SUM" of Effort Points, and you can see your total work currently assigned to each sprint. I also add a sprint card called "Backlog" and add it to the grid. Then pulling a story off the Backlog and assigning to a specific sprint is a breeze. You can also use the drag and drop lane prioritization to manage your backlog this way.

    Suzie is right, I think the Scrum Template might have a view similar to this, but this is how you can set it up yourself. Sounds like you might also want a higher-level grid that shows the status of releases in your project, and then Lane Headings that SUM a rollup of all effort points (from their story cards) in that release. This doesn't anwser all your questions, but it may help lock in the concept of card relationships as a property you can work with.


    -Dave G.

    Comment actions Permalink
  • Avatar
    Victor M.

    Hi Dave,

    Thanks so much for thaking the time to reply in such detail!

    Sounds like you know your way around Mingle. I am still confused unfortunately. I'm probably not asking my question clearly enough. Let me try and say it differently here.

    My goal is to track features/epics, releases, and sprints. We'll leave the tactical oversight to the stickies and the devs standing in front of the board. So our goal with Mingle is really to use it as a high level strategic tracking tool. That being said I do want to see burn downs at the sprint level (so stories will be on the wall, and in Mingle...our one duped set of data). So there's a very breif overview of our goals with the tool.

    In terms of specifics I have the following confusion.

    I want to set up my first project, like this:

    • Release1 (July1-August1)

    • Sprint1 (July1 - June14)

    • + Stories

    • Sprint2 (July15 - Aug1)

    • +Stories

    • Release2 (Aug2 - Sept1)

    • Sprint3 (Aug2 - Aug14)

    • +Stories

    • Sprint4 (Aug15 - Sept1)

    • +Stories

    • etc...

    How do I define those date ranges?

    Looks like I could do it using Variables? If that is correct, I'm confused about that to set it up, how to ref those variables at the card level, how to get my sprints to have date ranges, etc...

    Sounds like I could just make a Card called Release1 and build date ranges into that card...then make Sprint cards with their own date ranges...then drag those Sprint Cards into the Releases and allow those Sprints to adopt the Release name from the parent...then add stories to the Sprints wherever I want.

    This sounds super simple and lite weight, but unclear if it will work.

    Do I need Variables? Can I manage the entire theing without them and just use cards as the items that define date ranges?

    So sorry for the lengthy question. I see a great deal of potential in Mingle and want to put it through a full test but we are pretty much stalled on this point. Anyone with any direct experience or advice is greatly appreciated!



    Comment actions Permalink
  • Avatar
    Jay Mitchell

    Hi Victor,

    The starting point would be to create three card type, "Release", "Sprint", and "Story."

    Then create "Start Date" and "End Date" properties. When you create those properties associate them with the Release and Sprint card types.

    Once you've got this basic structure, create a card tree. The card tree will have a structure of Release > Sprint > Story.

    (As Suzie mentioned, this is how the Scrum template is setup. Also, Explore Mingle is a great place to learn about these concepts.)

    Now you can create a Release card named, "Release1", with a Start Date of July 1 and an End Date of August 1. Then Add two Sprint cards as children of Release1 and set their start and end dates. Now you've got a tree structure, where you can add stories to their specific sprints.

    When you get to this point, we can answer specific questions about how to work with this project.



    Comment actions Permalink

Please sign in to leave a comment.