Daily Standup Template for Agile Teams

Free Daily Standup Template

The daily standup (or daily Scrum) is a 15-minute synchronisation point for the development team. Done well, it surfaces blockers early and keeps everyone aligned without becoming a status report to management.

---

Standard Standup Template (In-Person or Video)

Each team member answers these three questions:

**1. What did I complete yesterday?**
[Specific tasks or stories finished — link to tickets where helpful]

**2. What will I work on today?**
[Specific tasks planned — be concrete, not vague]

**3. Is anything blocking me?**
[Blockers, dependencies, or things slowing progress — or "No blockers"]

Time limit: 15 minutes maximum for the whole team. Go around the room once. Save all detailed discussions for after the standup.

---

Async Standup Template (Slack / Teams)

For distributed or remote-first teams, post this message in the team's standup channel each morning:

📅 Standup — [Day, Date]

✅ Yesterday:
- [Task 1]
- [Task 2]

🎯 Today:
- [Task 1]
- [Task 2]

🚧 Blockers:
- [Blocker] OR None

---

Sprint-Level Standup Board

At the start of each standup, update your sprint board so the team can see actual progress against the sprint goal.

| Story | Status | Owner | Blockers | |---|---|---|---| | [Story name / JIRA-123] | To Do / In Progress / In Review / Done | [Name] | [Yes/No] | | | | | | | | | | |

Sprint Goal: [Paste the sprint goal here as a reminder] Days remaining: [X of Y] Stories completed: [X of Y]

---

Facilitator Checklist

Run through this before ending the standup:

• [ ] Every team member has spoken
• [ ] Blockers have been noted and an owner assigned
• [ ] Any discussions that ran long have been parked for a follow-up
• [ ] Sprint board is up to date
• [ ] No unplanned work was added to the sprint without discussion

---

Standup Anti-Patterns to Avoid

The status report. The standup is for the team, not for the Scrum Master or manager. If team members are reporting to a manager rather than co-ordinating with each other, it's a status meeting in disguise.

Solving problems in the standup. When a blocker surfaces, the instinct is to jump into problem-solving mode. Resist it. Note the blocker, assign an owner to resolve it, and schedule a follow-up. Don't let one thread derail the whole team.

Reading out ticket names. "I worked on PROJ-234" tells nobody anything. "I finished the password reset API endpoint" is useful. Describe the work, not the ticket ID.

Skipping days. A standup only has value if it's consistent. One-off skips become habits.

Going over 15 minutes. Timeboxing is a skill. If standups routinely run long, the Scrum Master should intervene. Common causes: too many people in the standup, discussions that belong elsewhere, or team members not preparing before joining.

---

Async Standup Tips

For distributed teams across time zones, async standups are often more effective than synchronous ones:

1. Set a deadline. Everyone posts their standup update by 10am local time (or a time that works for your time zones).
2. Use threads, not a wall of messages. Each person's update should be one message — not three separate messages for each question.
3. React to blockers immediately. When someone posts a blocker, teammates should acknowledge and help within an hour, not at the next synchronous meeting.
4. Review async updates before your first sync. Use the async updates to make synchronous meetings shorter and more targeted.

---

Standup Formats Beyond the Three Questions

The classic three questions work well, but some teams use variations:

Walk the board. Instead of going person by person, go ticket by ticket from right to left on the sprint board (Done → In Progress → To Do). This keeps focus on the sprint goal rather than individuals.

Yesterday / Today / Blockers + Confidence check. Add a fourth question: "What's your confidence level (1–5) that the sprint goal will be met?" This surfaces risk early without requiring a formal sprint review.

Two questions only. "What am I working on today, and is anything blocking me?" Drop the "yesterday" question for teams that keep the board up to date in real time — it's redundant if everyone can see ticket status.