Are there too many meetings in Agile?

综合技术 2016-06-17

A few months ago I was asked the following question, and wanted to share my thoughts.

Sometimes there are too many meetings and our developers find it difficult to be really focussed and do justice to development activities. Are there any inputs you could give to improve such an environment? We’re thinking of something like; no meetings Fridays or limit meetings to 2 hrs a day.

In the first instance, this indicates a serious disfunction in your organisation. If you’re spending more than 2 hours in meetings per day you’re doing something wrong. One of the intentions of lean and agile delivery is to limit waste and focus on only those activities that add value. This includes meetings - we only hold meetings where they add value to the product delivery. If we take Scrum as an example, there are only 4 proscribed “meetings”:

  1. A daily 15 minute standup
  2. A planning session
  3. A sprint review
  4. A sprint retrospective

The intent of these 4 is to replace the need for most other ad-hoc meetings that traditionally impact team productivity.

If you’re holding a lot of additional meetings, you need to look at the root cause. Why are you having these meetings? Who’s asking for them? What do they achieve? Are the right people in the meeting? Are the wrong people in the meeting (see who spends the meeting on their phone to answer this one)? etc, etc, etc.

You must also understand the distinction between distraction and collaboration. You want to encourage collaboration, but if the team is finding it distracting then, once again, you are probably doing it wrong. Look at mechansims that you can adopt to improve how your teams collaborate. For example, create a social contract that sets rules around collaboration and interuptions. Or, consider adopting pair programming techniques to build collaboration directly into the development cycle.

What are your thoughts? Let me know below.

责编内容by:The Agile Director (源链)。感谢您的支持!

您可能感兴趣的

Defining “Scaling” Agile, Part 1: Creating Cross-F... I keep encountering confusion about what scaling agile is. I’m writing what I think is a 4-part series to define it so we all talk about the same thin...
Innovation Starts At Home…? Mention was made a couple of times last week in the VC’s presentation to the OU about the need to be more responsive in our curriculum design and c...
论敏捷开发的优缺点 踏入软件开发行列时间不算短了,也使用过很多项目管理软件和方法,但是在使用过程中多多少少都会遇到一些问题吧,同行们或多或少也会有相应的体验。近期试用了一下华为最新推出的项目管理工具-华为软件开发云,接触了敏捷开发,产生一些想法。以下是使用体验,仅供同行们参考。 一、敏捷开发技术的几个特点和优势:...
What is an Agile Mindset? Six years later At the end of 2011 I wrote about what makes anagile mindset (in my opinion) and even made a fancy infographic about it: It concentrates on ho...
Growing Agile: The Idea Hackathon A week ago we held a 1 day event – The Idea Hackathon. It all started at Agile Testing Days in Germany in December. Matt Heusser chatted to us (Karen...