...
A more pragmatic approach is to use your current company-internal experiences and build hierarchy levels of interest based on your business. On each level, representing a particular abstraction grade of your business: you have projects you all control the same way based on epics and initiatives, actions, tasks, stories, or however you call those activities. For that, you are using the well-known standard features and reporting of Atlassian Jira. The bad news is that such multi-project dependencies are not supported out-of-the-box nor automatic aggregations from lower levels to higher ones. The good news: these missing features are available right now using "agile@scale".
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|