Global Araç
Standup Notes Template
## Standup — 2026-05-11 **Dün** - Shipped login flow - Reviewed pricing page copy **Bugün** - Start onboarding checklist - Pair on search ranking **Engeller** - none
Daily standup is the single most-attended recurring meeting in modern software teams, and the format “yesterday / today / blockers” is the dominant template — codified in the Scrum Guide (2010 edition by Ken Schwaber and Jeff Sutherland) and adopted across XP, Kanban, and most Agile-adjacent processes. The structure is deliberately constrained: each team member answers the same three questions in 30-60 seconds, the meeting itself caps at 15 minutes regardless of team size, and any deeper discussion gets parked for after the standup so no one’s 14 minutes are wasted on a 2-person debate. The structure works because it forces clarity (what did you actually do yesterday?), surfaces blockers early, and gives everyone a brief shared map of where the team is each day.
Standup happens in three modes: in-person synchronous (everyone gathers, voices the three points, done), distributed-synchronous (Zoom / Meet, same format, slightly slower), and asynchronous (each person posts a written standup in Slack / Discord / Notion). Async standups have grown explosively post-2020 because they accommodate timezone-spread teams and don’t cost the “interrupted morning coding” tax that synchronous standups do — but they only work when written updates are consistent, complete, and actually read by teammates. A copy-paste-friendly markdown template is the difference between a clean weekly Slack record and a graveyard of inconsistent “TBD” entries.
The tool fills three text areas (yesterday, today, blockers) and outputs a clean Markdown-formatted standup update that renders perfectly in Slack, Notion, GitHub comments, Linear/Jira, and any other markdown-aware destination. Bullets are consistent, line breaks survive paste, headings format reliably. Variants: switch between Markdown, Slack-flavored markdown (subtly different bold/italic syntax), plain text for email, and HTML if your destination requires it. Save reusable fragments (your ongoing project list, common blockers) and the tool will auto-suggest them next time.
Nasıl Kullanılır
- Fill in “Yesterday” — what you completed since the last standup (PRs merged, tasks done, decisions made).
- Fill in “Today” — your top 1-3 priorities for today (be specific: not “work on auth”, but “finish session-token refresh PR”).
- Fill in “Blockers” — anything blocking you that someone else needs to unblock (or “none” if clean).
- Click Generate — copy the formatted output.
- Paste into your team’s standup channel (Slack, Discord) or call the points off if synchronous.
Ne Zaman Kullanılır
- Daily async standup posts in Slack, Discord, Notion, or your team chat tool.
- Preparing notes for a synchronous standup so you don’t fumble when called on.
- Catching up a teammate or manager who missed today’s standup.
- Building a personal log of what you accomplish each day (paste into your private notes too).
Ne Zaman Kullanılmaz
- One-off team meetings — use a meeting agenda template instead.
- Status reports for stakeholders — those need different framing (outcomes vs activity, milestones vs daily progress).
- Sprint planning or retrospectives — those have different templates with different sections.
- Solo project journals — the standup format is calibrated for team coordination; solo work benefits from different structures (Pomodoro logs, GTD next-actions).
Yaygın Kullanım Senaryoları
- Verifying a number or output before passing it on
- Quick use during a typical workday
- Pre-decision sanity-check on inputs and outputs
- Educational use — demonstrating the underlying concept
Sık Sorulan Sorular
Should I include task IDs (JIRA, Linear)?
Yes — link them. “Yesterday: finished PROJ-1234 (auth refresh)” is much more useful than “finished auth refresh.” Teammates can click through, your manager has a paper trail, and the future you reading the channel in 3 weeks knows exactly what shipped.
What counts as a blocker vs a slow-moving thing?
A blocker is anything where you genuinely can’t make progress without external action — waiting on PR review, waiting on design specs, waiting on access permissions, waiting on a third-party API. “The build is slow” is not a blocker (you can keep working); “build is broken on main and I need someone to fix it before I can run tests” is a blocker. Be specific so the team knows exactly who needs to unblock you.
How long should each standup be?
Async written: 30-90 seconds to read for teammates. Sync verbal: 30-60 seconds per person. Whole meeting: 15 minutes hard cap regardless of team size — if your team has 12 people, your standup needs to move at 50 seconds per person. Teams larger than ~10 should split into sub-team standups.
Should I include “in progress” items in yesterday or today?
Today. Yesterday should describe completed work; today should describe active in-progress + planned items. If something’s stuck in “almost done” for multiple standups, flag it — that’s usually a sign of either an underestimated task or a hidden blocker.
What if I have nothing to say?
Be honest: “Yesterday: focused on code review and PR comments. Today: starting work on PROJ-5678. No blockers.” It’s fine to have light days. What’s not fine: copy-pasting the same content multiple days in a row (sign you should be flagging a stuck task) or skipping standup entirely (breaks the team’s shared visibility).
How does this differ from a weekly status update?
Standup = daily, granular, focused on the next 24 hours and immediate blockers. Weekly status = broader strokes, milestone progress, decisions needed from leadership, weekly themes. Use the standup template for daily, the weekly-goal-tracker tool for weekly. They serve different audiences and decision frequencies.