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 |
"Sheldon Linker was contracted by our team for his database expertise. We wanted to a database expert that could tune our utilization of MS Sql Server, Oracle and DB2 for performance and integrity. He delivered on his commitments and was easy to work with. We'd engage his services again if the need arises."
