Agile retrospective ideas how to#

It is therefore the starting point for the next retrospective, since the report makes it possible to see whether the actions previously selected were really implemented during the next sprint. This document contains all the information that was discussed during the agile retrospective! With Beekast and automatic meeting reports, the reports are generated automatically via a Word document that you can export and send to the entire team. Qualitative feedback allows them to know what elements captured the team’s attention and whether the meeting objective was really achieved.Īgile method pros know all too well that reporting on the ideas of a retrospective can take ages (even more so if you use post-its that have to be included one by one). This activity, to be carried out at the very end of a retrospective, allows the facilitator to know what information was retained by the team. What will your team take with them after the meeting? To do so, the team selects and votes for the best ideas to be implemented. In this phase, the facilitator specifies the objective: to identify the highest priority actions to be implemented in the very short term. This is the time to prioritise areas for improvement and come up with an action plan as a team by using dotmocracy (dot-voting).

Agile retrospective ideas how to#

→ How to create a Board activity Phase 4: decide as a team

Use this phase to set aside ideas that are off-topic.īeekast makes it easy to gather similar ideas, by sorting information in a group after brainstorming. This involves identifying redundant data patterns, sorting and filtering all ideas produced. → Find out how to host a speedboat workshop with Beekast Phase 3: gather information

The anchors and rocks are the constraints and obstacles.

The wind represents the strengths that help move the projects forward.

The island symbolises the goals to be achieved.

The boat represents the project (yes, everyone’s in the same boat).

Using the boat metaphor, the speedboat agile retrospective helps to identify what moves the project forward and what slows it down.

direct activities according to the mood of the group.

know whether the group is ready to work on its improvement (sometimes it’s wise to postpone the retrospective in order to ensure effectiveness).

Start by setting a relaxed atmosphere and getting a feel for the team’s frame of mind. Let’s get started: find out how to engage in a continuous improvement effort and improve teamwork processes. It is also important to remind the team of the retrospective’s purpose so that you can achieve that goal by the end of the session.įinally, appoint a time keeper who will enforce the time limit, and someone to make a note of all the decisions made during the session. Break the ice to jump-start discussionsĪt the beginning of the retrospective, go ahead and remind the team of certain essential rules: Retrospectives always follow the same chronological steps:

Introduce the different agile retrospective steps Very practical for distributed teams (multi-site or teleworking). Whatever your role, (agile coach scrum master, product owner, manager or project manager), Beekast’s interactive and collaborative activities enable you to easily coordinate all the steps of a retrospective, up to the implementation of action plans and workshop report.įurthermore, thanks to our meeting tool, you can host your agile retrospectives both in person and remotely. Goal: to engage in a continuous improvement effort. It brings all the team members together and gives everyone a chance to express themselves freely in terms of success and problems encountered. Key takeaway Host an agile retrospective with BeekastĪs a reminder, an agile retrospective is a meeting held after every sprint or iteration. These examples of agile retrospectives will make it easy for you to set up a team process for continuous improvement, at the end of an iteration, project phase or completed project.ġ0.

However, it can also be used for all teams, even the most traditional. An agile retrospective is the most important routine for agile teams.