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 …
One of the important parts of tracking project progress is defining milestones. These are points during the project where the required tasks and the goals for time meet. It only makes sense that the definition of milestones and how they are treated are an important part of project success. Defining Milestones Simplified Although these steps in the definition process are necessary, that does not mean they have to be complex. Every project is different, but I have found these guidelines …
