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.
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events