Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
We need to create a portfolio and hierarchy in JIRA based on the structure currently used in .xls.
In .xls, we have 3 levels; Program group, program and team. In the 3 levels we have several projects where they are managed:
- Program group: epics
- Program: epics, feature, story
- Team / project: epic, feature, story, sub-task
How can you group the information of all the projects to have a strategic vision with jira portfolio and struture?
In other organizations, how do you manage strategic planning in JIRA with portfolio for jira and / or structure?
In JIRA everything is managed with projects at the same level, how do you relate a project set with 2 levels higher to see the progress?
We have Program Increment, I think they could be in Portfolio for JIRA, the releases CROSS.
As Vanessa mentioned, it's quite a big quesiton to answer and both tools can be useful in this case. Each tool has it's strong points, so depending on your specific needs you can use one or the other or both like quite a few of our customers. Portfolio is mostly focused on planning, while Strucutre has many features for visualisation of a large scope of work, traking progress, creating issues break-downs for analysis and offers far more flexibility.
Here is an example of a structure similar to yours, but you can have any kind of hirarchy built in a similar way:
If you wish, we'll be happy to de a detailed demo of Structure capabilities and how it can be used for managing portfolios of projects.
Just contact us through support.almworks.com and we'll find some good time to do it.
Eugene (ALM Works)
Yo tengo muchas dudas para los Niveles una organizadora de "cartera" y "Programa".
En los Niveles de CARTERA Y PROGRAMA, ¿Puedo Tener Varios Proyectos?
Yo tengo varios "program" que tienen issues, como si fueran proyectos normales en JIRA, pero que estan en un nivel superior a los proyectos (nivel team).
En La DEMO que me mandas, veo Que Hay Un Proyecto para CARTERA y Un Proyecto para PROGRAMA.
¿Como se relacionan las cuestiones de PROYECTO DE PROGRAMA Y con cartera? ¿Como Es Posible párrafo Tener Una jerarquía?
Voy a Revisar tu DEMO, me sera de gran ayuda.
Un millón de gracias !! :-)
De nada :)
Con Strucutre es posible organizar tus projectos en qualquier manera. El estructura en la Demo es solo un ejemplo que refleja un setup mas tipico de nuestros clientes.
En este ejemplo he creado un tipo de JIRA link especial (implements/implemented by) para usar para connectar Initiatives i Epics. Eso es una manera bastante tipica.
Pero tambien puedes utilizar proyectos en otra manera i por ejemplo usar differentes tipos de issues por differentes niveles, pero del mismo projecto.
Todo depende de manera de organizacion en vuestra empresa.
Es un poco deficil explicar solo escribiendo - hay un grabacion de un webinar, que muestra los features basicos de Structure - es un poco largo, pero da un idea de que es possible:
Es en Ingles, pero si tiene algunas preguntas - puedo commentar i resolver qualquier dudas.
Puede escribir me a email@example.com o contactarnos por support.almworks.com
Losiento por mi Espanol - no practico mucho :)
This is a giant question to answer. We tried Structure in the past, but it was too much for us at the time. We currently use Portfolio. Within Portfolio we create additional hierarchy that does not exist in Jira using the term Program Epic. It's important to note though that issues in Jira can link to a "parent link" which reflects the additional hierarchy introduced with Portfolio. I can have a Project level Epic link to a program level Epic. This allows our Product Management team to manage a backlog of stuff at a higher level and refine it until it is "ready" for teams to work on.
Generically speaking, I think you can achieve the hierarchy you're looking for in Portfolio (it's designed for that); however the exact mechanics are not clear without context of your business and probably some trial and error.
Releases can be created at the project level in Jira or at the Portfolio level. For example, if you create a cross project release in Portfolio and push it down into Jira, it will create that same release in each of your individual projects.
If I have 3 projects in Jira (Project A, Project B and Project C) and in Portfolio, I have a plan with all 3 projects and want to create a cross project Release, I would do so in Portfolio, put the relevant epics and such in it and then push down to Jira. When pushing to Jira, each one of those projects will see that cross project release in the list of "Versions".
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Recently, as part of a series of Portfolio for Jira case studies, we spoke with Carl DiClementi, Director of Product Management at Factom about how he uses Portfolio for Jira. In...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs