Beyond Agile
Bonus Chapter: How can we iterate upon the Agile methodology itself, and improve it?
My chapter about Agile has received a positive response from the majority of readers. I am happy to be a voice of what many have already been thinking, but not have been saying out loud.
However, I admit that it was a very long chapter to read. I fear that my suggestions for improvements might be lost among my criticisms of Agile. I do not want to be known as someone who just criticizes without making any suggestions for improvement. Therefore, I wanted to write this relatively shorter post where I summarize how I believe we can improve upon the Agile methodology and develop software in a better way.
This chapter is just about my suggestions for improvement. If you want to know why I am making these suggestions or why I am criticizing some aspects of Agile in the first place, you might like to go back and read the original Agile chapter.
These are all my humble opinions of course. If you disagree, please feel free to comment and make alternative suggestions. I am always open to change my mind when presented with a good argument and some new evidence. Nevertheless, I must add that many times throughout my career, I have observed this methodology being applied quite successfully. There were many amazing products that were built following this way of developing software. Products with great features and very few defects.
I strongly believe that this way of development can help us produce great quality software within very reasonable timelines: