Comments on: First Visual Management Workshop http://www.xqa.com.ar/visualmanagement/2009/03/first-visual-management-workshop/ Using information visualization to manage agile projects Mon, 28 Nov 2011 17:36:49 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Tobias Mayer http://www.xqa.com.ar/visualmanagement/2009/03/first-visual-management-workshop/comment-page-1/#comment-121 Tobias Mayer Tue, 24 Mar 2009 01:13:43 +0000 http://www.xqa.com.ar/visualmanagement/?p=232#comment-121 Congratulations on running the workshop. It looks like a lot of fun with some good output. As always, the pictures really enhance the content of the post. You are visual indeed :-) Congratulations on running the workshop. It looks like a lot of fun with some good output. As always, the pictures really enhance the content of the post. You are visual indeed :-)

]]> By: Hans De Beuckelaer http://www.xqa.com.ar/visualmanagement/2009/03/first-visual-management-workshop/comment-page-1/#comment-35 Hans De Beuckelaer Tue, 03 Mar 2009 07:29:19 +0000 http://www.xqa.com.ar/visualmanagement/?p=232#comment-35 Hey Xavier, nice post again. I am pleased to see that you still are looking for improvements for your task boards. I also believe that it can always improve. Based on the photos, I see some things I like and some that I don't like, compared to the boards we use today: I like: - The separate 'impediment' section. It gives a clear view on the unplanned things that occupy the team. - The separate 'urgent' and 'issues' section. Currently we have something similar called 'unplanned' but it doesn't emphasize the importance of these tasks. Renaming it to 'urgent' and 'issues' would make it much easier to understand for everyone (also non team members). I don't like: - The time/effort indication on the different tasks. We are also asked to do that today. I think it results in tasks getting bigger and bigger every sprint and you don't see a daily team progress any more. According to me, a task should represent more or less 1 day of work. - The 'To test'-column. Testing a task is part of the work that is needed to succesfully deliver a story by the end of a sprint. I think it belongs to the 'In progress'-column. Hey Xavier, nice post again. I am pleased to see that you still are looking for improvements for your task boards. I also believe that it can always improve.
Based on the photos, I see some things I like and some that I don’t like, compared to the boards we use today:

I like:
– The separate ‘impediment’ section. It gives a clear view on the unplanned things that occupy the team.
– The separate ‘urgent’ and ‘issues’ section. Currently we have something similar called ‘unplanned’ but it doesn’t emphasize the importance of these tasks. Renaming it to ‘urgent’ and ‘issues’ would make it much easier to understand for everyone (also non team members).

I don’t like:
– The time/effort indication on the different tasks. We are also asked to do that today. I think it results in tasks getting bigger and bigger every sprint and you don’t see a daily team progress any more. According to me, a task should represent more or less 1 day of work.
– The ‘To test’-column. Testing a task is part of the work that is needed to succesfully deliver a story by the end of a sprint. I think it belongs to the ‘In progress’-column.

]]>