Comments on: Stand up and be counted http://carljoseph.com.au/blog/2008-05-29/stand-up-and-be-counted/ My personal high horse Fri, 21 Nov 2008 01:09:17 +0000 http://wordpress.org/?v=2.6.1 By: Joe http://carljoseph.com.au/blog/2008-05-29/stand-up-and-be-counted/#comment-2120 Joe Thu, 29 May 2008 14:03:36 +0000 http://carljoseph.com.au/blog/?p=212#comment-2120 Found this really interesting! It's amazing how fine-tuned it all is. How such small adjustments in the workplace can really boost productivity. Found this really interesting!

It’s amazing how fine-tuned it all is. How such small adjustments in the workplace can really boost productivity.

]]> By: Ameel http://carljoseph.com.au/blog/2008-05-29/stand-up-and-be-counted/#comment-2118 Ameel Thu, 29 May 2008 12:09:58 +0000 http://carljoseph.com.au/blog/?p=212#comment-2118 I suspect some of the team's DSW would stem from where in your project's lifecycle you are right now. If you're at a more relaxed, steady-as-she-goes stage then it's probably okay for meetings to simply be quick status updates. The challenge, I presume, will be make sure you don't get stuck in that format when work starts to picks up again :) In my experience, one way to encourage people to move out of the DSW state is to ask the question: Is there anything about to happen in the near future that would be good for the team, or for one particular team member, to know about right now? That is, are there are future potential obstacles that we should know about? For example, someone from another department might be getting ready to send a lot of work to a team member next week that may have some trickle-down effects on the others. Knowing this would help everyone prepare for that event now. In general, getting people to think about the whole team, as opposed to just what they alone are up to, turns out (in my experience, at least) to be very useful. Or is this outside the scope of the Scrum-format daily meeting? I suspect some of the team’s DSW would stem from where in your project’s lifecycle you are right now. If you’re at a more relaxed, steady-as-she-goes stage then it’s probably okay for meetings to simply be quick status updates. The challenge, I presume, will be make sure you don’t get stuck in that format when work starts to picks up again :)

In my experience, one way to encourage people to move out of the DSW state is to ask the question: Is there anything about to happen in the near future that would be good for the team, or for one particular team member, to know about right now? That is, are there are future potential obstacles that we should know about?

For example, someone from another department might be getting ready to send a lot of work to a team member next week that may have some trickle-down effects on the others. Knowing this would help everyone prepare for that event now.

In general, getting people to think about the whole team, as opposed to just what they alone are up to, turns out (in my experience, at least) to be very useful. Or is this outside the scope of the Scrum-format daily meeting?

]]>