Software developing is like building a house. first you have to figure out what kind of house you want. If you become clear about the plan you start to create the architecture. Ths all happens because you should have a plan about what you are going to build. Later design changes are much more expensive than when you would have planned the house from the beginning on thoroughly. Later you figure out the house was planned upside down.

In software design it’s the same. before there is no proper plan, user story and architecture, the programming quickly becomes a bad quality often with functional design patterns instead of object oriented design. This creates highly redundant code which could have being saved if there would have been a solid architecture in the beginning. This regularely happens especially on custom tools, but even general software development underestimates the risk of technical dept and the increase of money required to remove technical dept

Therefore, plan your Software from the beginning before you start coding.

• First user story
• Then requirement
• Then architecture
• Then coding