Sprint planning and execution in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Sprint Planning Purpose

What is the primary goal of sprint planning in Agile software development?

A To review the completed work and gather feedback from stakeholders

B To define the sprint goal and select backlog items to work on during the sprint

C To deploy the finished product to the production environment

D To assign tasks to team members based on their seniority

💡 Hint

Think about what the team decides before starting the sprint work.

Sprint planning focuses on setting a clear sprint goal and choosing backlog items the team commits to completing during the sprint. It is a collaborative effort to prepare for the upcoming work.

📋 Factual

intermediate

Sprint Execution Roles

During sprint execution, who is primarily responsible for managing the progress and removing obstacles?

A Product Owner

B Project Sponsor

C Development Team Member

D Scrum Master

💡 Hint

This role supports the team by facilitating and clearing blockers.

The Scrum Master helps the team by managing progress, facilitating meetings, and removing obstacles that slow down the sprint work.

🔍 Analysis

advanced

Sprint Backlog Adaptation

During a sprint, the team realizes a backlog item is more complex than initially estimated. What is the best approach to handle this situation?

A Immediately add more tasks to the sprint backlog to cover the complexity

B Ignore the complexity and continue as planned to meet the sprint goal

C Discuss with the team and Product Owner to possibly split the item or adjust scope

D Remove the item from the sprint backlog without informing the Product Owner

💡 Hint

Consider collaboration and communication when facing unexpected challenges.

The team should communicate with the Product Owner to split the backlog item or adjust its scope to ensure the sprint goal remains achievable and transparent.

❓ Comparison

advanced

Sprint Review vs Sprint Retrospective

Which statement correctly distinguishes the sprint review from the sprint retrospective?

A Sprint review focuses on the product and feedback; sprint retrospective focuses on the team's process improvement

B Sprint review is held before sprint planning; sprint retrospective is held after sprint planning

C Sprint review is only for the development team; sprint retrospective includes stakeholders

D Sprint review is about assigning new tasks; sprint retrospective is about testing the product

💡 Hint

Think about what each meeting aims to improve or evaluate.

The sprint review is a meeting to inspect the product increment and gather feedback from stakeholders. The sprint retrospective is a meeting for the team to reflect on their process and find ways to improve.

❓ Reasoning

expert

Impact of Incomplete Sprint Work

If a sprint ends with some backlog items incomplete, what is the correct way to handle these items in the next sprint?

A Reassess and re-prioritize incomplete items with the Product Owner before including them in the next sprint planning

B Discard incomplete items and create new backlog items for the next sprint

C Automatically carry over all incomplete items to the next sprint without re-estimation

D Force the team to complete all incomplete items first before starting new work

💡 Hint

Consider the importance of prioritization and planning for unfinished work.

Incomplete items should be reviewed with the Product Owner to decide their priority and whether they should be included in the next sprint, possibly with updated estimates.

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