tag:blogger.com,1999:blog-7930876570525471458.post4944528821132387320..comments2023-09-08T07:50:02.120-04:00Comments on Agile & Business: Suggestions for a better Daily ScrumJoe Littlehttp://www.blogger.com/profile/13413810050491070483noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-7930876570525471458.post-86481957888184358832015-05-21T08:43:05.693-04:002015-05-21T08:43:05.693-04:00Hi,
Thanks for this nice article. We figured out t...Hi,<br />Thanks for this nice article. We figured out that standup meetings are great but needed improvement (they took a lot of time, de-focussed our colleagues and interrupted their workflows). Because of this we developed a SaaS tool to "automate" the daily standup meetings - with just a single email. If you like to take a look: www.30secondsmail.com. <br />Best,<br />Ajie<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-34263908371278532902010-06-16T09:55:52.385-04:002010-06-16T09:55:52.385-04:00Hi Katie,
Thanks for your kind words. My view is...Hi Katie,<br /><br />Thanks for your kind words. My view is that even if we had the best Daily Scrum ever, we could still improve it. Although maybe we should improve a bigger impediment first.<br /><br />Anyway, that post was short. I have lots of other ideas on the Daily Scrum, which I hope to post soon. It seems to be a mis-understood meeting, probably because people have been to too many stupid 'status' meetings.<br /><br />The key purposes (that everyone seems to forget, at least eventually): 1. To give the whole team the info to land the plane successfully together. 2. To get the bad news out on the table asap, so the bad news does not get better with age. (Ok, some Aikido there, but you get the point.) [Yes, I said these in the blog post, but apparently they bear repeating. For others, not you.]<br /><br />Regards, JoeJoe Littlehttps://www.blogger.com/profile/13413810050491070483noreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-33978523225232646522010-06-16T09:10:22.215-04:002010-06-16T09:10:22.215-04:00Great post! As efficient as I believe our team is,...Great post! As efficient as I believe our team is, after reading your post, I smell areas of potential improvement. At least we are part of the lucky half that are Agile enough to continue to analysis and improve our processes. Thanks for the tips! Going to share your post on AgileShout.Katiehttp://www.agileshout.comnoreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-20658107738801049022010-05-29T10:29:28.516-04:002010-05-29T10:29:28.516-04:00I think we are talking about the same thing, I tel...I think we are talking about the same thing, I tell my scrum masters you need to take the time to get the job done, let people get out and share what needed but not let the conversation drift off into one or other technical detail. We have some team who get it done in 5 -10 some almost 15 to 20. Once over 20 I tend to start sitting in, usually there is a problem in the functioning of the team if they are going longer than 20 on a regular basis.5CentsWorthhttps://www.blogger.com/profile/11013305515644289452noreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-78788458657586244912010-05-29T09:37:41.019-04:002010-05-29T09:37:41.019-04:00Hi 5Cents,
Excellent advice.
I differ with you s...Hi 5Cents,<br /><br />Excellent advice.<br /><br />I differ with you slightly in one regard. I think the Daily Scrum "proper" should be reliably under 15 minutes. However, if anyone or the team decide to have an additional meeting right after the Daily Scrum, that would be fine (in my book).<br /><br />Usually in fact there is need for such a follow-on meeting with some group. But usually not the whole group of pigs. Or so I find.<br /><br />I think mostly we are saying the same thing, just a different way.<br /><br />I won't boor you and others saying all the reasons I agree with you on every other point.<br /><br />Regards,<br />JoeJoe Littlehttps://www.blogger.com/profile/13413810050491070483noreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-49854945892218449992010-05-29T07:00:03.863-04:002010-05-29T07:00:03.863-04:00All great advice, 15mins (max) mm, not really. If ...All great advice, 15mins (max) mm, not really. If they need to talk more thats ok, 15 mins is a guide. On reason I often find in teams that dont communicate in scrum meetings is the scrum master is working as a team leader , or another team member is working as a team leader and telling people what to do, so people shut up and wait. Or even worse that there has been a punitive response to bad news in the past. being late is not good but there maybe a good reason, and why is more important than anything else, so bad news is better than none and any action that stops bad news will crash the plane. Scrum meetings are a critical part of the bonding experience of the team the stronger the bond the stronger the team, the more committed they are, the more committed the more they will walk through fire to get the job done. Often forgotten in the It world we are human, being of two brains left and right, the left is the 3 questions that technically gets things done, the right is the multiplier, energy enthusiasm and engagement. Both are needed for you to get the highest performance and quality.5CentsWorthhttps://www.blogger.com/profile/11013305515644289452noreply@blogger.com