Daily Standup Meeting Efficiency

🚨 A Hard Truth: Nothing has been abused more than the Daily Scrum 👉 The Daily isn't open mic night for managers, Product Owners, and Scrum Masters. It’s supposed to be for the Developers to plan out the next 24 hours so they get a step closer to the Sprint Goal. Over the years we’ve: - Forced people to stand up - Made people answer the 3 infamous questions like zombies - Turned it into a status meeting for managers, Scrum Masters, and Product Owners - Stretched it into a 30 to 60 minute problem-solving workshop - Endlessly reviewed Jira tickets one by one - Scheduled it at a time that works for others, not the Developers - Crushed self-management as Scrum Masters by facilitating it for the Developers - Let stakeholders "observe" silently, turning it into surveillance - Treated it as optional, with people wandering in late or skipping entirely 🦃 Guilty as charged! I'm truly sorry I was part of that. Here’s a story from the trenches: A few years ago I was invited to consult with an organization that thought they only needed to "make a few small adjustments." For 45 minutes, a team of project managers sat in front of the team during the Daily, interrogating them, taking notes, and updating Microsoft Project plans in real time. That wasn’t a Daily Scrum, it was a daily status interrogation disguised as Scrum. Here are several ways to make your Daily Scrum effective: ✅ Protect the 15 minutes: ask managers, Product Owners, and even Scrum Masters to allow Developers to have this time without interruption. ✅ Keep it simple: 15 minutes, same place, same time. ✅ Always work toward a Sprint Goal. Stop committing to a fixed number of PBIs. ✅ Use the time to inspect progress toward the Sprint Goal, adapt the Sprint Backlog, and move forward together. ✅ Don't use a Sprint Goal? Start next Sprint. ✅ The three questions are not required. Drop them if they don’t add value. ✅ Scrum Masters, stop inventing "cute" replacements for the three questions. You are impeding self-management. Let Developers design their own structure. ✅ The Daily is not a synchronization meeting. Synchronization should be happening all day long. ✅ Impediments should not wait for the Daily. Raise them as soon as they appear. ✅ Scrum Masters are not required to attend or facilitate the Daily. ✅ If you do attend as a Scrum Master, observe quietly. Stand back, stay silent, and let the Developers own it. ✅ If the Daily is off the rails, use the Retrospective to figure out how to get back to it's purpose and make it healthy. Share your observations and ask Developers how they want to improve it. ⚠️ A plea to all Scrum Masters: For the next week, do not attend your team’s Daily Scrum. 🚪 Seriously, stay out. Hand it back to the Developers. 🤸 If they stumble, good. If it feels awkward, even better. 💡 That is how self-management grows. I promise you this: the world will not end, and your team will survive without you.

Daily standups are NOT status meetings. Your team hates standups because you're doing them wrong. I've seen this in 47 out of 50 teams I've coached: → The Scrum Master asks, "What did you do yesterday?" → Everyone reports to the SM like it's a performance review → The meeting drags on for 30 minutes → Nobody listens to anyone else Here's what actually works: ☑ Team members talk TO each other, not to you ☑ Focus on blockers and collaboration, not updates ☑ Keep it under 15 minutes (set a timer) ☑ Stand in a circle so everyone can see everyone in physical meetings. If it's onlineee Zoom/google meet will keep everyone in a room (Keeping the camera ONNN should be must in that case... to see each other in the meeting.) The standup is for the TEAM to synchronise. Not for YOU to track progress, That's what Jira is for. with 3 questions in Stand-up: “What’s blocking me?” “What can I help with?” “Are we on track to deliver value?” Tip: Next stand-up, start with: 👉 “Who needs help right now?” You’ll instantly shift from status to synergy. 90 Seconds for an individual member in the team. The stand-up went from 15 minutes of noise → 8 minutes of clarity. PS: If your standup takes more than 15 minutes, you're doing project management, not Scrum. ♻️ Repost and share if your team needs to see this.

What if your daily standup... is killing team velocity instead of boosting it? Teams waste 20% more time when standups turn into status reports. Here's the fix. → 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞 1: 𝐒𝐭𝐚𝐭𝐮𝐬 𝐌𝐞𝐞𝐭𝐢𝐧𝐠 𝐓𝐫𝐚𝐩 • Problem: Reports go to manager, not team. • Fix: Shift focus to collaboration. Ask: "What do you need from each other?" → 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞 2: 𝐑𝐚𝐦𝐛𝐥𝐢𝐧𝐠 𝐎𝐟𝐟-𝐓𝐨𝐩𝐢𝐜 • Problem: Lengthy updates bury key points. • Fix: Strict 15-min timebox. Updates: 1 min max per person. → 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞 3: 𝐏𝐚𝐬𝐬𝐢𝐯𝐞 𝐒𝐢𝐥𝐞𝐧𝐜𝐞 • Problem: Issues stay hidden from quiet members. • Fix: Round-robin prompts. Everyone shares: "Yesterday? Today? Blockers?" → 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞 4: 𝐇𝐢𝐝𝐝𝐞𝐧 𝐁𝐥𝐨𝐜𝐤𝐞𝐫𝐬 • Problem: Impediments slow progress unnoticed. • Fix: End with direct question: "Any blockers?" Assign owners immediately. → 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞 5: 𝐓𝐢𝐦𝐞 𝐃𝐫𝐢𝐟𝐭 • Problem: Irregular starts disrupt rhythm. • Fix: Same time daily. Start promptly - even if latecomers join mid-flow. Implement these tomorrow. Teams report 40% faster resolutions. Follow Carlos Shoji for more insights

How to Run More Effective Meetings. 8 research-backed upgrades… 👫 Have Everyone Stand Up Research shows standing meetings are 34% shorter than sitting and lead to more collaboration. 📄 Use Prereads Meetings are best for dialogue, not information sharing. Frame topics in writing and ask attendees to read beforehand. 🤔 Start with a Check-In Build psychological safety with genuine shares of “how are you doing today” at the start. ⏱️ Timebox Dial up focus and engagement by setting a timer on each agenda item. 📆 Kill 30s and 60s No one likes back to back meetings. 30 and 60 minute meetings are a trap, default to 25 and 50 instead. ↪️ Redirect complaints Anytime someone complains, ask them to propose a solution or alternative. No vibes of futility and hopelessness allowed. 📝 Fewer People + Written Notes Meetings get big because people don’t want to be left out. Remedy this with fewer attendees and shared written notes on all decisions made. AI makes this easy now. ☀️ End Early Research shows that meetings that end 10 minutes early due to effective time management boost productivity by up to 30% Which will you try this coming week?

Everyone hates meetings because they’re the default, not the decision. ⏳ We pile people in a room to “figure it out,” with no owner, no pre-work, and a 60-minute calendar block that magically expands to fill itself. The result? Status theater, meandering updates, and nothing that actually moves. Here’s a simple playbook to make meetings not-awful (and actually useful) 🧰 Ask the killer question first: “Could this be async?” – If yes: write a 1-pager, comment in a thread, or record a quick walkthrough. Only meet if there’s real ambiguity or a decision to make. Define the outcome up front. – By the end we will: Decide X, Generate 3 options for Y, or Commit to a plan for Z. If you can’t write that sentence, you’re not ready to meet. Do the pre-work. – Send a one-pager 24 hours ahead. Start with 5 minutes of silent read so everyone begins at context, not catch-up. Invite fewer people. – 2–5 deciders + 1 scribe beats 12 spectators. Everyone else gets notes or a recording. Shorten the slot. – Default to 15 minutes. Add time only if the agenda demands it. Keep a “parking lot” for off-topic items. Assign clear roles. – DRI (owner), Facilitator (keeps time), Scribe (writes decisions), Approver (one person). Many “approvers” = no decision. Close strong. – End with: the decision, owners, deadlines, and the first next step. Ship notes within 10 minutes while context is fresh. Meeting alternatives to try this week: – Decision doc + comments – Async standup (yesterday/today/blockers) – Office hours block instead of recurring status – Living FAQ/playbook page for repeat questions – Annotated screen recording for walkthroughs Copy/paste “Meeting Brief” template: Goal: Type (Decision / Brainstorm / Kickoff / Retro): DRI: Must-have attendees: Pre-read link: Agenda with timestamps: Exit criteria (how we’ll know it worked): Risks / open questions: Next steps (owner + date): If every calendar invite had an outcome, pre-read, and a DRI, most meetings would be half as long and twice as valuable. What’s one change you’ll try this week?

Meetings Shouldn't Be Counted, But Weighed This discussion is oriented around Agile, but (hopefully) my point is broadly applicable... Some organizations measure agility by how many Scrum events they hold. Calendar invites accumulate. Teams find themselves trapped in recurring stand-ups, refinements, reviews, and retros. But doing something just because the Scrum or SAFe guide says so misses the point entirely. A meeting isn’t inherently valuable. Value comes from purpose, effectiveness, and relevance. The number of meetings matters far less than their "weight." A well-structured, well-attended meeting can accomplish in 15 minutes what a poorly designed one might waste an hour failing to achieve. Purpose Over Ritual Effective meetings have a clear, narrow purpose. The best meetings result in a decision made, a problem solved, or a plan clarified. Without that, meetings become status updates or rambling discussions. That’s not agility; it’s bureaucracy. Scrum prescribes five events (including the sprint), but blindly following them turns them into empty rituals. If a daily scrum doesn’t help the team coordinate, it’s a waste. If sprint planning is just backlog-filling, it’s failing to satisfy its purpose - setting up the team for success. The Right People Meetings need exactly the right attendees - no more, no less. Too many, and discussions fragment. Too few, and decisions get delayed (and you need another meeting). The Right Duration Meeting length should match the nature of the conversation and the target outcome. Some decisions take five minutes, others longer. Don't let Outlook defaults dictate duration. Don't schedule every event for its maximum allowable timebox. End meetings early if the outcome is achieved. Dragging out a meeting to fill the slot is waste. Asking attendees to prepare in advance will likely save everyone a lot of time. The Weight of a Meeting A heavy meeting (the good kind) moves work forward, fosters alignment, and resolves ambiguity. A light meeting (the bad kind) wastes time, drains energy, and leaves attendees wondering why they were there. Weight comes from serving a purpose, engaging the right people, and driving meaningful outcomes. Teams should optimize for fewer, weightier meetings. Before scheduling, ask: Is it necessary? Can this be solved asynchronously? See my prior post on "Asynchronous Scrum." What’s the purpose? What needs to be achieved? Who needs to be there? Who is essential? How long should it be? What’s the shortest time needed? What prep work will abbreviate the meeting? Agile Isn’t About Meetings Agile isn’t about planning sessions, stand-ups, refinement meetings, reviews, or retros. It’s about delivering value. Meetings are a means to an end, not an end in and of themselves. Successful teams don’t check off events on a Scrum checklist; they hold only the meetings they need, in the way they need to, to get the job done right. Meetings shouldn’t be counted. They should be weighed.