Sprint planning and execution in Software Engineering - Step-by-Step Execution

Concept Flow - Sprint planning and execution

Start Sprint Planning

↓

Define Sprint Goal

↓

Select Backlog Items

↓

Estimate Tasks & Assign

↓

Sprint Execution Begins

↓

Daily Standups & Progress

↓

Sprint Review & Demo

↓

Sprint Retrospective

↓

Sprint Ends

Sprint planning starts with setting a goal, selecting tasks, then moves to execution with daily checks, ending with review and reflection.

Execution Sample

Software Engineering

1. Define sprint goal
2. Pick backlog items
3. Estimate and assign tasks
4. Work on tasks daily
5. Review and demo
6. Retrospect and improve

This sequence shows the main steps from planning to finishing a sprint.

Analysis Table

Step	Action	Details	Outcome
1	Define sprint goal	Team agrees on what to achieve	Clear focus for sprint
2	Select backlog items	Choose tasks from product backlog	Sprint backlog created
3	Estimate & assign	Tasks estimated and assigned to team	Workload balanced
4	Sprint execution	Team works on tasks daily	Progress towards goal
5	Daily standups	Short meetings to share updates	Issues identified early
6	Sprint review	Demo completed work to stakeholders	Feedback collected
7	Sprint retrospective	Discuss what went well and improvements	Plan for next sprint
8	Sprint ends	Sprint cycle completes	Ready for next sprint planning

💡 Sprint ends after review and retrospective, ready to start next sprint cycle

State Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 7	Final
Sprint Goal	None	Defined	Defined	Defined	Defined	Defined
Sprint Backlog	Empty	Selected items	Estimated & assigned	In progress	Completed/Reviewed	Ready for next sprint
Team Tasks Status	None	None	Assigned	Working	Completed	Reviewed
Feedback	None	None	None	None	Collected	Used for improvement

Key Insights - 3 Insights

Why do we estimate and assign tasks before starting the sprint?

Estimating and assigning tasks (see execution_table step 3) helps balance workload and sets clear responsibilities, so the team knows what to do during execution.

What is the purpose of daily standups during sprint execution?

Daily standups (step 5) allow the team to share progress and spot problems early, keeping the sprint on track.

Why is the sprint retrospective important after the sprint ends?

The retrospective (step 7) helps the team reflect on what worked and what didn’t, so they can improve future sprints.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the sprint backlog created?

A Step 2

B Step 1

C Step 4

D Step 6

💡 Hint

Check the 'Details' column in execution_table row for Step 2.

According to variable_tracker, what is the status of 'Team Tasks Status' after Step 4?

A Completed

B Assigned

C Working

D None

💡 Hint

Look at the 'Team Tasks Status' row under 'After Step 4' column.

If the team skips the sprint retrospective, which outcome from the execution_table is missed?

A Sprint backlog created

B Plan for next sprint

C Issues identified early

D Sprint goal defined

💡 Hint

Refer to execution_table step 7 'Outcome' column.

Concept Snapshot

Sprint planning starts by defining a clear goal and selecting backlog items.
Tasks are estimated and assigned before sprint execution.
Daily standups track progress and surface issues.
Sprint ends with a review demo and a retrospective to improve.
This cycle repeats for continuous delivery and improvement.

Full Transcript

Sprint planning and execution is a process where a team first defines a sprint goal, selects tasks from the backlog, estimates and assigns them. Then the team works on these tasks during the sprint, holding daily standups to share progress and solve problems. At the end, the team reviews the completed work with stakeholders and holds a retrospective meeting to discuss improvements. This cycle helps teams deliver work in small, manageable chunks and continuously improve their process.

Practice

1. What is the main purpose of sprint planning in software development?

easy

A. To assign permanent roles to team members

B. To review completed work after the sprint ends

C. To set clear goals and tasks for a short work period

D. To write detailed documentation for the project

Solution

1. Step 1: Understand sprint planning goals

   Sprint planning is about deciding what the team will work on during the sprint.

2. Step 2: Identify the correct purpose

   The main goal is to set clear, achievable tasks and goals for the sprint period.

3. Final Answer:

   To set clear goals and tasks for a short work period -> Option C

4. Quick Check:

   Sprint planning = Set goals and tasks [OK]

Hint: Sprint planning = setting goals before work starts [OK]

Common Mistakes:

• Confusing sprint planning with sprint review
• Thinking sprint planning assigns permanent roles
• Believing sprint planning is for documentation

2. Which of the following is a correct activity during sprint execution?

easy

A. Planning the sprint backlog

B. Team members working together to complete tasks

C. Conducting the sprint retrospective

D. Writing the project proposal

Solution

1. Step 1: Identify sprint execution activities

   Sprint execution is when the team actively works on the planned tasks.

2. Step 2: Match the correct activity

   Team collaboration to complete tasks fits sprint execution, while planning and retrospectives happen before or after.

3. Final Answer:

   Team members working together to complete tasks -> Option B

4. Quick Check:

   Sprint execution = Doing the work [OK]

Hint: Execution means doing planned tasks together [OK]

Common Mistakes:

• Mixing execution with planning or review phases
• Thinking retrospectives happen during execution
• Confusing proposal writing with sprint tasks

3. During a sprint, the team holds daily stand-up meetings. What is the main purpose of these meetings?

medium

A. To share progress and identify blockers

B. To assign new tasks to team members

C. To review the entire project plan

D. To finalize the sprint backlog

Solution

1. Step 1: Understand daily stand-up purpose

   Daily stand-ups are short meetings to update the team on progress and problems.

2. Step 2: Identify the correct purpose

   The main goal is to share progress and quickly spot any blockers that slow work.

3. Final Answer:

   To share progress and identify blockers -> Option A

4. Quick Check:

   Daily stand-up = Progress updates + blockers [OK]

Hint: Daily stand-ups = quick progress check-ins [OK]

Common Mistakes:

• Thinking daily stand-ups assign new tasks
• Confusing stand-ups with sprint planning or review
• Believing stand-ups finalize backlogs

4. A team forgot to update the sprint backlog during the sprint. What is the likely problem caused by this?

medium

A. The team will have unclear progress and priorities

B. The sprint planning will be more effective

C. The sprint retrospective will be skipped

D. The team will finish tasks faster

Solution

1. Step 1: Understand the role of sprint backlog updates

   Updating the sprint backlog keeps track of progress and task priorities.

2. Step 2: Identify the impact of not updating

   Without updates, the team loses clarity on what is done and what remains important.

3. Final Answer:

   The team will have unclear progress and priorities -> Option A

4. Quick Check:

   Unupdated backlog = unclear progress [OK]

Hint: Keep backlog updated to track progress clearly [OK]

Common Mistakes:

• Assuming backlog updates speed up task completion
• Confusing backlog updates with sprint retrospective
• Believing planning improves without backlog updates

5. A team wants to improve their sprint execution by reducing blockers. Which approach best supports this goal?

hard

A. Assign all tasks to a single team member

B. Skip sprint retrospectives to save time

C. Avoid updating the sprint backlog during the sprint

D. Hold daily stand-ups to discuss progress and blockers

Solution

1. Step 1: Identify ways to reduce blockers

   Blockers slow down work, so the team needs quick ways to spot and fix them.

2. Step 2: Choose the best approach

   Daily stand-ups help the team share progress and highlight blockers early for fast resolution.

3. Final Answer:

   Hold daily stand-ups to discuss progress and blockers -> Option D

4. Quick Check:

   Daily stand-ups reduce blockers effectively [OK]

Hint: Daily stand-ups catch blockers early [OK]

Common Mistakes:

• Skipping retrospectives reduces learning opportunities
• Not updating backlog hides progress issues
• Assigning all tasks to one person overloads them