Comments on: Rules Of Standup – You Don’t Need To Justify Your Own Existence http://www.skorks.com/2009/09/rules-of-standup-you-dont-need-to-justify-your-own-existence/ For the betterment of the software craft... Mon, 21 Nov 2011 13:57:06 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Alan Skorkinhttp://www.skorks.com/2009/09/rules-of-standup-you-dont-need-to-justify-your-own-existence/comment-page-1/#comment-3230 Alan Skorkin Sat, 10 Oct 2009 11:21:00 +0000 http://www.skorks.com/?p=1169#comment-3230 I do see your point and the situation will differ from team to team. You can easily gauge if your standup is working by looking at how bored people are during. If people are not getting value out of the standup then you need to change what you're doing. This change could simply be letting people not say anything if they have nothing to say. It could also be something else you need to try different things and see what works. Everyone would agree though that a standup where people are bored is not useful to anyone. I do see your point and the situation will differ from team to team. You can easily gauge if your standup is working by looking at how bored people are during. If people are not getting value out of the standup then you need to change what you’re doing. This change could simply be letting people not say anything if they have nothing to say. It could also be something else you need to try different things and see what works. Everyone would agree though that a standup where people are bored is not useful to anyone.

]]> By: Nirav Assarhttp://www.skorks.com/2009/09/rules-of-standup-you-dont-need-to-justify-your-own-existence/comment-page-1/#comment-3223 Nirav Assar Thu, 08 Oct 2009 19:58:46 +0000 http://www.skorks.com/?p=1169#comment-3223 I disagree with some of the points made here above. If you are working a task that is long (as you say, longer than two days), just keeping quiet and saying "same deal as yesterday" provides no value to the team. The point of scrum is to flush out any intersections of tasks or actions so that efficiency can be gained or a technical innovation can be shared. The point is to lay things on a table and see what matches and use that information to better the project, on a micro and macro level. In addition, if a task is longer than two days there must be some way to communicate about the task in a more broken down manner. Even if you are researching some obtuse bug, where the problem is not well defined you must be making some kind of progress even if it be eliminating certain root causes. If nothing, you can describe what your roadblock is! The main point to take from a long scrum is for each person to be concise and short, not to just play dead and act like they have nothing to add. If there is a lot of people on a team and you have scrum you can all agree to limit your time to one minute each, and bam! get through it fast. I was on an agile scrum with 25 people and we got done in avg 16 minutes. The larger the team gets you have to accept that some minimal time is needed for each person and accept that your scrums simple just can't be 5-10 mins. I disagree with some of the points made here above. If you are working a task that is long (as you say, longer than two days), just keeping quiet and saying “same deal as yesterday” provides no value to the team. The point of scrum is to flush out any intersections of tasks or actions so that efficiency can be gained or a technical innovation can be shared. The point is to lay things on a table and see what matches and use that information to better the project, on a micro and macro level.

In addition, if a task is longer than two days there must be some way to communicate about the task in a more broken down manner. Even if you are researching some obtuse bug, where the problem is not well defined you must be making some kind of progress even if it be eliminating certain root causes. If nothing, you can describe what your roadblock is!

The main point to take from a long scrum is for each person to be concise and short, not to just play dead and act like they have nothing to add.

If there is a lot of people on a team and you have scrum you can all agree to limit your time to one minute each, and bam! get through it fast. I was on an agile scrum with 25 people and we got done in avg 16 minutes. The larger the team gets you have to accept that some minimal time is needed for each person and accept that your scrums simple just can’t be 5-10 mins.

]]>