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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I want to know which should be a part of a Kanban board: Use Cases or User Stories?
The scenario is that we have issues in Jira and GitHub that are marked as use cases and user stories.
We have swimlanes: To Do, Under Progress, Under Review, In Testing, Tested and Done.
I know that agile frameworks only talk about Product Backlog Items and the terms like Epic, User Story, Use Cases, Task, Sub-Task are practically for team discussions but yet I need to find out what should I put in the Kanban board: Use Cases or User Stories.
User Story defines the story/requirement from a user's perspective.
Use Case defines the scenario(s) in which that requirement (feature) will be used by the user.
So should it be better to define a User Story first as a separate Jira and GitHub Task and then create Sub-Tasks as user cases. But how to integrate them within a Kanban board under these swimlanes: To Do, Under Progress, Under Review, In Testing, Tested and Done, that is my main challenge.
I will greatly appreciate any help.
In the dashboard you can see everything and they will be located in the columns according to the status of the user story or the use case
All the work that is being done by the team (s) must be reflected on the board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.