Summer can be a frustrating time. Much like the end of the year, there are a lot of vacations to work around, and your team varies from week to week. That makes this an excellent time to take your vacation as well. However, when you find yourself at work with limited staff or tasks waiting for people to return, there is an opportunity for catching up.
Sooner or later we have to consider how to change our systems. This situation can come from growth in business, changes in technology (or requirements), or systems that have aged poorly. When we reach the point of deciding on a move we often have to decide on the incremental vs. all-in approach to achieve our goal. There are times when one choice or the other is
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