Sander’s retrospective A2
You will hear a story about a team meeting after a sprint. Listen carefully, then answer the questions.
Listen to the recording. You can play it as many times as you like.
Questions about the recording
Your result
Answer review
Transcript
Sander worked as a developer at an IT company. On Friday, his team finished a two-week sprint. In the afternoon, they had a retrospective. This was a meeting about how they worked together. They discussed good things and problems from the sprint. Everyone had a chance to speak and share ideas.
The meeting started with the question, “What went well?” Sander said that developers and testers worked closely together. They checked new features early and found problems quickly. A colleague said that their short daily calls also went well. Good communication helped everyone understand the plan. The team wanted to keep doing these things in the next sprint.
Then they discussed another question: “What could be improved?” Sander explained that some tasks did not have clear instructions. Sometimes, he did not know exactly what he needed to build. He had to ask questions and wait for answers. Other colleagues had the same problem. They agreed that they needed to improve the information in their tasks.
Sander wanted to suggest a simple change. He said, “Next time we should add a clear example to each new task.” Another colleague suggested a short checklist for writing tasks. The team liked this idea because it was easy to try. Their first action item was to create the checklist. Sander agreed to prepare it by Monday morning.
The checklist included a clear description, an example, and a contact person. Sander planned to share it in the team chat. Everyone agreed to use it during the next sprint. At the next retrospective, they would discuss whether it helped. One important lesson learned was that clear instructions could save time for everyone. Sander left the meeting with a useful task and a clear plan.