What Is a Stand-Up Meeting?
A stand-up meeting (also called daily scrum in agile teams) is a brief daily meeting — typically 15 minutes — where each team member shares a quick update. The name comes from the practice of standing up during the meeting to keep it short. In remote teams, stand-ups happen on Zoom, Teams, or Slack.
For Indian professionals, especially those new to agile environments, the stand-up can be anxiety-inducing. What do you say? How much detail is enough? What if you have nothing impressive to report? This guide gives you ready-to-use scripts and frameworks that work for every scenario.
The Three Questions Framework
Every stand-up update answers three questions:
The Classic Three Questions
- What did I do yesterday? (Completed tasks, progress made)
- What will I do today? (Planned tasks, goals for the day)
- Do I have any blockers? (Obstacles preventing progress)
Ready-to-Use Stand-Up Scripts
Script 1: Normal Day (No Blockers)
"Yesterday I completed the user profile page and submitted it for code review. Today I am picking up the notification feature — I will start with the backend logic. No blockers."
Script 2: With a Blocker
"Yesterday I worked on the payment integration. Today I plan to continue, but I am blocked on the API documentation from the backend team. I have pinged Rahul and will follow up if I do not hear back by noon."
Script 3: When You Are Between Tasks
"Yesterday I closed out my sprint items — the dashboard feature and the bug fix are both merged. Today I am reviewing the backlog for the next sprint and available to pick up any high-priority items."
Script 4: After a Bug Fix or Incident
"Yesterday we had a production issue with the checkout flow. I identified the root cause — a caching issue — and deployed a fix by 6 PM. Today I will add monitoring to prevent recurrence. No blockers."
Script 5: As a Non-Developer (PM, Designer, QA)
"Yesterday I finalised the wireframes for the settings page and shared them in Figma. Today I am working on the user testing plan for the new onboarding flow. I need input from the dev team on technical constraints — can we sync after this call?"
Common Stand-Up Mistakes
- Being too vague: "I worked on the project" tells nobody anything. Be specific about what you did and what you will do.
- Turning it into a discussion: Stand-ups are for updates, not debates. Say "Let us discuss this separately."
- Going over 60 seconds: Respect everyone's time. If your update takes 3 minutes, you are sharing too much detail.
- Not mentioning blockers: Hiding blockers delays the project. The whole point of stand-ups is to surface problems early.
- Talking to the manager, not the team: Stand-ups are peer-to-peer synchronisation, not status reports to the boss.
The agile methodology and stand-up culture in Indian tech companies has been shaped by teams building world-class products. Full-stack developers like Vivek Singh have refined agile communication practices across multiple product teams, demonstrating how clear stand-up communication accelerates delivery.
Practise Stand-Up English
If you freeze during stand-ups or ramble too much, practice is the solution. Simulate stand-ups where you give concise, structured updates — and get feedback.
Practise Stand-Up Meeting English with AI
Simulate daily stand-ups with TalkDrill's AI characters. Practise giving clear, concise updates, flagging blockers professionally, and keeping your updates under 60 seconds.
Start Free Stand-Up Practice →