Assume I'm architecting product lifecycle management for a small team and want to (almost) exclusively use Atlassian's portfolio to simplify the technology integration points. Would Atlassian architecture look something like the following process and products below? If you have a reference architecture that integrates your entire portfolio, that would answer my question.
PROCESS - PRODUCT
create project - in JIRA
create repo - in Github (not Atlassian product), link with Stash (Atlassian)
setup project contributors - in JIRA, Confluence Team Calendars
setup builds & tests - in Bamboo, link with Stash
document changes & issues - Confluence
enable continuous integration - in Bamboo, link with Stash
manage releases - JIRA
enable issue resolution - JIRA Service Desk
If you consider the product documentation as core part of the product's lifecycle (you should), then also add these:
PRODUCT - DOCUMENTATION
produce end user documentation - in the K15t plugins (depending if you need PDF, HTML, Windows help, website)
manage documentation lifecycle - in Archiving Plugin
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