Currently we use JIRA and Confluence. Confluence for the business requirements, and JIRA where Epics links together the requirements and the user stories.
We are thinking on make it even more agile by removing the documents in Confluence, and directly have the requirements and documentation in the Epics. We also plan to add a Kanban bord for just hadling the Requirements/Epics to display the priority, status of the requirement, and so on.
What's your thoughts on this? Can you see and pro's or con's?
I'm very thankful for all input!!
In my experience, using Epics as "large stories that may span more than one sprint" works well. Depending on the complexity of your software and the size of your development team(s), you can use components as well.
I say, give it a try. If that doesn't work, look into other plugins, like Structure.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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