In Scrum, you’re expected to do a retrospective at the end of every sprint. The retrospective is the moment where the team is reflects and improves their way of working. This is one of the fundamental inspect and adapt checkpoints of Scrum that makes it so great. But should retrospectives always happen at a fixed time, at the end of the sprint?
You are currently browsing the archive for the Agile category.
I was referred to a post about a keynote speech Jeff Paton gave at XP Days London 2007. It’s called “The waterfall trap for Agile projects” by Gojko Adzik. The initial argument of the post is that iterative is not the same as incremental, something I will not argue. Gojko gives some nice Mona Lisa examples to illustrate the difference. Unfortunately, he goes on to develop some ideas and conclusions that I strongly disagree with and thus this article, in which I have developed my own “Van Gogh” counterexamples.
We will discuss three strategies to non-waterfall software development:
- Pure incremental
- Pure iterative
- Iterative and incremental