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.
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.
Parabol is an agile meeting tool that helps remote teams run guided retrospective, check-in and Sprint Poker meetings. Parabol’s structured format and built-in templates make it easy for facilitators to run a great agile meeting – no matter if you’re a pro or just starting out. It’s free to use for up to two teams.
In this article we’d like to share our views on the distinct advantages an online retrospective offers over traditional retrospectives for distributed Agile teams, and what to look for in a remote retrospective tool.
Anti-Patterns are like patterns, only more informative. With anti-patterns you will first see what patterns reoccur in “bad”Agile retrospectives and then you will see how to avoid, or remedy, the situation.