The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Next Gen Portfolio: Planning Large Stories
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?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.