Daily standup and sprint review in Software Engineering - Full Explanation

Introduction

Teams working on projects often need quick ways to share progress and adjust plans. Without regular check-ins, problems can go unnoticed and work may not align with goals. Daily standups and sprint reviews help teams stay connected and focused.

Explanation

Daily Standup

A daily standup is a short meeting held every day, usually lasting 10-15 minutes. Team members quickly share what they did yesterday, what they plan to do today, and any obstacles they face. This keeps everyone informed and helps spot issues early.

Daily standups provide a fast, daily update to keep the team aligned and identify blockers.

Sprint Review

A sprint review happens at the end of a sprint, which is a set period of work, often 1-4 weeks. The team shows what they have completed to stakeholders and discusses what went well and what could improve. This meeting helps gather feedback and plan the next steps.

Sprint reviews allow the team to demonstrate progress and get feedback to improve future work.

Real World Analogy

Imagine a sports team that meets briefly before each practice to share how they trained and any injuries, then at the end of the season, they review their games to celebrate wins and learn from losses. This keeps the team coordinated and improving.

Daily Standup → The quick team huddle before practice where players share updates and issues

Sprint Review → The end-of-season meeting where the team reviews performance and plans improvements

Diagram

Diagram

┌───────────────┐       ┌───────────────┐
│ Daily Standup │──────▶│ Sprint Review │
└───────────────┘       └───────────────┘
       │                       ▲        
       │                       │        
       └───────────────┬───────┘        
                       │                
               Continuous Feedback      

This diagram shows the daily standup feeding into the sprint review, creating a cycle of continuous feedback.

Key Facts

Daily Standup → A short daily meeting where team members share progress and obstacles.

Sprint → A fixed time period, usually 1-4 weeks, during which work is completed.

Sprint Review → A meeting at the end of a sprint to show completed work and gather feedback.

Blocker → An issue that stops a team member from making progress.

Common Confusions

Daily standups are long status meetings.

Daily standups are long status meetings. Daily standups are meant to be brief, focused updates lasting about 10-15 minutes, not detailed reports.

Sprint reviews are only for the team.

Sprint reviews are only for the team. Sprint reviews include stakeholders outside the team to gather feedback and align on goals.

Summary

Daily standups are short daily meetings to share progress and spot problems quickly.

Sprint reviews happen at the end of a sprint to show work done and get feedback.

Together, these meetings help teams stay aligned and improve continuously.

Practice

1. What is the main purpose of a daily standup meeting in agile teams?

easy

A. To conduct detailed technical discussions

B. To review the completed sprint work with stakeholders

C. To plan the entire project timeline

D. To share quick updates and identify any blockers

Solution

1. Step 1: Understand the daily standup purpose

   Daily standups are short meetings where team members share what they did, what they will do, and any problems.

2. Step 2: Compare options with this purpose

   Only To share quick updates and identify any blockers matches this purpose by focusing on quick updates and blockers.

3. Final Answer:

   To share quick updates and identify any blockers -> Option D

4. Quick Check:

   Daily standup = quick updates and blockers [OK]

Hint: Daily standups = quick updates, not detailed reviews [OK]

Common Mistakes:

• Confusing daily standup with sprint review
• Thinking daily standup is for detailed planning
• Assuming daily standup includes stakeholders

2. Which of the following is the correct typical order of topics in a daily standup?

easy

A. Sprint goals, completed tasks, next sprint planning

B. What I did yesterday, what I will do today, any blockers

C. Project budget, resource allocation, risk assessment

D. Code review, testing results, deployment schedule

Solution

1. Step 1: Recall daily standup structure

   Daily standups usually follow: what was done yesterday, plans for today, and blockers.

2. Step 2: Match options to this structure

   What I did yesterday, what I will do today, any blockers matches this order exactly, others describe different meetings or topics.

3. Final Answer:

   What I did yesterday, what I will do today, any blockers -> Option B

4. Quick Check:

   Daily standup order = yesterday, today, blockers [OK]

Hint: Daily standup = yesterday, today, blockers order [OK]

Common Mistakes:

• Mixing sprint review topics with daily standup
• Including unrelated project management topics
• Confusing order of updates

3. During a sprint review, the team demonstrates completed features. Which of the following is NOT a typical outcome of this meeting?

medium

A. Assigning daily tasks for the team members

B. Gathering feedback from stakeholders

C. Planning improvements for the next sprint

D. Celebrating completed work and achievements

Solution

1. Step 1: Understand sprint review goals

   Sprint reviews focus on showing work done, getting feedback, and planning improvements.

2. Step 2: Identify which option does not fit

   Assigning daily tasks is done in daily standups or sprint planning, not sprint review.

3. Final Answer:

   Assigning daily tasks for the team members -> Option A

4. Quick Check:

   Sprint review ≠ assigning daily tasks [OK]

Hint: Sprint review = feedback and demo, not daily task assignment [OK]

Common Mistakes:

• Confusing sprint review with sprint planning
• Thinking sprint review sets daily tasks
• Ignoring the feedback and demo focus

4. A team member says in the daily standup: "I am blocked because I need access to the database." What is the best way to fix this issue during the meeting?

medium

A. Ignore it and continue with the meeting

B. Ask the team member to fix it alone

C. Note the blocker and assign someone to help after the meeting

D. Delay the entire meeting until the blocker is resolved

Solution

1. Step 1: Identify proper handling of blockers in daily standup

   Blockers should be noted and addressed quickly but not delay the meeting.

2. Step 2: Evaluate options for best practice

   Note the blocker and assign someone to help after the meeting correctly notes the blocker and plans help after the meeting, keeping the standup efficient.

3. Final Answer:

   Note the blocker and assign someone to help after the meeting -> Option C

4. Quick Check:

   Blockers = note and resolve after meeting [OK]

Hint: Blockers noted, help assigned after standup, don't delay meeting [OK]

Common Mistakes:

• Ignoring blockers during standup
• Trying to solve blockers during the standup
• Delaying the whole meeting for one issue

5. A sprint review shows that some features are incomplete due to underestimated tasks. How should the team use this information in the next sprint planning?

hard

A. Include buffer time and re-estimate tasks more carefully

B. Assign all tasks to the team lead to control progress

C. Reduce the sprint length to avoid delays

D. Ignore the incomplete features and move on

Solution

1. Step 1: Analyze the impact of incomplete features

   Incomplete features indicate estimation or planning issues that need adjustment.

2. Step 2: Determine best practice for next sprint planning

   Including buffer time and better estimation helps avoid repeating the problem, as in Include buffer time and re-estimate tasks more carefully.

3. Final Answer:

   Include buffer time and re-estimate tasks more carefully -> Option A

4. Quick Check:

   Use feedback to improve estimates and planning [OK]

Hint: Use sprint review feedback to improve next sprint estimates [OK]

Common Mistakes:

• Ignoring feedback from sprint review
• Changing sprint length without reason
• Centralizing tasks to one person unnecessarily