There are a number of techniques that can be used to keep a project out of trouble. However, there are a lot of programmers who are unaware of them. Here is a short list of ways to keep a project out of trouble in the first place.
I make most of my living by fixing projects that have gone wrong, rather than controlling and performing on projects that are going well. I'd rather be doing the latter, because my customers are a lot calmer and happier when they're not in trouble. To that end, I present the case for doing a project by the book, rather than by cutting corners.
Why do we need it?
The first step in doing a project is not what you think. The first step is knowing why you need the new system, or modifications to the system in the first place. Some good examples of why you need a project done are:
| Attachment | Size |
|---|---|
| ByTheBook.pdf | 115.07 KB |
"I chose Linker Systems because of their unique ability to
understand the project in hand, plus offer suggestions relat -
ing to final operation of the ProofNet product. A schedule
was put together for development and Linker Systems came
in well before the deadline. This enabled Aqua-4 to start
testing the beta version earlier than expected and plan to
release the product at the Newspaper Exposition in Atlanta.
Linker Systems offers a total guarantee regarding the work,
providing the specifications do not change—this I find very
refreshing. Aqua Four consider themselves in a develop -
ment partnership with Linker Systems and plan to utilise
their unique skills well into the future."
