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

Advanced Roadmaps - Teams with different methods of estimation


From what I can gather when creating a plan it is recommended that you elect for an estimation for a plan timed based or story points.


I have elected for story points.


As I assemble the plan across the different teams, I note that some teams estimate using hours.

This leads me to believe that we should create separate plans, and use the dependency feature.

I work on the core platform features, and other teams are dependent on our delivery of those core platform features to plan out their delivery to their customers.  Those teams use hourly estimation for various reasons.



1 answer

Hi @Neil Wills 

In simple terms - yes, you need multiple plans.

Advanced Roadmaps needs one estimation method per plan to help with auto-scheduling, etc. 

If you do need a central multi-team view, you could either...

  • Not utilise estimates, and just use it as a basic roadmap to show progression
  • Meet with the other teams, and see if you can settle on one estimation method
  • Consider normalising the data - and potentially auto-populating it into Story Points and/or Hours using Auomation


Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you