Scrum framework overview in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Scrum Roles Identification

Which of the following is NOT a defined role in the Scrum framework?

A Development Team

B Project Manager

C Product Owner

D Scrum Master

💡 Hint

Scrum defines three specific roles that work together closely.

Scrum defines three roles: Product Owner, Scrum Master, and Development Team. The role of Project Manager is not part of Scrum.

📋 Factual

intermediate

Scrum Artifacts Purpose

What is the main purpose of the Product Backlog in Scrum?

A To prioritize and manage all desired work for the product

B To list all tasks assigned to the Scrum Master

C To track daily progress of the Development Team

D To document the final product specifications

💡 Hint

Think about where all the work items for the product are collected and prioritized.

The Product Backlog is an ordered list of everything that might be needed in the product. It is the single source of work for the Scrum Team.

🔍 Analysis

advanced

Sprint Planning Outcome

After a Sprint Planning meeting, what is the expected outcome?

A A list of bugs found during the last Sprint

B A detailed project plan for the entire product development

C A Sprint Backlog with selected Product Backlog items and a plan for delivering them

D A report on team member performance

💡 Hint

Consider what the team commits to completing during the Sprint.

Sprint Planning results in a Sprint Backlog, which includes the Product Backlog items selected for the Sprint and a plan for delivering them.

❓ Reasoning

advanced

Daily Scrum Purpose

Why is the Daily Scrum important for the Development Team?

A It allows the Scrum Master to assign new tasks to team members

B It serves as a formal status report to management

C It is used to review the Product Backlog and reprioritize items

D It helps the team synchronize activities and create a plan for the next 24 hours

💡 Hint

Think about how the team coordinates their work daily.

The Daily Scrum is a short meeting where the Development Team synchronizes activities and plans work for the next day.

❓ Comparison

expert

Difference Between Sprint Review and Sprint Retrospective

Which statement correctly distinguishes the Sprint Review from the Sprint Retrospective?

A Sprint Review focuses on the product increment; Sprint Retrospective focuses on the process and team improvement

B Sprint Review is held daily; Sprint Retrospective is held at the end of the project

C Sprint Review is led by the Scrum Master; Sprint Retrospective is led by the Product Owner

D Sprint Review is optional; Sprint Retrospective is mandatory

💡 Hint

Consider what each event aims to inspect and adapt.

The Sprint Review inspects the product increment and adapts the Product Backlog. The Sprint Retrospective inspects the process and team dynamics to improve future Sprints.

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