You Should Iterate Faster. And Better.
During a few days, I have seen, and evaluated, lots of different Agile practices. Here are the results, and how people fail Agile by overthinking features, under-observing outcomes, and limiting its iterations to just code.
During this week, I have been a member of several tribunals evaluating final degree projects of software engineering. For my surprise, many of them were still doing Waterfall, but even some of those who claimed to follow Agile practices, did not iterate even once.
The surprising thing is that I have seen replicated by the students the same problems that I found in my daily consulting job, in real environments. Although Agile is already more than twenty years old, old Waterfall practices stick.
Well, I know what are you thinking: it is not my case, we are following Agile practices, and we are iterating, and we are delivering at each iteration. Well, are you?
Between the students who claimed following Agile practices, there was a wide spectrum range of expertise:
- A few of them were the ones who did not iterate even once. They claimed to do iterations of documentation generation, interviews, and others. Sorry, but…
