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.