We're just about to start using confluence and jira for our SDLC, and we're trying to map out how this process will work the best. In our organization, normally we have product managers defining epics. Then product owners/analysts will take those epics and break them down into individual stories, which will then go through the normal life cycle.
What I'm thinking initially for our handling of this process in Atlassian is something like this:
Does this flow in general sound doable? Am I going down a problematic road for some reason? Is there a better approach?
Ultimately we want a Confluence page for each feature that will always display the most up-to-date product requirements for all features. We also want the requirements to link easily to JIRA so that it's easy for people to get back and forth between individual JIRA stories or tickets and back to the overall requirements page / Epic.
(Considering adding Yogi to help with the integration.)
Like I said, brand spanking new to this, but if I can gain some lessons learned from people who have gone here BEFORE we screw it all up, that would be great!
LinkedIn, the world's largest business network has an exceptionally large Confluence instance. In their case, large means millions of pages and thousands of spaces. In this Showcase, we're focusing i...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot