Using the Kanban (Board) for a retrospective meeting and follow-up

2,354 views
2,247 views

Published on

Communication : Using the Kanban (Board) for a retrospective meeting and follow-up – (manly for distributed teams)

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,354
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Using the Kanban (Board) for a retrospective meeting and follow-up

  1. 1. Communication : Using the Kanban (Board) for a retrospectivemeeting and follow-up – (manly for distributed teams)Shirly Ronen-Harelshirly@agilesparks.comOne can use Kanban board for the retrospective documentation and follow-ups over retrospective action items.One small reminder, first. The retrospective has three main characters: 1. Open discussion of the team – main goal and the most important artifact of the team 2. Action items 3. Acting upon those action itemsI have been wondering, what will be the best way to handle a retrospective, which is visible, easy to follow andactually having the team act upon those action items easily.It bothers me especially when looking into the differences we have in our distributed teams, mainly visibility toaction items of the retrospective and be able to create an effective discussion over issues raised in the sprintwhile the team is not placed at the same room/country.The idea was, to try and use a Kanban board,( best recommended to use a web Kanban board when dealing withdistributed teams) to overcome those obstacles of establishing an open discussion and its outcomes.My suggestion is best used for: 1. Creating the issues for discussion – place them on the board 2. Setting the action items 3. Following the actions for next time
  2. 2. Lets see how Kanban can answer all of those and meet the three retrospective chanters detailed above: 1. Visualize your flow a. create a simple Kanban board flow to fit the retrospective structure b. It can hold columns of: what should we stop doing , continue doing, start doing; or :went well, needs improvement….. c. Don’t forget to add an action item and acting columns 2. Ask team members to take some time and start filling out tasks in each of those columns (do not assign these tasks) 3. Create an open discussion over those issues 4. Decide on action items and place them will the assignee on the action items column 5. Team members follow this board during the sprint , allocates the correct capacity into their product sprint to be able to complete those tasks , and make sure to move the action items as they progress 6. Next meeting: open the Kanban board and start the meeting by reviewing last session progress. 7. A more improved and mature process can hold types of tasks, deferent columns, and assignments to areas or improvements, whatever…..…..Enjoy….

×