Comments on: Making Meetings More Effective http://blog.brodzinski.com/2007/10/making-meetings-more-effective.html Dealing with software projects in real life Fri, 10 Feb 2012 19:07:34 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Pawel Brodzinski http://blog.brodzinski.com/2007/10/making-meetings-more-effective.html#comment-1934 Pawel Brodzinski Wed, 10 Oct 2007 20:11:00 +0000 http://blog.brodzinski.com/2007/10/making-meetings-more-effective.html#comment-1934 Yes, I missed that one: preparing and executing the agenda helps everyone to start at the same point, helps to keep the track and not to lose some important points which were to be discussed.<br/><br/>Thanks for appreciating the blog. Yes, I missed that one: preparing and executing the agenda helps everyone to start at the same point, helps to keep the track and not to lose some important points which were to be discussed.

Thanks for appreciating the blog.

]]> By: Andy Sells http://blog.brodzinski.com/2007/10/making-meetings-more-effective.html#comment-1933 Andy Sells Wed, 10 Oct 2007 18:43:00 +0000 http://blog.brodzinski.com/2007/10/making-meetings-more-effective.html#comment-1933 Pawel -- I only recently discovered your blog, but I've really been enjoying reading through your articles. This one, and your other on the frequency of team meetings especially resonate. While good communication between team members is essential to project success, spending time in meetings is time we're not producing product. Finding the balance is tricky. <br/><br/>We thought about this issue a lot when designing JuggleMyStuff. Our experience has been that the more transparent we can make a project, the fewer meetings we need to keep everyone on the same page.<br/><br/>Getting back to your points, there are times when a meeting is really the best way -- for example, to brainstorm or work through some complicated, multi-faceted issue(s). And I totally agree with your suggestions. One thing I would add is requiring an agenda --preferably sent before the meeting. That way, everyone comes with the same understanding of the purpose and stays on track.<br/><br/>Thanks,<br/>Andy Sells<br/>CEO, Jugglesoft Pawel — I only recently discovered your blog, but I’ve really been enjoying reading through your articles. This one, and your other on the frequency of team meetings especially resonate. While good communication between team members is essential to project success, spending time in meetings is time we’re not producing product. Finding the balance is tricky.

We thought about this issue a lot when designing JuggleMyStuff. Our experience has been that the more transparent we can make a project, the fewer meetings we need to keep everyone on the same page.

Getting back to your points, there are times when a meeting is really the best way — for example, to brainstorm or work through some complicated, multi-faceted issue(s). And I totally agree with your suggestions. One thing I would add is requiring an agenda –preferably sent before the meeting. That way, everyone comes with the same understanding of the purpose and stays on track.

Thanks,
Andy Sells
CEO, Jugglesoft

]]>