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

So How’s It with Architecture - Up-Front Design or Evolutionary Architecture?

So How’s It with Architecture - Up-Front Design or Evolutionary Architecture?

Where does architecture currently stand? We can say that there are two classic approaches:

Read More

Code Cleanliness: More Than Just Refactoring Part 1

Initially, my intention was to create an article about refactoring. However, the more I pondered the subject, the clearer it became that I would not be writing solely about refactoring. It’s about something much more significant—conveying a vast amount of knowledge, essentially experience, related to code creation. Code that not only works or is well-designed but is most importantly easy to read. When we achieve this skill, we stand on the threshold of professionalism. Programming professionalism.

Read More

Why I Hate These Standups...

Why I Hate These Standups…

I often hear it… that they are a waste of time, just distractions from work, adding no real value…

Read More