Reflection:
Reflection in Agile means the team regularly looks back at how the work went and decides how to improve.
In Scrum, the formal event for reflection is the Sprint Retrospective. Sprint Retrospective as one of the five Scrum events, along with Sprint, Sprint Planning, Daily Scrum, and Sprint Review.
Simple definition
| Term | Meaning |
| Reflection | Thinking back on recent work to learn what went well, what did not go well, and what should be improved. |
| Sprint Retrospective | A Scrum meeting held at the end of the sprint where the team reflects on process, teamwork, tools, communication, and improvement actions. |
| Adaptation | Changing the team’s approach based on what was learned from reflection. |
Why do we need reflection?
Reflection helps the team improve continuously. It supports one of the Agile principles: teams should regularly reflect and adapt. Your slides mention “regular reflection and team adaptation” as part of the Agile principles.
It helps the team answer:
What worked well?
What problems slowed us down?
What should we change in the next sprint?
What the action looks like
At the end of a sprint, the team may hold a retrospective and discuss:
| Question | Example student/team answer |
| What went well? | We completed most of the high-priority user stories. |
| What did not go well? | Some stories were unclear, so estimation was difficult. |
| What should we improve? | Add better acceptance criteria before sprint planning. |
| What action will we take next sprint? | Product Owner will clarify stories before estimation. |
