“We should do it that way because it is best practice!” Does this sentence sound familiar to you? I’ve heard it many times in the context of software development. I don’t know why, but when people say the phrase “best practice”, most of the room agrees with them without hesitation – almost like they’ve cast […]
The truth about best practices. Read More »
In the previous article, I diagnosed issues with what I called the standard approach.I recommend reading it first before jumping into this article. What I encourage you even more to do is conduct a retrospective of your retrospective meeting. You may find your own issues that I did not mention. As stated in the previous
How to Run Better Retrospectives Read More »
In my last article, we explored what makes retrospectives valuable. We defined three major external factors: dedicated time, frequency, and taking outcomes seriously . Having all it set, now, we shift our focus to the retrospective meeting itself. Within this article, I will first define the general approach cultivated by most organizations. Next, based on
Retrospective on retro – hidden improvement Read More »
At some point, most IT organizations decided to become Agile. Hence, they decided to implement the Scrum framework:). Many people dislike Scrum because it requires numerous meetings that seem for some people wasteful. However, one meeting proves essential: the Retrospective. Teams consistently undervalue and ignore this critical component. It is one of the most important
Undervalued retrospective and ways to improve it. Read More »