DawnBringer3D Tips & Tricks, Personal News, Game Development

Thoughts On Sprint Retrospective

I had my first sprint retrospective last week and it was a very useful thing to do.

Sprint retrospective is like a post mortem of the sprint : go through what went well and what could be improved. It becomes very powerful as you will have many retrospectives during the project, after each iteration you are able to improve for the next sprint!

Note that it is important that the improvement process is organized. When improvement process is organized it is a lot easier to handle, e.g. improvement will done during or at X – date, how it is done, who will be affected by it, person X is responsible for it.

I really recommend trying out Scrum. Iterative development is very useful if used right. If used wrong it will probably just do more harm than good. You need to give it some time, apply these processes step by step, results won’t show right away. Scrum doesn’t solve all problems, and it should not, it will identify more problems. And that is important : you cannot improve if you don’t even your problems.

Our team found loads of improvements to be done, we are going to apply some of those right away and some later. Remember that you might also find improvements that doesn’t just fit in to this project but might be good ones to next one, so it is useful to write those down too.