Daily Standup Template

---
title: "Daily Standup Template"
methodology: "agile"
complexity: "intermediate"
owner: "mirichard"
updated: "2026-09-19"
primary_principles: ["collaborative-leadership", "adaptability"]
secondary_principles: ["continuous-learning"]
principle_rationale: "Helps developers inspect Sprint Goal progress, expose impediments and adapt their daily plan through a short shared discussion."
---

# Daily Standup Template

## When to Use

- During a Scrum sprint when developers inspect progress toward the Sprint Goal.
- When a short coordination discussion can expose impediments and adjust the daily plan.

## When NOT to Use

- As individual status reporting to a manager rather than team coordination.
- Do not impose enterprise coordination or approval layers where team size and risk do not justify them. See [Maximum governance](../../../../../docs/principles/anti-patterns.md#maximum-governance).

## Pairs Well With

- [Sprint Planning Template](../../../../../domains/delivery/templates/agile/sprint_planning_template.md).
- [Issue Log Template](../../../../../domains/delivery/templates/traditional/Traditional/Templates/issue_log_template.md).

Selection context: Team domain; agile methodology; intermediate complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../../../meta/architecture-research/800-801-context-assessment-model.md).

## Meeting Information
- **Date**: [Date]
- **Sprint**: [Sprint Number]
- **Facilitator**: [Developer-selected facilitator, if needed]
- **Duration**: 15 minutes
- **Time**: [Time]
- **Location/Platform**: [Location or virtual platform]

## Purpose and facilitation

In Scrum, Developers use this 15-minute event to inspect progress toward the Sprint Goal and adjust their plan. They choose the format. Use only the sections that help that purpose; move detailed problem solving and announcements outside the event.

## Standup Format

### Optional prompts
These prompts are one possible format, not required Scrum questions:

1. **What did you accomplish yesterday?**
2. **What will you work on today?**
3. **Are there any impediments or blockers?**

### Team Member Updates

#### [Team Member 1 Name]
- **Yesterday**: [Work completed]
- **Today**: [Planned work]
- **Blockers**: [Any impediments]
- **Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked

#### [Team Member 2 Name]
- **Yesterday**: [Work completed]
- **Today**: [Planned work]
- **Blockers**: [Any impediments]
- **Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked

#### [Team Member 3 Name]
- **Yesterday**: [Work completed]
- **Today**: [Planned work]
- **Blockers**: [Any impediments]
- **Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked

## Sprint Progress Tracking

### Sprint Goal Reminder
**Goal**: [Current sprint goal]

### Sprint Backlog Status
| Story | Owner | Status | Progress | Blockers |
|-------|-------|--------|----------|----------|
| [Story 1] | [Owner] | In Progress | 60% | [Blockers] |
| [Story 2] | [Owner] | Done | 100% | None |
| [Story 3] | [Owner] | To Do | 0% | [Blockers] |

### Sprint Burndown
- **Total Story Points**: [Total]
- **Completed**: [Completed points]
- **Remaining**: [Remaining points]
- **Days Left**: [Days remaining in sprint]
- **Trend**: 📈 Ahead / ➡️ On Track / 📉 Behind

## Impediments Tracking

### New Impediments Raised
| Impediment | Reporter | Impact | Priority | Owner | Target Resolution |
|------------|----------|--------|----------|-------|------------------|
| [Impediment 1] | [Name] | High | Critical | [Owner] | [Date] |

### Impediments Status Update
| Impediment | Status | Owner | Update | Next Steps |
|------------|--------|-------|--------|------------|
| [Previous impediment] | In Progress | [Owner] | [Update] | [Next steps] |

### Resolved Impediments
- [Impediment]: Resolved by [Owner] on [Date]

## Action Items
- [ ] [Action 1] - Owner: [Name] - Due: [Date]
- [ ] [Action 2] - Owner: [Name] - Due: [Date]
- [ ] [Action 3] - Owner: [Name] - Due: [Date]

## Team Collaboration

### Cross-Team Dependencies
- [Dependency 1]: Status [Status] - Contact [Person]
- [Dependency 2]: Status [Status] - Contact [Person]

### Knowledge Sharing Opportunities
- [Team member] can help with [Topic]
- [Team member] needs assistance with [Topic]

### Pair Programming/Code Review
- [Pair 1]: Working on [Story/Feature]
- [Review needed]: [Story] by [Reviewer]

## Meeting Notes

### Key Decisions Made
- [Decision 1]: [Description and rationale]
- [Decision 2]: [Description and rationale]

### Important Announcements
- [Announcement 1]
- [Announcement 2]

### Follow-up Items
- [Follow-up 1]: [Owner] to [Action] by [Date]
- [Follow-up 2]: [Owner] to [Action] by [Date]

## Standup Health Check

### Participation
- **Attendance**: [X]/[Total] team members present
- **Engagement**: 🟢 High / 🟡 Medium / 🔴 Low
- **Focus**: 🟢 On Track / 🟡 Some Drift / 🔴 Off Topic

### Time Management
- **Start Time**: [Actual start time]
- **End Time**: [Actual end time]
- **Duration**: [Actual duration]
- **Efficiency**: 🟢 Good / 🟡 Acceptable / 🔴 Needs Improvement

### Improvement Opportunities
- [Observation 1]: [Suggestion for improvement]
- [Observation 2]: [Suggestion for improvement]

## Next Standup
- **Date**: [Next meeting date]
- **Focus Areas**: [Any specific areas to emphasize]
- **Special Topics**: [Any additional items to discuss]

---

**Meeting Facilitated by**: [Developer-selected facilitator, if needed]
**Notes Taken by**: [Note taker]  
**Next Standup**: [Date and Time]

*Daily synchronization for team alignment and progress*


Framework reference: [Scrum Guide, November 2020](https://scrumguides.org/scrum-guide.html).