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,559,686
Community Members
 
Community Events
185
Community Groups

How do you track ongoing support epics?

We are starting to use Portfolio and I'm hoping that it helps us get better at planning for the future.  We are t-shirt sizing epics, and that's pretty straightforward to plan out in Portfolio, but what do you do with ongoing maintenance/support?  That "epic" (it's not really an epic) has no end date, but I want to allocate a certain percentage of capacity to it each sprint.  That percentage will change over time, for example, it could be 20% of capacity for awhile but next year we might spend a couple months doing 50% maintenance/support.

I'm looking for suggestions of how you all plan out future sprints in Portfolio when you have a combination of sized epics and percentage allocations to ongoing support efforts.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events