When using Kanban boards in Azure DevOps, if the story is split into tasks, is there any support for working with tasks?
In the below image we can see the tasks with yellow under the stories but that is not easy for the developers to use. The task board can only be used if also working with sprints.
I haven't been able to find any documentation related to this. Are tasks supposed to be used at all when using a Kanban board?
Are tasks supposed to be used at all when using a Kanban board?
No, I'm afraid there's no such feature supported in azure devops boards now.
Because this is by designed based on the concept of Agile process.
See this Agile process workflow:
For Epic, Feature and Stories, they are all belong to Portfolio backlogs, while tasks is iteration backlog.
For our Azure devops Kanban Boards, it used to display the Portfolio backlogs for management team. You could add additional customized portfolio backlogs level by modifying the process your project is using.
But you could not change the tasks from iteration backlog to Portfolio backlogs. Because this does not match the basic concept of Agile process.
For Azure DevOps Boards, the Boards view visualizes the Requirement Backlog which is typically a User Story or Product Backlog Item, but it is not meant for moving Task states. For moving a Task between states, the Sprints view is used:
In my experience, for a team using an iterative methodology like Scrum or the Agile template, the Sprints view is likely more heavily used than Boards and the opposite is likely normal for a team using Kanban since Boards visualizes the requirements nicely for flow. Hybrid methodologies like ScrumBan could use both. Whatever works best for the team.
See this table and more information here:
