Daily Standups: Keeping the Team on Track

Daily standups are short, focused meetings that help development teams stay aligned and aware of each other’s progress. Typically lasting 10-15 minutes, these meetings happen at the start of the workday, where each team member gives a quick update on their work. The purpose is to improve communication, identify blockers, and ensure everyone is moving in the same direction. Standups are not meant to be deep discussions or problem-solving sessions; instead, they serve as a quick check-in to keep the project running smoothly.

During a standup, each team member should answer three key questions:

  1. What did I work on yesterday? – A brief summary of completed tasks.
  2. What am I working on today? – What they plan to accomplish before the next standup.
  3. Do I have any blockers? – Anything preventing progress that needs attention.

These updates should be short and to the point, avoiding unnecessary technical details. If a blocker needs discussion, it should be noted and handled in a separate meeting with the relevant people after the standup. This keeps the meeting from dragging on and allows others to continue their work without delay.

One of the biggest mistakes in a standup is turning it into a debugging session or a full-blown design discussion. Standups are not the time to share screens and dive into code problems. If someone is stuck on an issue, they should mention it as a blocker, and the team can decide who will help them afterward. Similarly, standups should avoid unnecessary storytelling or off-topic conversations. The goal is efficiency—keeping everyone updated and ensuring no one is blocked—so that the team can move forward productively.

Meeting with the Stakeholder: How to Run an Effective Meeting

Meeting with a stakeholder is an essential part of any project, as it allows teams to gather requirements, understand expectations, and ensure they are building something valuable. Since this is a part-time class meeting only on Monday, Wednesday, and Thursday, teams need to use their time wisely when communicating with stakeholders. Meetings should be structured, focused on gathering key insights, and followed up with clear action items. Having an agenda and preparing questions in advance will help make the most of the limited time available.

Tips for Running a Successful Stakeholder Meeting

  1. Start with a Clear Agenda – Outline what you want to discuss ahead of time and share it with the stakeholder so they know what to expect.
  2. Ask Open-Ended Questions – Focus on understanding the stakeholder’s needs, pain points, and goals rather than making assumptions.
  3. Take Notes & Record Key Takeaways – Capture important points so nothing gets lost between meetings.
  4. Clarify Expectations & Priorities – Determine what features or functionality matter most to the stakeholder.
  5. Keep it Professional & Respect Time – Stay on track, be mindful of time, and avoid long-winded explanations.

How to Approach the First Meeting

Example Meeting Recording from Previous Students:

https://www.dropbox.com/scl/fi/673y8jk7pm02kskc4sb14/PoetryGroup_InceptionMeeting.mp4?rlkey=213u6jz1ccogdxjk7nce31v6n&st=nj32z5hj&dl=0