Retrospectives are a crucial part of agile software development. They provide the basis for self-improvement in Scrum teams. This article explores the benefits and challenges of distributed retrospectives and provide tips for conducting effective remote team reflection.
This video is an interactive exploration of retrospectives top tips, strategies and agile hacks for enabling continuous improvement of Scrum teams.
Even if Agile approaches favor collocated teams, distributed Scrum teams with remote work are more common that what you might think. Many Agile software development teams are based on a virtual organization.
This article presents the retrospective & health radar tool, Trune. There are many Scrum retrospective tools out there, and the number is growing by the day. So why do companies like Intuit, IBM, Airbnb, Volvo, and Starbucks choose Trune as their retrospective tool for their Agile teams?
Continuous improvement is one of the main concept of Agile and retrospectives is a technique used by Scrum team to achieve it. This article shares five situations that Scrum teams should avoid in their retrospectives.
We are going to walk you through how to facilitate a retrospective using RetroTeam. Some of the features are as follows — Creating a Board and Card, Inviting Participants, Settings to turn on Timer, and Export your Retrospectives to PDF. RetroTeam lets you seamlessly run Scrum retrospectives with small to large Agile teams.
The retrospective is arguably the event that will yield the most benefits for your agile team. This is because it is the place where you identify crucial, valuable improvements for your team that will drive ongoing performance improvements. Such improvements allow your team to deliver higher value products in a shorter timescale.
Scrum Expert Copyright © 2009-2023 Martinig & Associates