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
We have Developers, Designers and QA working on a single Jira board. Lately, we started using user story mapping to integrate the entire team into the planning process.
The difficulty is about finding an efficient way to link issues during planning and to make everyone understand what to work on first and what to wait for.
During planning, our team creates a new user story "As a user, I want to register so that I can start enjoying services". We would then create a story named "Login page" and create additional sub-tasks for each dedicated teams like
Once the designer are done designing the Login page, they will transition its issue to done and notify the developers to start work on its frontend.
I wonder whether the approach using story as main feature and its sub-tasks as jobs for each team to be the right approach, or should we actually create each as a separate issue and link them together?
Once the designers are done, they will pass the issue "Design UI for Login page" to the developers for frontend development. But due to the naming of this issue, the developers cannot simply continue to use it, they actually need to create a new issue titled "Develop frontend for Login page" and then link it to the original "Design UI for Login page". This involves quite some manual work. There must be more efficient ways out there.
Could you share with us how you would solve this sort of organizational problems?
This is also a challenge I have faced in multiple organizations, however, I have never seen Atlassian-sanctioned guidance around this which is pretty frustrating. I can't help feel that Jira just doesn't have a great way to handle this scenario, which is why Atlassian is remaining silent.
In my current scenario, we also need to split out the work for dev / design / qa in order to properly track velocity of the dev team. We do not track velocity of the designers due to the fact that they are spread across multiple teams and not dedicated to one scrum team, so we have the need to create separate issues for each discipline.