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
Currently we run our projects where we have User Stories and Acceptance criteria in Confluence, and Jira tickets are used to organise the implementation of these via Sprints and agile boards (and to log time via Tempo).
We're finding that:
We've started to do the following, in an effort to mitigate some of these issues:
This solves a lot of these problems however after some research I've found that a lot of places are doing the opposite of what we're doing where Confluence is used as just a list of User Story titles and have a link to a Jira ticket that has all of the meat (User Story, AC, status, conversation). There's even a blueprint in Confluence that drafts this (Product Requirements) for us.
I actually think this approach is better, but wanted to see what others are doing and how they find it?
Some issues with this approach that I haven't solved for yet:
Keen for any insights from anyone.