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 …
One of the first steps in any projects is gathering and defining requirements. These are needed to measure whether the features being built are useful. Requirements also give us a way to map progress and eventual success. Sometimes there are projects where we will have all the information we need to get started. However, most projects will require us to gather, define, and refine these details from others. Gathering Requirements The process of gathering requirements from others can be complicated …
It is hard to run a business without paying attention to IT at some level. The required amount of work might be as simple as keeping up with a couple of subscriptions to websites. On the other hand, it can be as complex as running a team of thousands. Although IT provides several options, the cost of technology in solutions is often estimated incorrectly. In these cases (and all points between) one of the most important factors to keep in mind …
