Module: Meetings and standups

Daily standup sentences

Daily Standup Sentences - Markdown Format

Here's a collection of sentences, categorized for common standup updates. Mix and match to fit your situation!


1. Yesterday - What did I accomplish?

  • Yesterday, I finished implementing the user authentication flow.
  • I completed the initial design mockups for the new dashboard.
  • I resolved the bug causing intermittent crashes on iOS.
  • I spent yesterday refactoring the database query logic for improved performance.
  • I worked on writing unit tests for the payment processing module.
  • I documented the API endpoints for the new feature.
  • I collaborated with [Team Member] on the integration of the third-party library.
  • I addressed the feedback from code review on [Pull Request #].
  • I researched potential solutions for [Problem/Challenge].
  • I prepared the environment for the upcoming deployment.

2. Today - What will I work on?

  • Today, I'll be focusing on integrating the front-end with the back-end API.
  • I plan to start working on the implementation of the search functionality.
  • I'm going to investigate the performance issues reported in production.
  • Today I'll be writing tests for the new feature branch.
  • I'll be working on updating the documentation based on recent changes.
  • I'm planning to pair program with [Team Member] on [Task].
  • I'll be addressing the remaining items on the backlog for this sprint.
  • I'm going to focus on optimizing the image loading process.
  • I'll be working on creating a proof-of-concept for [New Idea].
  • Today, I'll be reviewing pull requests.

3. Blockers - Are there any impediments?

  • I'm blocked waiting for access to the staging environment.
  • I'm currently blocked by a dependency on [Team Member]'s work.
  • I'm facing an issue with [Technology/Tool] and need some assistance.
  • I'm blocked because I'm unsure about the best approach for [Problem].
  • I'm waiting for clarification on the requirements for [Feature].
  • I'm blocked by a third-party API that is currently down.
  • I'm having trouble reproducing the bug reported by QA.
  • I need help with debugging [Specific Issue].
  • I'm blocked until I can get feedback on [Deliverable].
  • No blockers at this time.

4. Combining all three - Full Standup Updates (Examples)

  • "Yesterday, I finished implementing the user authentication flow. Today, I'll be focusing on integrating the front-end with the back-end API. No blockers."
  • "I completed the initial design mockups for the new dashboard yesterday. Today I'll be working on updating the documentation. I'm blocked waiting for access to the staging environment."
  • "I resolved the bug causing intermittent crashes on iOS yesterday. Today, I'm going to investigate the performance issues reported in production. I'm currently blocked by a dependency on [Team Member]'s work."
  • "Yesterday I worked on writing unit tests. Today I'll be addressing the remaining items on the backlog. I need help with debugging [Specific Issue]."
  • "I collaborated with [Team Member] on the integration of the third-party library yesterday. Today I'll be reviewing pull requests. No blockers."

5. Quick/Concise Updates

  • "Auth flow done, integrating front-end today, no blockers."
  • "Mockups complete, documentation updates today, blocked on staging access."
  • "Bug fix deployed, investigating performance, dependency on [Team Member]."
  • "Unit tests written, backlog items today, need help with debugging."
  • "Integration complete, reviewing PRs, all clear."

6. Offering Help

  • "I have some bandwidth if anyone needs help with [Skill/Area]."
  • "I'm familiar with [Technology/Tool] if anyone is running into issues."
  • "Happy to pair program on [Task] if anyone is interested."

Important Notes:

  • Keep it concise: Aim for updates that take no more than 1-2 minutes per person.
  • Focus on value: Highlight what you've done that contributes to the sprint goal.
  • Be honest about blockers: Don't hesitate to ask for help.
  • Be specific: Avoid vague statements like "I worked on the project." Instead, say "I implemented the user profile page."
  • Tailor to your team: Adjust these sentences to fit your team's specific needs and workflow.