The difference between good and bad software lies in coordination of IT processes. Badly managed software projects are bouncing from one hotfix to the other, with many work over the weekend. In well managed software projects farsighted decisions are made, capacities increased and problems detected before going into testing phase.
We at Tempelhove have made this experience in several software projects ourselves. Therefore we know precisely which steps are needed to form a good project out of a bad one. And we know examples of opposite cases. We understand the urgency of customers requirements on the one market-driven side. But we also know the feasibility on the technical side of the software. We know how to write sustainable software code, which survives also the next performance test.
