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,582
Community Members
 
Community Events
184
Community Groups

Two portfolios each with a unique project, but also share a project - how to estimate?

Hello,

I have two separate projects that each have their own portfolio. However, each project shares a third project, in which both portfolios have the exact same tickets from that project.

What is the best way to handle portfolio estimations for that third project, given it's the same tickets? For example, if I just add the project, it's story points will be double counted in each portfolio. Is there a way to let portfolio know to either split the estimate, or, something of that nature?

1 answer

1 vote
Thomas
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 15, 2017

Hi @Rob Thorpe,

You seem to have reached an use case not currently covered by Portfolio. Could you expend a little more on why those issues are needed in both Portoflio Plans?

Are those issue being worked on by the same team / team members (or should be at least)?

If those plans are small and have a tight dependency with each other, you could consider grouping those under a single plan.

If the dependencies are minimal you could use earliest start date to ensure some issue are not started before the right date.

 

Cheers,

Thomas

The project that is being shared is provided by a 'shared services' team. Both of the projects mentioned need the same features provided by the shared service.

Both projects have different team members. However, the shared services team has the same members accross both projects.

Grouping under one plan is not an option, since they are separate products. We need to have separate schedules. However, this would of course solve my estimation issue.

Any further ideas based on this?

--

Thanks, Thomas.

Thomas
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 17, 2017

If the shared project is worked on by the same team with the same configuration then it should be scheduled the same way in both plans.

There is currently no capacity aggregate across plans so this shouldn't have an impact.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events