Computer Science
Grade 9
20 min
Sprint Retrospectives
Sprint Retrospectives
Tutorial Preview
1
Introduction & Learning Objectives
Learning Objectives
Define what a Sprint Retrospective is and explain its purpose in a project.
Identify the three core questions asked during a retrospective: What went well? What could be improved? What will we commit to doing differently?
Differentiate between blaming individuals and improving team processes.
Participate constructively in a simulated retrospective for a class project.
Formulate a clear, actionable improvement item based on feedback.
Explain the importance of following up on action items in the next sprint.
Ever finish a group project and think, 'That was okay, but we could have done so much better'? 🤔 A Sprint Retrospective is a team's special meeting to figure out exactly how to do that next time!
In this lesson, you'll learn about...
2
Key Concepts & Vocabulary
TermDefinitionExample
SprintA short, time-boxed period (usually 1-4 weeks) during which a software development team works to complete a set amount of work.Our team's 'Sprint 1' is two weeks long, and our goal is to build the user login page for our app.
Sprint RetrospectiveA meeting held at the end of a Sprint for the team to reflect on its process and identify ways to improve for the next Sprint.After finishing the login page, our team held a retrospective to discuss our communication and planning.
What Went WellA category of feedback in a retrospective focusing on the positive things, successes, and strengths the team demonstrated during the Sprint.Feedback: 'We did a great job of helping each other debug our code this sprint.'
What Could Be ImprovedA category o...
3
Core Syntax & Patterns
The Prime Directive
Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
This is the most important rule. It creates a safe environment where the team can be honest without fear of blame. The goal is to improve the future, not punish the past.
Focus on Process, Not People
Critique the team's way of working, not the individuals on the team.
Instead of saying 'You wrote buggy code,' say 'Our code review process didn't catch enough bugs.' This helps find the root cause of a problem in the system the team uses, which is easier to fix than trying to change a person.
Create Actionab...
4 more steps in this tutorial
Sign up free to access the complete tutorial with worked examples and practice.
Sign Up Free to ContinueSample Practice Questions
Challenging
A team successfully completes all their planned work ahead of schedule in a Sprint. Why is it still crucial for them to hold a Sprint Retrospective?
A.It is not crucial; they can skip it since everything went well.
B.To figure out what went so well so they can repeat that success in the future.
C.To give the project manager a chance to reward the team.
D.Because the rules say they must hold the meeting no matter what.
Challenging
A team's action item is: 'We will try to have better communication.' Why is this a weak action item, and how does it violate the principles taught in the tutorial?
A.It is too negative and will hurt team morale.
B.It is not a SMART item; it's not specific or measurable, so the team won't know if they've achieved it.
C.It blames the entire team instead of a specific person.
D.It focuses on people ('communication') instead of the technical process.
Challenging
A team's retrospective focuses only on technical bugs and coding standards. What critical aspect of the project are they most likely neglecting by having such a narrow focus?
A.The project budget and deadlines.
B.The team's collaborative processes, communication, and overall well-being.
C.The features that the users want the most.
D.The individual performance reviews of each programmer.
Want to practice and check your answers?
Sign up to access all questions with instant feedback, explanations, and progress tracking.
Start Practicing Free