Conducting Sprint Retrospective Meetings – DZone Agile

What Is a Dash Retrospective?

It can be a assembly held at the end of each dash to go about the sprint and talk about what could be performed better for the subsequent dash and what went effectively in the previous sprint. The retrospective is an significant portion of the Scrum methodology as it will help in determining gaps for class correction and to figure out issues that are operating well and need to be finished extra.  

What Do You want?


In case your staff is conference remotely, you will have to have:

Video Conferencing Instrument

You will need a video conferencing device this kind of as Google Hangout, Zoom, WebEx, and so forth., for the crew to collaborate. It is a good strategy to have the films on so that your workforce can see every other in actual-time.

Collaboration Tool 

You will have to have a digital instrument for the workforce to work with each other through this session. For illustration, numerous teams use a Confluence webpage, Retrium, on line docs, or some other instrument through which groups can collaborate in genuine-time.

In-particular person

Assembly Place

A assembly put for the staff associates to meet and collaborate.

Whiteboard and Markers

For the workforce customers to generate their views and inputs.


To continue to keep monitor of the time. You can use your cellphone for it.


For conducting a effective session, you can create a Retrium session, a Google or Phrase doc, or aboard. In the situation of a remote group, it will make sense to use on line collaboration applications such as Confluence, Trello, Retrium, etcetera. For the in-man or woman session, you can use a whiteboard and have the sticky notes or markers handy for the group users to use. On the doc or the board, build three sections:

  • What went properly – This section will address issues that labored properly, and the crew would like to proceed accomplishing.
  • What failed to go nicely – This segment will deal with items that staff felt did not operate effectively. These are the points that require to be improved or course-corrected.
  • Action products – This part should really be utilised for actions that need to be taken in the next sprints.

You can have neutral facilitators in the meeting to make certain there is no bias.  

Placing the Context

It really is really crucial to set the context for a effective and honest discussion. Structure the ground regulations for the session as the major reason for this assembly is to discover out the improvement chances and have an open dialogue.

  • Have an open up brain
  • This dialogue is not for finger-pointing but for finding enhancement alternatives.
  • Everyone’s viewpoint counts. They could have diverse ordeals than you. So hear with out judging.
  • The assembly must have a distinct time period of time in brain – whether or not the last dash, final quarter, and so forth.

What Went Very well

Each individual crew member writes their perspective on what went perfectly. You can group equivalent strategies or themes collectively. This will assist in being familiar with from a broader point of view what was going effectively.      

What can be performed far better

Team users publish down their ideas on what can be enhanced. Then, you can team related thoughts and themes. This will assistance you determine enhancement chances on a broader amount.


Right after wanting at what went effectively and what can be completed greater, the team brainstorms on steps that can be taken to increase the process in the foreseeable future. As right before, you can group strategies grouped collectively and try to determine themes. Most of the motion items may well stem from your what went effectively and what can be performed greater sections.

Follow By way of

The moment the retrospective assembly is finished, comply with by on the action goods and assure that you are tracking the development. Agile is all about steady advancement and active participation.

Content Protection by
Please Share