"Just in Time" approach to meetings

One of the most common objections I hear when introducing Scrum is this:

“That sounds like a lot of meetings.”

At first glance, it might look that way. Scrum includes five events: Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. But in practice, many teams actually spend less time in meetings when they use Scrum.

That’s because Scrum uses what I like to think of as a “just in time” approach to meetings.

Just Enough, But Not Too Much

A just-in-time approach means meeting at the moment collaboration is most valuable, rather than trying to plan everything far in advance.

Scrum Teams meet briefly and frequently to inspect progress, coordinate their work, and adjust their plans. These short conversations help teams catch problems early before they turn into bigger issues that require long meetings later.

In other words, Scrum Teams meet just enough—but not too much.

Timeboxes Keep Meetings Short

Another reason Scrum meetings stay efficient is that every Scrum event is timeboxed.

A timebox means there is a maximum amount of time allowed for the event—but not a minimum. Teams often finish earlier if they have accomplished the purpose of the meeting.

For example, the Daily Scrum is timeboxed at 15 minutes. That short time limit keeps the conversation focused on inspecting progress toward the Sprint Goal and planning the next 24 hours.

Sprint Planning is timeboxed at 8 hours for a one-month Sprint, but it is usually much shorter. In more than 20 years of working with Scrum, I have only attended one Sprint Planning event that lasted the full eight hours - and it was terrible.

Most teams finish Sprint Planning in an hour or two, especially when they do a good job refining the Product Backlog ahead of time.

Feedback at the Right Time

The Sprint Review allows the team and stakeholders to inspect the product together and discuss what to do next. This frequent feedback helps teams avoid going in the wrong direction for months before discovering the problem.

The Sprint Retrospective provides a regular opportunity for the team to improve how they work together, preventing small issues from turning into larger problems.

Less Meeting Time, Not More

Scrum doesn’t eliminate meetings. Instead, it introduces short, purposeful conversations at the right moments.

Because teams coordinate frequently and inspect their progress often, they avoid the long status meetings, emergency problem-solving sessions, and late project corrections that are common in many traditional environments.

That’s why many teams discover something surprising after adopting Scrum:

They’re not spending more time in meetings.

They’re spending less, because they’re meeting just in time.