Here's a Situation.
I have got multiple Products. Several different Customers are aligned to these Products.
Customers have Projects relating these Products. Also these Projects map different Functional areas'.
Followed by the Stories/Tasks mapping these Functional areas and their association to the Projects.ABCD Hierarchy Distribution.png
This is a very interesting use case. Overall everything is possible and I have a couple of clarifying questions so that I can give you the most accurate answer.
First, what is the end deliverable - a project or a product version. From the picture it might look that the end deliverable to the customer is a project which consist of multiple product. Please clarify.
Second, the functional area are they physical sub-areas of the product like DB, UI, etc or more of a organizational function like team?
Thank you for the response.
PFB are my comments:
1. Yes the end deliverables are Project and the consideration made is correct.
However, to give a clarity, a project will be mapped to at least one product and may get mapped to multiple products if needed at later stage.
Futher to this, a project will be mapped to at least one customer and may get mapped to multiple customers if needed at later stage.
2. Functional Areas are more like teams of the organization. In addition to this, every project will be mapped to at least 1 Functional Area and may get mapped to multiple if needed at later stage.
OK. Here is what I suggest.
your product = Project in JIRA
your functional area = Agile Board
Now comes the tough part how can you create you Project which a composition of multiple JIRA Projects - here I suggest that you use an add-on Cycle Control which allows you to map a so called Release to multiple JIRA Project and in addition gives you a nice Project management features for control it.
To recap - each product will have its own Product where the stories/tasks will be created. The functional teams will use Agile boards to track their work, there boards will have stories from multiple JIRA Projects.
The actual customer deliverables will be tracked in Cycle Control releases which are mapped to multiple JIRA Projects.
The picture will look like this:
Let me know if this works for you.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs