“If you are afraid to change something it is clearly poorly designed.”
― Marin Fowler

One of the most important steps in agile development is the refactoring. Before actually getting involved in agile methodology, we should spend some time writing the legacy architecture of the project. I do not think we should use this methodology when starting a project; I strongly believe it should be another step before the famous sprint zero. You should design your project first. I clearly understand that a well engineered code is going to help in long term for every agile project in several ways. If you don’t want to be afraid to change your code in the future, it has to be well designed and structured. This is done by people who engineer code; there is a huge difference between just programming and engineer code.

Who do you think would win this fight? Many of you might say Chuck Norris, no contest. But if I may be so blunt — you’d be wrong! Bruce Lee would win this fight, hands down! Heck, he could win with his hands tied behind his back!

The same goes for the agile method. Some people will swear up and down that agile is the reason their project failed while others feel just as strongly that this methodology was the best change they could have made to their projects.

There are many ways an agile project can fail, though. In this post I’ll explain what can be done to avoid one of the most common mistakes.

About Agile Nucleus

For anyone curious about agile methods, Agile Nucleus exists to spread ideas about agile and lean thinking to business and life. What defines success for people using agile? We started this blog to formulate and distribute our thoughts about why we have chosen this approach and how it can help others bring their ideas to life.