Meetings in a Hurry Are Not Effective Ones

Table of Contents

The Importance of Timeboxing in Scrum

The timeboxing is a fundamental technique for many Scrum activities. There is often a misunderstanding that meetings should be fast, leading facilitators to rush participants to finish within the timebox. This haste results in poorly discussed problems and many uninformed decisions.

Time boxing, in this context, serves a different purpose. It is for making conscious decisions on choosing what and what not to talk about during the conversation. It is more for eliminating than for being in a rush.

Strategies for Effective Timeboxed Meetings

As a facilitator aiming for effective timeboxed meetings:

  1. Ensure everybody agrees on the goal of the meeting, the expected outcome, and the decisions that need to be made (e.g., planning meeting - discussing items with defined acceptance criteria, estimated, and having a rough design).

  2. Ensure that an agenda (structured) is agreed upon.

  3. Keep an eye on the time.

  4. If time is running short, say it aloud and remind everyone of the goal, expected outcome, and necessary decisions.

  5. Ask participants what they think they should focus on or eliminate to achieve the results within the timebox.

  6. If time is about to exceed the timebox, make an agreement for another timebox (e.g., extend the meeting for 30 minutes).

  7. Summarize the results.

  8. Consider conducting a short retrospective afterward to find ways to improve the meeting.

By following these guidelines, facilitators can help ensure that timeboxed meetings are productive and decisions are well-informed, without the stress of rushing through discussions.

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

The Natural Order of Refactoring Under the Microscope Part 5: Evolution of Architecture

Architectural Evolution

An essential next step, at a much higher level of abstraction, requires a deep understanding of the system. Based on emerging patterns and developing domain objects, over time we realize the need to modify the architecture. Architectural patterns or the introduction of other architectural mechanisms can assist us. Such transformations may include:

Read More

Technical Leader Worries: Team Members Are Whining

Understanding Team Complaints

It’s very annoying when you hear whining from your team. They complain about boring work, stupid company security policy, wrong management decisions, customers not knowing what they want and changing their minds, and project managers crowding them. Doesn’t it sound familiar?

Read More

Self-Organization - A Myth?

The entire Agile community (and not just Agile) loudly discusses organization. I have the impression that for some time, we’ve been trying to find the holy grail that will allow us to answer the question: “How to manage without managing?”. This time, I’ll play the devil’s advocate.

Read More