Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,560,647
Community Members
 
Community Events
185
Community Groups

Next Gen Portfolio: Planning Large Stories

John Armenia
John Armenia Aug 12, 2019

We use large place holder stories to account for initial estimates of our epics.  As the teams break the epic down to stories, they pull points from these place holder stories.  In Portfolio 2.0, we could set the number of members that could be considered to work on a story.  This worked well as we assumed for these larger stories that more than one person could work on them at a time.

 

With Portfolio 3.0, it assumes only one person can work on these large stories so the timelines are obviously overextended.  What is the intended way to plan for these larger epics before they get broken down in the new version of Portfolio? Is there a plan to bring back the setting to assume more than one person can work on a story? 

Answer
Watch
Like Be the first to like this
284 views

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian logo
Team-managed projects
TAGS
AUG Leaders

Atlassian Community Events

See all events