Scrum framework overview in Software Engineering - Step-by-Step Execution

Concept Flow - Scrum framework overview

Product Backlog

↓

Sprint Planning

↓

Sprint Backlog

↓

Sprint Execution

↓

Daily Scrum

↓

Sprint Review

→Product Increment

↓

Sprint Retrospective

↓

Product Backlog

This flow shows how Scrum starts with a list of work, plans a sprint, executes it with daily check-ins, reviews the result, and reflects to improve next time.

Execution Sample

Software Engineering

1. Create Product Backlog
2. Sprint Planning selects tasks
3. Team works in Sprint
4. Daily Scrum updates progress
5. Sprint Review shows results
6. Sprint Retrospective improves process

This sequence outlines the main Scrum events and artifacts in one sprint cycle.

Analysis Table

Step	Event/Artifact	Action	Result
1	Product Backlog	List all desired features and fixes	Prioritized list of work items
2	Sprint Planning	Select items for next sprint	Sprint Backlog created with tasks
3	Sprint Execution	Team develops selected tasks	Working product increment in progress
4	Daily Scrum	Team meets daily for 15 minutes	Progress shared and obstacles identified
5	Sprint Review	Show completed work to stakeholders	Feedback collected and product increment accepted
6	Sprint Retrospective	Team reflects on process	Improvements planned for next sprint
7	Loop back	Update Product Backlog with new info	Cycle repeats with better planning

💡 Sprint cycle ends after Retrospective; process repeats for continuous improvement

State Tracker

Artifact/Event	Initial State	After Step 2	After Step 3	After Step 5	After Step 6	Final State
Product Backlog	List of all ideas	Prioritized and refined	Updated with progress	Updated with feedback	Updated with improvements	Ready for next sprint
Sprint Backlog	Empty	Tasks selected	Tasks in progress	Tasks completed	Reviewed	Closed or moved
Product Increment	None	None	Partially done	Completed and reviewed	Accepted	Delivered

Key Insights - 3 Insights

Why does the Sprint Backlog change during the sprint?

The Sprint Backlog starts with selected tasks but can be updated as the team learns more or adjusts work during Sprint Execution and Daily Scrums (see execution_table steps 3 and 4).

What is the difference between Sprint Review and Sprint Retrospective?

Sprint Review focuses on the product and feedback from stakeholders (step 5), while Retrospective focuses on the team's process and improvements (step 6).

Why do we loop back to the Product Backlog after a sprint?

Because new ideas, feedback, and improvements arise, the Product Backlog is updated to reflect current priorities for the next sprint (step 7).

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the Sprint Backlog created?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Check the 'Action' column for when tasks are selected for the sprint.

According to variable_tracker, what is the state of the Product Increment after Step 3?

A Partially done

B Completed and reviewed

C None

D Accepted

💡 Hint

Look at the 'Product Increment' row under 'After Step 3' column.

If the team skips the Sprint Retrospective, what part of the cycle is missed according to the concept_flow?

A Sprint Planning

B Sprint Review

C Continuous improvement loop

D Daily Scrum

💡 Hint

See the loop back arrow after Sprint Retrospective in the concept_flow diagram.

Concept Snapshot

Scrum is a cycle of events and artifacts:
- Product Backlog: list of work
- Sprint Planning: select tasks
- Sprint: work + Daily Scrum
- Sprint Review: show results
- Sprint Retrospective: improve process
Repeat for continuous delivery and improvement.

Full Transcript

Scrum framework is a way teams work in short cycles called sprints. It starts with a Product Backlog, which is a list of all desired work. During Sprint Planning, the team picks tasks to do in the sprint, creating the Sprint Backlog. The team works on these tasks during the Sprint, meeting daily in the Daily Scrum to share progress and solve problems. At the Sprint Review, the team shows what they built to stakeholders and gets feedback. Then, in the Sprint Retrospective, the team talks about how to improve their work process. After that, the cycle repeats with updated priorities and improvements.

Practice

1. What is the main purpose of the Scrum framework?

easy

A. To avoid changes during the project development

B. To create detailed project plans before starting work

C. To assign tasks to individuals without collaboration

D. To help teams build products in small, manageable steps

Solution

1. Step 1: Understand Scrum's goal

   Scrum is designed to help teams work in small steps to build products effectively.

2. Step 2: Compare options

   Options B, C, and D contradict Scrum principles like flexibility and teamwork.

3. Final Answer:

   To help teams build products in small, manageable steps -> Option D

4. Quick Check:

   Scrum purpose = small steps product building [OK]

Hint: Scrum breaks work into small steps for teamwork [OK]

Common Mistakes:

• Thinking Scrum avoids changes
• Believing Scrum is about strict plans
• Assuming Scrum assigns tasks without collaboration

2. Which of the following is a key role in Scrum?

easy

A. Project Manager

B. Scrum Master

C. Team Leader

D. Product Owner Assistant

Solution

1. Step 1: Identify Scrum roles

   Scrum has three main roles: Scrum Master, Product Owner, and Development Team.

2. Step 2: Match options to Scrum roles

   Only Scrum Master is an official Scrum role; others are not standard Scrum roles.

3. Final Answer:

   Scrum Master -> Option B

4. Quick Check:

   Key Scrum role = Scrum Master [OK]

Hint: Remember Scrum Master leads Scrum process, not Project Manager [OK]

Common Mistakes:

• Confusing Project Manager with Scrum Master
• Assuming Team Leader is a Scrum role
• Thinking Product Owner Assistant is official

3. During a Sprint, which meeting is held daily to discuss progress and obstacles?

easy

A. Daily Scrum

B. Sprint Planning

C. Sprint Review

D. Retrospective

Solution

1. Step 1: Recall Scrum meetings

   Scrum includes Sprint Planning, Daily Scrum, Sprint Review, and Retrospective meetings.

2. Step 2: Identify daily meeting

   The Daily Scrum is a short daily meeting to discuss progress and obstacles.

3. Final Answer:

   Daily Scrum -> Option A

4. Quick Check:

   Daily meeting in Scrum = Daily Scrum [OK]

Hint: Daily Scrum happens every day to track progress [OK]

Common Mistakes:

• Confusing Sprint Review with daily meeting
• Thinking Sprint Planning is daily
• Mixing Retrospective with Daily Scrum

4. Identify the error in this Scrum practice: The team skips the Sprint Retrospective meeting.

medium

A. Skipping Retrospective is recommended for experienced teams

B. Skipping Retrospective speeds up product delivery

C. Skipping Retrospective reduces team improvement opportunities

D. Skipping Retrospective increases Sprint Planning time

Solution

1. Step 1: Understand Retrospective purpose

   The Sprint Retrospective helps the team reflect and improve their process.

2. Step 2: Analyze skipping impact

   Skipping it means losing chances to improve teamwork and processes.

3. Final Answer:

   Skipping Retrospective reduces team improvement opportunities -> Option C

4. Quick Check:

   Skipping Retrospective = less improvement [OK]

Hint: Retrospective is for team improvement; skipping hurts progress [OK]

Common Mistakes:

• Believing skipping improves speed
• Thinking experienced teams can skip it
• Confusing Retrospective with Planning

5. A Scrum team wants to improve flexibility by adjusting work during a Sprint. Which Scrum principle supports this?

hard

A. Responding to change over following a plan

B. Fixed scope during Sprint

C. Continuous improvement through Retrospectives

D. Strict adherence to initial requirements

Solution

1. Step 1: Identify Scrum values

   Scrum values include flexibility and responding to change rather than rigid plans.

2. Step 2: Match principle to flexibility

   Responding to change over following a plan directly supports adjusting work during a Sprint.

3. Final Answer:

   Responding to change over following a plan -> Option A

4. Quick Check:

   Scrum flexibility = respond to change [OK]

Hint: Scrum values adapting to change, not fixed plans [OK]

Common Mistakes:

• Choosing fixed scope as flexible
• Confusing Retrospective with flexibility during Sprint
• Believing strict requirements allow flexibility