Back to Forum

Which should be a part of a Kanban board: Use Cases or User Stories Edited

Last post 10:29 am February 19, 2020 by Ian Mitchell
1 reply
Muneer Ahmed
07:28 am February 17, 2020

Hi,

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.

Ian Mitchell
10:29 am February 19, 2020

Who is accountable for the value being delivered, and what would their preference be? Would use cases, user stories, or something else best allow value to be accounted for transparently, and incrementally maximized?

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.