In this episode, I will tell you about retrospection in the context of work in the Scrum model.
Retrospection is a very important event when you work in Scrum, but many times people do not understand why retrospection should be performed by Scrum teams and what it can give to them.
Thanks to retrospection, teams can work better and better. They can make progress, polish the way of their cooperation. But to achieve this, it’s essential to perform retrospection properly. So the first thing that is very important: during retrospection, you should talk about all those things which were done well, discuss why you see them as done well and what issues you should improve in the future.
The second stage of every retrospection discussion is what went wrong. But it shouldn’t be the main focus. If something went wrong, you discuss why, what happened, why something went wrong, and how you can change it in the future. It looks very simple, but the thing is that many teams don’t see the value in retrospection.
One more thing: if you invite for retro your stakeholders, people not involved in development who are not part of them of the development team, then you can be sure that your developers will not be open as they should. Talk and analyze inside your team.
If you want to learn more about the scrum methodology, here are interesting articles and videos:
About the Authors
Do you want to know how to
estimate the budget needed
for your project?