http://www.rallydev.com/agileblog/2009/03/get-serious-about-your-meetings-with-jean-and-seth/ Adopt, Scale and Succeed with Agile Development Tue, 10 Jan 2012 03:30:50 +0000 hourly 1 http://wordpress.org/?v=3.0.5 http://www.rallydev.com/agileblog/2009/03/get-serious-about-your-meetings-with-jean-and-seth/#comment-3554 Blair R Wed, 08 Jul 2009 22:24:05 +0000 http://www.rallydev.com/agileblog/?p=1293#comment-3554 @Jean, do you have any more info on scrum for non-sofware projects? Like your wife's work that you mentioned in another interview @Jean, do you have any more info on scrum for non-sofware projects? Like your wife’s work that you mentioned in another interview

]]> http://www.rallydev.com/agileblog/2009/03/get-serious-about-your-meetings-with-jean-and-seth/#comment-3481 Scott Jackson Wed, 17 Jun 2009 20:03:29 +0000 http://www.rallydev.com/agileblog/?p=1293#comment-3481 I currently work on a project that suffers from the Waterfall process. My team has tried to incorporate "stealth" agile practices, one of which was a daily Scrum. We thought having a scrum would identify roadblocks and help us meet our schedule. At first it wasn't working out the way we hoped due to several reasons. The biggest issue was that we were stuck with a fixed highly ordered schedule and the result of the meeting lacked an impact on our daily tasks. We are still trying to find the ways to make our daily scrum feel like it is valuable. What definitely helps (and it sounds simple) is defining the purpose of the meeting and sticking to it. At first our team treated the scrums as a glorified status gathering snooze fest, then it became a quagmire of technical discussions. We had to step back and think what we are trying to gain from this meeting. It seems simple, but loosing track of meeting purposes happen all the time. Making sure the interested parties know that there is something gained by the meeting is critical to getting everyone involved. Maybe there isn't something gained and the meeting is not needed If the meeting does drift from the intended purpose then someone definitely has to step up and make the call to take the discussion off-line. I currently work on a project that suffers from the Waterfall process. My team has tried to incorporate “stealth” agile practices, one of which was a daily Scrum. We thought having a scrum would identify roadblocks and help us meet our schedule. At first it wasn’t working out the way we hoped due to several reasons. The biggest issue was that we were stuck with a fixed highly ordered schedule and the result of the meeting lacked an impact on our daily tasks. We are still trying to find the ways to make our daily scrum feel like it is valuable. What definitely helps (and it sounds simple) is defining the purpose of the meeting and sticking to it. At first our team treated the scrums as a glorified status gathering snooze fest, then it became a quagmire of technical discussions. We had to step back and think what we are trying to gain from this meeting. It seems simple, but loosing track of meeting purposes happen all the time. Making sure the interested parties know that there is something gained by the meeting is critical to getting everyone involved. Maybe there isn’t something gained and the meeting is not needed If the meeting does drift from the intended purpose then someone definitely has to step up and make the call to take the discussion off-line.

]]> http://www.rallydev.com/agileblog/2009/03/get-serious-about-your-meetings-with-jean-and-seth/#comment-3467 Scott Fri, 12 Jun 2009 23:24:23 +0000 http://www.rallydev.com/agileblog/?p=1293#comment-3467 I stopped calling them meeting and started calling them doings. I stopped calling them meeting and started calling them doings.

]]>