Daily standup and sprint review in Software Engineering - Time & Space Complexity

Time Complexity: Daily standup and sprint review

O(n)

Understanding Time Complexity

We want to understand how the time spent in daily standups and sprint reviews grows as the team size or sprint length changes.

How does the meeting duration scale when more people join or when the sprint covers more work?

Scenario Under Consideration

Analyze the time complexity of the following meeting structure.

// Daily Standup
for each team member:
  speak for fixed time (e.g., 1-2 minutes)

// Sprint Review
for each completed work item:
  present demo or explanation
  answer questions

This shows how daily standups involve each team member briefly, while sprint reviews involve presenting each completed work item.

Identify Repeating Operations

Look at what repeats during these meetings.

• Primary operation: Each team member speaks once in the daily standup; each completed work item is presented in the sprint review.
• How many times: Number of team members for standup; number of completed items for sprint review.

How Execution Grows With Input

Meeting time grows as more people or items are involved.

Input Size (n)	Approx. Meeting Time
5 team members / 5 items	~5-10 minutes standup, ~5 presentations sprint review
10 team members / 10 items	~10-20 minutes standup, ~10 presentations sprint review
20 team members / 20 items	~20-40 minutes standup, ~20 presentations sprint review

Pattern observation: Meeting time increases roughly in direct proportion to the number of people or items.

Final Time Complexity

Time Complexity: O(n)

This means the meeting duration grows linearly with the number of participants or items discussed.

Common Mistake

[X] Wrong: "Adding more team members won't affect meeting time much because everyone is brief."

[OK] Correct: Even short turns add up, so more people mean longer meetings overall.

Interview Connect

Understanding how meeting time scales helps you plan and communicate effectively in teams, a valuable skill in any software project.

Self-Check

"What if the daily standup was done in smaller groups instead of the whole team? How would that change the time complexity?"

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