When training teams to work in timeboxed cycles for agile innovation projects, we so far mostly have used a very simple way of breaking down the tasks within a cycle based on google docs. Here is an example:
Basically, the team adds tasks based on the backlog tasks they get from the champ (product owner) and they then pull tasks. Who has started a task marks it yellow, if it's done it becomes green. It's a very useful way of managing the tasks.
Some teams, however, have started preferring kanban as a tool to monitor the tasks in their timeboxed cycles. They argue that is more visual and easier to follow. The same tasklist like above would then look different:
What is interesting is that many teams think that kanban visualizes the work better. While in the tasklist above you can see, of course, if a task is already pulled and started, here you can actually see where exactly it is in the process, who pulled it, you can go into a card and see details or links or comments.
By assigning different colors to the tasks you can distinguish between types or sizes of tasks or you can assign urgency (see next example)
It is not necessary, of course, for a team to use a digital kanban board. Often, the handmade version with Post-its or generic stickies is more than enough. The important thing is that the work is visualized and the team meets in front of their board often to check the status of their work.
We do not tell teams how to manage their tasks, but we tell them to keep a task list and explain them the two most common ways it can be done. Maybe you have other options, please share them!
Basically, the team adds tasks based on the backlog tasks they get from the champ (product owner) and they then pull tasks. Who has started a task marks it yellow, if it's done it becomes green. It's a very useful way of managing the tasks.
Some teams, however, have started preferring kanban as a tool to monitor the tasks in their timeboxed cycles. They argue that is more visual and easier to follow. The same tasklist like above would then look different:
What is interesting is that many teams think that kanban visualizes the work better. While in the tasklist above you can see, of course, if a task is already pulled and started, here you can actually see where exactly it is in the process, who pulled it, you can go into a card and see details or links or comments.
By assigning different colors to the tasks you can distinguish between types or sizes of tasks or you can assign urgency (see next example)
It is not necessary, of course, for a team to use a digital kanban board. Often, the handmade version with Post-its or generic stickies is more than enough. The important thing is that the work is visualized and the team meets in front of their board often to check the status of their work.
We do not tell teams how to manage their tasks, but we tell them to keep a task list and explain them the two most common ways it can be done. Maybe you have other options, please share them!
No comments:
Post a Comment