Patrik Opat ERNI retrospective agile

Patrik Opát
Agile Coach and Service Unit Leader


What is a retrospective?

According to the Scrum guide the Sprint retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. The Scrum Master ensures that the event takes place and that attendants understand its purpose.

The Scrum guide does not define the exact duration of the event. It may vary based on the Sprint duration and needs of the team.


What are the success factors influencing its smooth running?

There are for sure multiple factors that could and should be taken into consideration. From my point of view a couple of main success factors are:

  • All participants need to understand the purpose of the session, that it is not only “another meeting” just because we decided to follow the Scrum framework, but we are doing it to improve the team culture, delivery, and added value
  • Understanding that every person is individual and by putting these individuals together is creating a unique mixture, once you understand your team chemistry you will be able to reach out to them much better
  • Create a safe place, where everybody will be encouraged to speak openly
  • Make it as fun and interactive as possible, during the regular Sprint there is enough focus and hard work which needs to be fulfilled by the team members and the retrospective should be more relaxing
  • Provide a clear outcome of the retrospective, what did you agree on, what are the action points, what needs follow-up, etc. This will show the team that time on the retrospective was well spent.


Which pitfalls do we encounter usually during retrospectives?

We need to understand that team is a group of people put together to achieve some common goal. These team members are usually assigned to the team based on their skills and therefore it may happen that you will end up with a team with very “interesting” chemistry.

  • The first pitfall which comes to my mind is a “silent retrospective”, where you keep asking questions, but you get no or very limited feedback. This usually happens with a new team where the team members do not know each other well enough and the team did not complete their “team journey” to becoming a team. For further information, I would recommend looking up the 5 stages of team development.
  • The second scenario, as we said earlier, during the retrospective you want to create a safe environment where everybody can speak openly, however you also need to make sure that this openness does not end up in blaming and fingerpointing, therefore it is recommended to set up basic rules and try to follow them
  • The last pitfall which I would like to mention, especially during the home office or remote work times is visual contact, try to make sure that if you are doing a retrospective virtually, every team member has the camera enabled, because the facial expression can say much more than words sometimes


What best practices from your experience you have and why?

What I would recommend from my own experience is to keep the retrospective fun and interactive. Which practices to choose also depends on the actual state and issue we are experiencing. There are multiple sources online where to get inspiration. (e.g.

My personal favourites are:

  • Three little pig, where you try to describe your team based on a story of three little pigs and their houses (straw, timber, bricks)
  • Promised land, where you need to define your wished goal / outcome and afterwards try to define what hinders you and could you possibly overcome these obstacles


Would you like to discuss solutions for your business with us?

Contact us.

News from ERNI

In our newsroom, you find all our articles, blogs and series entries in one place.

  • 22.11.2023.

    Recognising trends: An insight into regression analysis

    Data plays a very important role in every area of a company. When it comes to data, a distinction is made primarily between operational data and dispositive data. Operational data play an important role, especially in day-to-day business. However, they are not nearly as relevant as dispositive data. This is because these data are collected over a longer period of time and provide an initial insight into the history or the past.

  • 08.11.2023.

    Why do we need digital transformation for medical devices?

    For hospitals, it is not up for discussion as to whether they want to digitalise. The increasing age of the population in western countries and the progressive shortage of medical professionals mean that without digitalisation, the healthcare system will not be able to provide the quality that patients want in the future.

  • 25.10.2023.

    Mastering the challenges of mobile app testing: Strategies for efficient quality assurance

    Discover the unique challenges faced in testing mobile applications and learn how to overcome them effectively. From selecting suitable devices and operating systems to leveraging cloud-based test platforms, test automation and emulators, this article provides seven essential strategies for optimising your mobile app testing process.

  • 11.10.2023.

    Incorporating classical requirements engineering methods in agile software development for a laboratory automation system

    Traditional agile methodologies can sometimes struggle to accommodate the complexity and regulatory requirements of laboratory automation systems, leading to misalignment with stakeholder needs, scope creep, and potential delays. The lack of comprehensive requirements documentation can result in ambiguous expectations and hinder effective communication among cross-functional teams.

  • 27.09.2023.

    Unveiling the power of data: Part III – Navigating challenges and harnessing insights in data-driven projects

    Transforming an idea into a successful machine learning (ML)-based product involves navigating various challenges. In this final part of our series, we delve into two crucial aspects: ensuring 24/7 operation of the product and prioritising user experience (UX).

  • 13.09.2023.

    Exploring Language Models: An overview of LLMs and their practical implementation

    Generative AI models have recently amazed with unprecedented outputs, such as hyper-realistic images, diverse music, coherent texts, and synthetic videos, sparking excitement. Despite this progress, addressing ethical and societal concerns is crucial for responsible and beneficial utilization, guarding against issues like misinformation and manipulation in this AI-powered creative era.

  • 01.09.2023.

    Peter Zuber becomes the new Managing Director of ERNI Switzerland

    ERNI is setting an agenda for growth and innovation with the appointment of Peter Zuber as Managing Director of the Swiss business unit. With his previous experience and expertise, he will further expand the positioning of ERNI Switzerland, as a leading consulting firm for software development and digital innovation.

  • data230.08.2023.

    Unveiling the power of data: Part II – Navigating challenges and harnessing insights in data-driven projects

    The second article from the series on data-driven projects, explores common challenges that arise during their execution. To illustrate these concepts, we will focus on one of ERNI’s latest project called GeoML. This second article focuses on the second part of the GeoML project: Idea2Proof.