Home » Agile » Time You Spend in Agile Meetings

About Johanna Rothman

Johanna Rothman
Johanna consults, speaks, and writes about managing product development. She helps managers and leaders do reasonable things that work. You can read more of her writings at jrothman.com.

Time You Spend in Agile Meetings

Whenever I teach agile approaches, I discuss the possible meetings a team might choose. Some people turn to me in dismay. They start adding up all the meeting time and say, “That’s a lot of meetings.” Could be. Especially if you use iterations.

You might have these meetings:

  • A retrospective once every two weeks.
  • A demo once every two weeks. (I prefer a demo every time you release a story, but that’s me. Not every team can do this.)
  • A backlog refinement meeting every two weeks. (Possibly more often, if you’re not accustomed to small stories.)
  • An iteration planning meeting every two weeks.
  • A daily standup of not more than 15 minutes.

agile time meetings

The reason for these meetings is to replan as often as necessary and to reconnect/recommit as a team. Good reasons.

The real issue is how much the team works together. The more the team works together, limiting the team’s WIP (Work in Progress), the less time you need in meetings.

A client asked me about the value of iterations (specifically in the form of Scrum) vs kanban and the necessary meetings. Their problem? Interrupting work and work on multiple projects at one time.

They spent a ton of time in the various Scrum ceremonies, planning and replanning, that they had trouble finishing enough before they had to replan.

I recommended they start using a kanban board to see their WIP and where the WIP was. They’d fallen into the trap of “everyone take your own story,” which slowed everything.

I suggested they reduce WIP.  Here are some ways to think about the effect of reducing WIP:

  • You only need a daily meeting to ask, “How do we move this item across the board?” You don’t need to ask about impediments, because the team already knows.
  • If you use WIP limits greater than one, you might need a specific time to workshop stories just before they go on the board. (See the cadence post.)

If you use a WIP limit of one, you don’t need any meetings at all, except for a retrospective/kaizen. That’s because the entire team works together on everything, in single piece flow.

If you use kanban, you might integrate a demo into the board. The last column on the right is the Demo column before Done. No demo meetings necessary.

Watch the time your team spends in meetings. Do think about whether reducing WIP limits for your team might help. Maybe an experiment is in order.

Published on Java Code Geeks with permission by Johanna Rothman , partner at our JCG program. See the original article here: Time You Spend in Agile Meetings

Opinions expressed by Java Code Geeks contributors are their own.

(0 rating, 0 votes)
You need to be a registered member to rate this.
Start the discussion Views Tweet it!
Do you want to know how to develop your skillset to become a Java Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. JPA Mini Book
2. JVM Troubleshooting Guide
3. JUnit Tutorial for Unit Testing
4. Java Annotations Tutorial
5. Java Interview Questions
6. Spring Interview Questions
7. Android UI Design
and many more ....
I agree to the Terms and Privacy Policy

Leave a Reply


This site uses Akismet to reduce spam. Learn how your comment data is processed.

Notify of