Kanban’s Implementation of Technical User Stories

Although user stories are frequently implemented as cards or work items in a Kanban system by numerous practitioners, it is crucial to note that this is not mandatory. The reason behind the popularity of user stories in Kanban is their ease and speed of estimation, rather than being a prerequisite of the Kanban system.


One of our apps was developed by a programmer who worked independently and had a tendency towards spaghetti code. As a result, it’s now considered technical debt and requires attention. As the team leader, I propose splitting the
user story
into two parts: redesigning and creating the database and its related
store procedures
, etc. The user story includes multiple tasks such as database design, creation, table creation, stored procedure creation, and job creation. Given the complexity of the project, I recommend assigning two people to work on it. Do you suggest splitting the user story into two parts or keeping it as is with multiple tasks?


This is not exactly a user story, but rather a task. The question is whether multiple developers can work on it, and the answer is yes. In contemporary methodologies like JiT and ToC, completing tasks quickly takes precedence over having numerous tasks in progress simultaneously.

When it comes to deciding whether to divide the task among individual developers or not, the crucial factor is:

  • Individuals comprehend which tasks are being carried out by whom.
  • Moving between the overall view and the specifics is a simple task.
  • It’s SMART

In my experience, both methods have been successful. However, I believe that tasks should be divided if they can be completed independently. Otherwise, the task remains the same, regardless of the number of people working on it. Therefore, in your situation, it would be best to treat it as a single task.

Inquire with the team about their preferred option and experiment with both before making a decision. However, it’s best to keep things uncomplicated unless it’s necessary. Begin with a simple approach.

Frequently Asked Questions

Posted in Uncategorized