You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a strategy question, and I'm very interested to hear how others address this. We have an ecommerce website, and over the last 2 years, our team has been using Jira and Confluence, learning as we go.
We're trying to improve our documentation and planning to better support an offshore development team. 100% of our time is devoted to this website, so we have a single Jira project for working on the website. We create epics for all initiatives on this website; things like redesigning our checkout process, or bulding a new product detail page, things like that.
The epic and story process works well in Jira, but I'm struggling to match this up in Confluence. we have spaces created for teams, and some for side projects, but we're trying to use a single space to capture the business requirements and wire frame files. Right now, we're using a single requirements document that matches up to an epic, but this seems a bit awkward. Is that the best way? should we start in Conflunce, and then create the epic and stories?
I'm wondering how others use these two tools together. I'm also curious how others use Confluence to manage documentation after the epic has completed, and how you gather initial research (vendor docs, customer inverviews, business requirments from marketing, things like that).
Any feedback would be greatly appreciated. Thanks!