Daily standup and sprint review in Software Engineering - Step-by-Step Execution

Concept Flow - Daily standup and sprint review

Start of Sprint

↓

Daily Standup Meeting

↓

Team shares progress

↓

Identify blockers

↓

Adjust daily plans

↓

Sprint continues

↓

Sprint Review Meeting

↓

Demonstrate completed work

↓

Gather feedback

↓

Plan next sprint

The flow shows how daily standups happen every day during a sprint to track progress and blockers, leading up to the sprint review where the team demonstrates work and plans next steps.

Execution Sample

Software Engineering

Day 1: Standup - Share progress, blockers
Day 2: Standup - Share progress, blockers
...
Day N: Sprint Review - Demo work, get feedback

This sequence shows daily standups where the team shares updates and blockers, followed by a sprint review at the end to demonstrate work and gather feedback.

Analysis Table

Day	Meeting Type	Team Action	Outcome
1	Daily Standup	Share what was done yesterday, plan today, mention blockers	Team aligned, blockers identified
2	Daily Standup	Update progress, discuss new blockers	Adjust daily tasks
3	Daily Standup	Continue updates and blockers discussion	Keep sprint on track
...	...	...	...
N	Sprint Review	Demonstrate completed work, gather feedback	Feedback collected, next sprint planned

💡 Sprint ends after review; feedback informs next sprint planning

State Tracker

Day	Progress Shared	Blockers Identified	Adjustments Made	Feedback Collected
1	Yes	Yes	Yes	No
2	Yes	Yes	Yes	No
3	Yes	Yes	Yes	No
N	Yes	No	No	Yes

Key Insights - 3 Insights

Why do daily standups happen every day instead of just once?

Daily standups keep the team aligned on progress and blockers frequently, as shown in execution_table rows 1-3, allowing quick adjustments to stay on track.

What is the main difference between a daily standup and a sprint review?

Daily standups focus on quick updates and blockers (rows 1-3), while sprint review (row N) is for demonstrating completed work and gathering feedback.

Why is feedback collected only during the sprint review and not daily standups?

Feedback requires reviewing completed work, which happens at sprint end (row N), while daily standups focus on ongoing progress and immediate blockers.

Visual Quiz - 3 Questions

Look at the execution_table, on which day does the team demonstrate completed work?

A Day N

B Day 2

C Day 1

D Every day

💡 Hint

Check the 'Meeting Type' and 'Team Action' columns in the last row of execution_table.

According to variable_tracker, on which days are blockers identified?

A Only on Day 1

B Only on Day N

C Every day except Day N

D No blockers identified

💡 Hint

Look at the 'Blockers Identified' column for each day in variable_tracker.

If the team skips daily standups, what impact would you expect on the sprint?

A No impact, sprint review covers everything

B Blockers might not be found early, causing delays

C Feedback would be collected daily

D Sprint would finish earlier

💡 Hint

Refer to key_moments explaining the purpose of daily standups and blocker identification.

Concept Snapshot

Daily standup: short daily meeting to share progress, plan, and blockers.
Sprint review: meeting at sprint end to demo work and get feedback.
Standups keep team aligned daily.
Review helps improve next sprint.
Both are key Agile ceremonies.

Full Transcript

Daily standups happen every day during a sprint where the team shares what they did, what they will do, and any blockers. This keeps everyone aligned and helps solve problems quickly. At the end of the sprint, the sprint review meeting happens where the team shows the completed work to stakeholders and collects feedback. This feedback helps plan the next sprint. The daily standups focus on progress and blockers, while the sprint review focuses on demonstration and feedback. Skipping daily standups can cause blockers to go unnoticed, risking delays. Both meetings are important for smooth Agile development.

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