Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How should i support 2 different hierarchies

We have several projects already using advanced roadmaps, and the global settings look like:

  • initiative ...
  • epic ...
  • story (defaults)
  • sub-task (defaults)

 

Now we have other teams using R4J and requirements based projects and they have something like this (not in the the plan tool):

  • Customer Requirement / New Feature
    • (with possibly several levels of customer requirements tree here)
  • Functional Requirement / Non-functional Requirement
    • (again possibly 1+ levels)
  • Task
  • Sub Task

We also have "Test", "Test Execution", ... (all from XRAY) that should be represented in the hierarchy somewhere.

I dont want to break existing "stry" type projects, but want to allow the requirements projects to use the planning features in roadmaps.

 

Any thought on the best way to do this?

1 answer

The hierarchy of themes/initiatieves/epic/stories is bases on the duration of that item:

"While an epic is something you might complete in a month or a quarter, initiatives are often completed in multiple quarters to a year." Quote from this article: https://www.atlassian.com/agile/project-management/epics-stories-themes

If you customer requirement is broke into several functional requirements, then you can create an initiative for the customer requirements with underlying epics for the functional requirements.

My suggestion for Test and Test execution is to make that part of your scrumboard by adding columns if you want every item to be tested (and consider this extra work when estimating it).
If you want to do all the testing at the end of the project you can create a separate task-ticket for it.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....

148 views 2 6
Read article

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