Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,603
Community Members
 
Community Events
176
Community Groups

Is there a best practice for number of levels of hierarchy in portfolio?

I am trying to understand how this community is using different hierarchy levels in portfolio and how the different levels are defined. I am trying to implement portfolio management and wanted some guidance on how the different levels are used by portfolio, program and teams. 

1 answer

1 accepted

0 votes
Answer accepted
Ste Community Leader Sep 05, 2019 • edited

Hi @Bamini Subramanian

I would advise you create the number of levels necessary to visualise your organisation's Portfolio.

There are going to be lots of great suggestions on the right number of levels - but what you have to remember is Jira isn't mapping your organisation's work structure - you should apply it to Jira / Portfolio to get you the best view of your own data.

One of the most common methods I've used is:

  • Initiative: Project-level - an objective or goal, often multi-year in size
  • Feature: A sizeable chunk of work, with isolated value that can be delivered at completion
  • Epic / Story / Sub-task

Thank you for responding, and I have taken your advise to look more closely at the organisation's structure and needs. We have landed on Theme, Initiative and Feature. Of course it is going to be evolving, but it is a start. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events