a look back at events that already have taken place. As a noun, retrospective has speci fi c meanings in medicine, software development, popular culture and the arts. […]
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.” “Project Retrospectives” - Norman Kerth Photo by Nathan Dumlao on Unsplash
retrospective. This is a rule to help creating a safety environment. Keep in mind to share the learnings/outcome of the retrospective. Photo by Grant Cai on Unsplash
sit in a boat … What speeds you up? What slows you down? 1st everyone write its own cards, than present the notes to the team. Try to fi nd overlapping topics. Choose the most important ones.
team is able to focus on the retrospective itself. Maybe you want to develop your soft skills and put a training in your PDR? Photo by Adrià Crehuet Cano on Unsplash
up to the moderator to handle escalated situations or heated debates. Such problems need to be solved fi rst. Most often it helps to re fl ect the situation back to the team, e.g. describing (not arguing) from the moderators point of view. The team should commit on the solution to solve the special situation. This comprehensive topic is worth of discussing separately.
remote ones use at least a video/webcam to look into others eyes • As a replacement for moderator cards use e.g. Google Docs/Presentation or draw.io • When using Zoom, it helps when everyone is able to do drawings and others can see that • Everyone should see changes in realtime and being able follow the discussion