It’s a Planv1.12.0

Treat Agile Meetings as Decision Forums, Not Status Theater

Learn how to make Agile meetings useful decision and coordination forums rather than status updates. This guide covers focused agendas, impediments, follow-through, and a practical meeting audit.

Andrii PoluosmakUpdated 7 min read

Every recurring Agile meeting needs a job. It can help your team make a decision, coordinate work, inspect progress toward a goal, or remove an impediment. When the meeting repeats updates people could read elsewhere, change its format.

A ceremony can end with a decision or a shared plan. It can also identify who will address a blocker. Judge it by whether your team leaves ready to act.

Start with the job the meeting must do

Before you change an agenda, write down the work the meeting supports. Identify the decision or coordination problem the team needs to address. Name who must contribute and what should be different by the end.

Give the purpose enough detail to guide preparation. Name the handoff, dependency, shared plan, or improvement the meeting needs to make visible. If the meeting serves several purposes, put them in order and reserve time for the main one.

The Scrum Guide describes Scrum events as formal opportunities to inspect and adapt. Use that standard to decide whether the event helps your team notice a problem and respond. If the meeting produces no decision, adjustment, coordination, or improvement signal, revisit its purpose, participants, or format.

A meeting can confirm that the plan still holds. Give other topics time for the information or smaller group they need. Do not force a decision to fill the final minutes.

A meeting can also help people coordinate work across roles or dependencies. Define what the team needs to coordinate and who needs a shared understanding. Put the purpose in the invitation so attendees can prepare and decide whether to join.

Separate updates from topics that need a conversation

Share a status update when it changes what someone else needs to know or do. Post completed work in writing or keep it visible on the work board when it does not change the team's next move. Use meeting time for a dependency, changed priority, risk, or choice that needs discussion.

The Scrum Guide defines the Daily Scrum as a 15-minute event for Developers to inspect progress toward the Sprint Goal, adapt the Sprint Backlog, and produce an actionable plan for the next day. Shape the conversation around the team's shared work. After a progress update, discuss its effect on the plan.

Connect updates to the Sprint Goal and the work ahead. Give the team room to identify a changed condition or an obstacle that needs coordination. Keep individual progress reports brief when they do not change the shared plan.

When a topic needs detailed problem-solving, capture it and arrange a focused follow-up with the people who can resolve it. Use the stand-up to identify the issue and assign the next conversation. Keep other team members out of an unplanned working session.

A 2026 Cambridge study of 33 stand-up recordings from two teams reported uneven participation and blockers that were not always resolved. In your own meeting, notice who contributes useful information, whether an obstacle keeps returning, and whether someone has taken the next step on a blocker.

Put a decision-ready prompt on the agenda

For each live agenda item, state the question to answer, name the decision-maker or contributors, and specify the result the group needs. Send the agenda early enough for participants to prepare. Label information-only items as updates so people can read them before the meeting.

Set out the decision or coordination need before the meeting begins. Give participants the context they need. Identify whose input matters and whether the group needs to choose a direction, review a plan, or assign follow-up. Remove agenda items without a clear purpose or owner.

A study of 958 employees' work meetings found that agenda use, starting and ending on time, and meeting facilities were positively associated with perceived meeting effectiveness. Send a focused agenda, start on time, and end when the timebox expires.

Timebox each topic to focus the discussion. When time runs out, decide with the information available, assign someone to gather what is missing, or schedule a smaller follow-up. Record the next step so the item does not return without progress.

Set time for each item according to the work it needs. Leave room to confirm decisions and next steps. When the group needs more time, agree how to continue instead of letting the agenda expand without a plan.

Make room for impediments and the next action

Invite people to raise blockers, dependencies, and concerns without blame. Identify what prevents progress, what help the team needs, and who can take the next step.

Separate naming an impediment from solving it. Use a short coordination meeting to identify a decision the team needs. For a technical issue that needs detailed work, capture the problem, invite the people with relevant knowledge, and agree when they will reconnect with the team.

A PM Perspectives summary of research by Meghann Drury and Orla McHugh describes interviews and observations across four Agile teams. In the two kinds of meetings studied, the researchers found teams did not use a rational, linear decision process. Make the decision path visible: state the problem, share what the team knows, hear relevant perspectives, and confirm the next action.

Give participants room to contribute information before the group settles on a course of action. The facilitator can invite input from people close to the work and bring the discussion back to the decision or coordination need. Aim for useful participation, not a speaking turn for every attendee on every topic.

When the team cannot resolve an impediment in the time available, record who will take it forward and when the team will review progress. If the issue needs a separate conversation, invite the people needed to make progress. Bring the result back to the team when it affects the shared plan.

Close with the decision, owner, and follow-through

Before the meeting ends, summarize what changed. Record the question, the decision or current direction, the person responsible for the next action, and when the team will review it. If the group made no decision, state why and name what will move the issue forward.

Give each next action an owner and a check-in point. Record the information or coordination the owner needs to provide. Make the result visible to the people affected by it so the team can follow up between meetings without repeating the whole discussion.

The Scrum Guide calls the Sprint Review a working session where the Scrum Team and stakeholders collaborate on what to do next. Plan the review around the product outcome, feedback, and adaptations to consider. Let the group work through what comes next instead of limiting the session to a presentation of completed work.

Audit one recurring meeting

Choose a meeting that feels repetitive or whose purpose is hard to explain. Review its last few agendas or notes, then complete this audit:

  1. Purpose: Identify the decision, coordination, inspection, or improvement the meeting serves.
  2. Participants: Confirm that each attendee brings information, authority, or work the meeting needs.
  3. Format: Separate updates people can share beforehand from topics that need conversation.
  4. Output: State what the team should decide, change, or assign before the meeting ends.
  5. Follow-through: Choose where the team will record the result, owner, and next check.

If you cannot name the meeting's job, rewrite its invitation and agenda around the team's need. Make it smaller when only one or two people need to talk. Try an asynchronous update when the team has no need for real-time discussion. Keep the ceremony when it helps the team act. Change its format or cancel it when another approach serves the need.

Try the revision for a few cycles. Then review whether the meeting produced useful coordination, surfaced impediments, or clarified what happens next. Ask participants which parts helped and which still felt like status theater. Adjust the purpose, attendees, prompts, or timebox. Treat the change as an experiment in improving the team's work, not a test of whether people can fill a meeting slot.

Put the audit into practice

Pick one recurring Agile meeting this week. Write down the decision or coordination need it serves, then revise the agenda to make that purpose visible. Close the next session by recording the outcome and owner. If the meeting no longer helps the team make progress, change its format or stop holding it.

Key takeaway

Give each recurring meeting a clear job, reserve live time for topics that need discussion, and close with an outcome, an owner, and a follow-up point.

Andrii Poluosmak

Founder

Andrii founded It’s a Plan and leads its product and roadmap, from the open-source edition to Pro for teams. He works with the project’s contributors and the teams that run It’s a Plan.

All posts by Andrii Poluosmak

Put your next project on the board.

The open-source issue tracker you host yourself.