Reflective Practice

Where and when did it go wrong? What did I learn?
What should I do differently next time?
Do you ever ask yourself these questions after completing a project or a task?

We see many agile transformations fail and poor implementations of Scrum, that at times we can feel disappointed.
The concept of agile is neither new nor complex. However, it is very difficult to implement in a lasting manner.

The key success in applying agile is simply reflective practice. Sometimes we get focused too heavily on the principles and the values that we forget to reflect.

As a group and individual, we should take time to identify learning opportunities. We should continually observe ourselves and our teams to look for ways to improve.

I believe every team regardless of the nature of their task, should pause and reflect regularly. Regardless of what you do, the reflection will definitely help you to improve.

As described in the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
The Scrum team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible.

During each agile sprint retrospective, the development team focuses on increasing product quality by improving work processes. It allows the team to identify potential impediments at an early stage and resolve conflict areas.

Effective retrospectives can be vital to your team’s ability to execute. Most importantly, we should create a safe space for people to share their opinions without any blame to ensure that everyone is comfortable and contributes to the team.

I would say that retrospective is the most important agile ceremony as it is undoubtedly uncovering better ways.


Ahmed Hikal
Scrum Master
Somatic Thinking Coach