tag:blogger.com,1999:blog-6671186884241707065.post1405874362711249353..comments2009-03-30T22:57:19.594-05:00Troy Tuttlenoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-6671186884241707065.post-19047365655979435482009-03-30T21:09:00.000-05:002009-03-30T21:09:00.000-05:00Very good post and a great reminder to stay focused on the big picture and execute. The point of the standup meeting is to simplify, not complicate, the process.<BR/><BR/>I wrote a post a couple of days ago about the daily standup meetings, which I use for my engineering organization:<BR/><BR/>http://johnfmoore.wordpress.com/2009/03/29/why-i-love-the-daily-standup/<BR/><BR/>I would love to hear your feedback.<BR/><BR/>John<BR/>http://johnfmoore.wordpress.comJohn Moorehttp://johnfmoore.wordpress.comnoreply@blogger.comtag:blogger.com,1999:blog-6671186884241707065.post-78412829994942203122009-03-30T13:08:56.589-05:002009-03-30T13:08:56.589-05:00@Derick<BR/>I agree context is king. Thanks for raising the question to begin with. It is an important topic for Agile teams to consider, with no easy answers.Troy Tuttlehttp://www.blogger.com/profile/18294885767408324112noreply@blogger.comtag:blogger.com,1999:blog-6671186884241707065.post-77650554114102884052009-03-30T12:46:00.000-05:002009-03-30T12:46:00.000-05:00Great insights, Troy. I got a little over-enthusiastic in my post and dove into the big-M Methodology without realizing it. <BR/><BR/>on further reflection of what i originally wrote, i think the notion of a "no issues" anti-pattern is more applicable to immature teams, and any maturing/mature team should drop the need to require an issue to be brought up.<BR/><BR/>it all comes down to the context of the individual team.Derick Baileyhttp://www.blogger.com/profile/11278436552796934211noreply@blogger.comtag:blogger.com,1999:blog-6671186884241707065.post-4401941991359786782009-03-30T07:23:00.000-05:002009-03-30T07:23:00.000-05:00Preach it brother. This process inflation is a common problem in software, I think. Good post.<BR/><BR/>~Leeleebrandthttp://www.blogger.com/profile/01387649808988075295noreply@blogger.comtag:blogger.com,1999:blog-6671186884241707065.post-62604091047155102072009-03-30T00:17:00.000-05:002009-03-30T00:17:00.000-05:00Having "no issues" in a daily standup is a good thing, indeed it is a goal of Scrum.<BR/><BR/>Developers should raise impediments - and the daily standup is a tool to encourage them. But after some time they will learn to raise issues immediatly and the ScrumMaster can solve them immediatly. No need to wait for a daily standup.<BR/><BR/>Cheers<BR/>Stephan<BR/>http://twitter.com/codemonkeyismStephan.Schmidthttp://www.blogger.com/profile/03845125686370893937noreply@blogger.com