nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Portfolio Mgmt via Kanban boards

Troy Plant

Are their any best practice documentation available on how to use Jira for Kanban boards to manage the relationship between strategy (portfolio planning and governance/reporting) and exection (scrum or kanban teams).

With the goal of using Kanban boards to to prioritize and manage the flow of projects, and then have Epic level data be rollup up into the status of the projects.

Basically want to re-create the functionality that Rally offers.

http://www.rallydev.com/help/getting-started-rally-portfolio-manager

Any reference documentation or add-in information would be helpful.

Accepted answers

Guillermo _DEISER_

Hello Troy;

We've been working with a big financial company trying to use JIRA & Greenhopper to 'view' the global situation of the projects. The workaround starts considering one JIRA project where the issues would represent Projects and the issue worklow the project workflow. that way we would be able to create a Kanban Board to visualize the state of every project.

Depending of the scope and the use, it is working fine but, of course, these solutions depends on the end user.

At a JIRA level we have developed a plugins called profields to add Project-level information and try to improve the Project portfolio management including gadgets to have an overall picture of all our JIRA projects based on those project-level attributes. You can take a look and try it, if you consider interesting the features:

http://www.deiser.com/subject/landing/profields/

https://marketplace.atlassian.com/plugins/com.deiser.jira.profields

But the use of Kanban to have a project-level picture requires, I think the use of JIRA issues representing your coporate projects, maybe.

Regards

All comments

Guillermo _DEISER_

Hello Troy;

Depending of the scope and the use, it is working fine but, of course, these solutions depends on the end user.

http://www.deiser.com/subject/landing/profields/

https://marketplace.atlassian.com/plugins/com.deiser.jira.profields

But the use of Kanban to have a project-level picture requires, I think the use of JIRA issues representing your coporate projects, maybe.

Regards

Igor Sereda [ALM Works]

Troy, in addition to Guillermo's answer:

You can take a look at our Structure plugin, which allows building a deep hierarchy of issues like the one displayed on the Rally page, with Categories, Initiatives, Features, and then Story hierarchy and Tasks.

With additional configuration, Structure is then able to:

- Aggregate statuses upwards, so a Feature is resolved when all stories are resolved;
- Aggregate progress information, time spent and estimates;
- Integrate with GreenHopper, so at the team level you can still use Rapid Boards.

Hope this helps
Igor

Tom Jackson

To echo Igor, we are using Structures for our Portfolio management. Works great.

John Garcia

It's worthwhile to check out the HowTo: Track Epics on the Control Chart to make sure the Epic Status stays up to date. There's a great link to Nick Muldoon's blog on the subjet there, as well.