Even if Agile approaches favor collocated teams, distributed Scrum teams are more common that what you might think. Many Agile software development teams are based on a virtual organization.
Many Scrum teams are based on a distributed organization where members are in different locations, countries or time zones. How could these Agile teams perform their retrospectives? Some companies have developed online tools that can be used to facilitate retrospectives for distributed Scrum teams.
Meetings like the daily stand-up or retrospectives are moments that rhythm the journey of Scrum and Agile teams. Sometimes these meetings are almost religiously considered as rituals or ceremonies that bound participants together and that nobody could miss. Is this true? In his book Forming Agile Teams Workbook, Jesus Mendez discusses if the participation to Scrum meetings is mandatory.
As retrospectives are one of the main improvement tools for Agile teams, it is a challenge to keep them efficient and they can also be the subjects of improvement. In this article, Pablo Pecora shares five ideas of techniques that could help a ScrumMaster to improve the next Scrum retrospectives.
Some software development teams try to adopt Scrum, but they don’t achieve the full benefits of this approach. This might be due to the fact that the teams customize Scrum in a way that is inappropriate. In this article, Pablo Pecora suggests five aspects of Scrum, like the planning poker, that you cannot skip if you want to get the benefits of Agile.
Retrospectives are an important tool for Agile software development teams to support continuous improvement. One of the challenge is to maintain their efficiency when this activity is repeated again and again. To achieve better results, Scrum Masters will diversify the type of formats, but this might not solve the issue. In this article, Colleen Johnson proposes an approach that focuses instead on the type of data collected to improve the outcome of your retrospectives.
Retromat is a free online website that allows to generate random plans for Agile and Scrum retrospectives. Out of a pool of more than 100 activities, it selects one for each of the five phases (stage setting, data gathering, insight generating, decision, conclusion) to create a retrospective plan.