Daily standup and sprint review in Software Engineering - Mini Project: Build & Apply

Daily Standup and Sprint Review Meeting Notes

📖 Scenario: You are part of a software development team using Agile methodology. Your team holds daily standup meetings and sprint review meetings to track progress and plan work.In this project, you will create a simple structured record of daily standup notes and sprint review summaries to help your team stay organized.

🎯 Goal: Build a structured set of notes for daily standups and sprint reviews using dictionaries and lists. This will help your team quickly see what was done, what is planned, and any blockers.

📋 What You'll Learn

Create a dictionary to hold daily standup notes for 3 team members with their updates

Add a variable to track the current sprint number

Create a list of sprint review summaries with key points

Add a final summary string describing the sprint status

💡 Why This Matters

🌍 Real World

Teams use daily standups and sprint reviews to communicate progress and challenges clearly and quickly.

💼 Career

Understanding how to organize and record Agile meeting notes is essential for roles like Scrum Master, Product Owner, and developers in Agile teams.

1

Create daily standup notes dictionary

Create a dictionary called daily_standup with these exact entries: 'Alice': 'Completed login feature', 'Bob': 'Working on API integration', 'Charlie': 'Fixing bugs in UI'.

Software Engineering

# Create the daily_standup dictionary with exact entries
# Your code here

Hint

Use curly braces {} to create a dictionary with keys as names and values as their updates.

2

Add current sprint number variable

Add a variable called current_sprint and set it to the integer 5.

Software Engineering

daily_standup = {
    'Alice': 'Completed login feature',
    'Bob': 'Working on API integration',
    'Charlie': 'Fixing bugs in UI'
}
# Add current_sprint variable below
# Your code here

Hint

Just assign the number 5 to the variable current_sprint.

3

Create sprint review summaries list

Create a list called sprint_reviews with these exact strings: 'Demoed new login feature', 'API integration 80% complete', 'UI bugs reduced by 50%'.

Software Engineering

daily_standup = {
    'Alice': 'Completed login feature',
    'Bob': 'Working on API integration',
    'Charlie': 'Fixing bugs in UI'
}

current_sprint = 5
# Create sprint_reviews list below
# Your code here

Hint

Use square brackets [] to create a list of strings.

4

Add final sprint summary string

Add a variable called sprint_summary and set it to the string 'Sprint 5 completed successfully with key features delivered.'.

Software Engineering

daily_standup = {
    'Alice': 'Completed login feature',
    'Bob': 'Working on API integration',
    'Charlie': 'Fixing bugs in UI'
}

current_sprint = 5

sprint_reviews = [
    'Demoed new login feature',
    'API integration 80% complete',
    'UI bugs reduced by 50%'
]
# Add sprint_summary string below
# Your code here

Hint

Assign the exact string to the variable sprint_summary.

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