By: Oceangold  09-12-2011

Note: in some situations, it also makes sense to add an additional phase, Standardisation, during or at the end of Development/Purchase/Integrate, which specifically looks for modular segments which are appropriate for other applications or purposes. This involves adherence to your organisation's Development Strategy and Technology Roadmap. Please contact us for further details. 

Ensuring your development processes are fast, stable and flexible through effective technology, code management (regular reviews and release control), rigourous and frequent quality assurance, testing, prototyping, involvement of the client in all processes and client sign-off at the end of each phase. 

More important than the choice of technology is how it is applied, how it is used and how it is tested. True, some tools are faster, easier to use and more cost-effective. But technology changes, products die and are reborn elsewhere. Processes and lifecycles change much less frequently.  In fact, the same basic tenets used for large-team COBOL programming decades ago are still effective with large-team rapid-application development, RUP and Extreme Programming today whether it's COM or CORBA, VB or Java, DHTML or WAP. 

Then again, maybe you're trying something new and are unsure of the legal process involved. 

Are your network, servers, data store, Internet connections and security procedures sound, scaleable and secure? Can they cope with a denial of service attack or a fire in your operations centre? How important is your data? Can it be interchanged easily within all your systems?  Perhaps you are negotiating a new Service Level Agreement and would appreciate an arbitration point, someone who knows the subject and who will offer clear thinking and a holistic approach? Or maybe you just need an unbiased, accurate and honest opinion from someone who can communicate in clear, easily understandable terms?