When you listen to a professional or college sports team discuss a bad stretch, they often mention that they will get back to basics. These statements are not a knock on the players. They understand the basics. It is instead a focus on doing the things that have to be done. It is a return to their foundation so they can simplify and then work on building again. This approach happens to work well for software projects as well. Spinning Out …
The Agile methodology has a lot of pros and cons. In fact, it is one of the most common argument/discussions I have with a mentor of mine. He likes to point out (correctly in most instances) that the Agile approach skips out on important design. It causes a lot of re-work because of that lack of up-front design. This re-work is only partially a problem. The Agile method assumes that changes will come during the implementation of a project. Instead of …
It takes very little time in the software business to see that implementation is king. Software design and similar pursuits that lack a deliverable outside of documentation are pushed aside far too often. One may look at the poor success rate of software projects and draw a connection. In this post, I plan on doing exactly that. Software is Complicated The first thing we must agree on is that software has gotten complicated. There are all kinds of tools …
