In the practice of agile development, it is a necessary practice to realize team collaboration and transparent management through visual task Kanban. By visualizing the task Kanban we can achieve several purposes:
1. Visualize the objectives of the management team;
2. Define the priority of the target;
3. Clarify the task items after the target decomposition;
4. Visualize the progress of management tasks.
Agile task Kanbans are usually one per iteration, and the structure of the kanban usually consists of several columns:
- Story-This column stands for user stories, user stories are expressions of demand in agile development, and each user story represents a user's needs expressed from the product's user perspective. User stories This column is a list of all the user stories that need to be completed for this iteration, and these stories together are the goals of this iteration. These stories are usually ranked from top to bottom in priority order.
- Todo -This column represents a to-do task item, and the user story is broken down into the corresponding technical tasks, which are put to todo columns.
- Doing -in-progress tasks, putting the tasks in progress.
- Done-complete the task and put the completed tasks and user stories.
In addition to the 4 columns on the Task Kanban board, we also create a swimlane for each user story to manage the correspondence between stories and tasks through a swimlane.
A standard task Kanban looks like-1:
Figure-1
In the recently released version of Leangoo, we have added a swimlane feature that allows us to easily create lanes and use it to manage the correspondence between stories and tasks. (Figure 2) is an example of an agile development iteration kanban using the Leangoo implementation with a swimlane, for reference:
Figure-2
About
Liao Jingbin, International Scrum Federation certified CSP,CSM, a nationally renowned agile coach, consultant, trainer
Article turned from: leangoo.com
How do I use Leangoo for iterative management (sprints, Task Kanbans, burndown charts)?