This white paper examines the problems of managing large information technology projects and how the Ripose Technique has addressed these problems.

Overview
There is no doubt that information technology professionals are facing mounting pressure to deliver quality systems on a wide range of platforms at an affordable price to their organisation.

There is a plethora of research notes on every facet of information technology development (Gartner to name but one). The one common factor in all failures is the inability to align information technology with the business. This problem has been at the top of just about every survey ever carried out as to why information technology projects either fail or end up costing more than estimated.

After 28 years in the information technology industry, and having read hundreds of articles, the need for a truly effective, integrated tool to pull together (integrate) the seemingly disparate tasks became the number one priority of Ripose Pty Limited. (Articles)

In his book 'Patterns of Software Failure & Success' (Published by International Thompson Computer Press), Capers Jones wrote the following summary (page 53):
'Managing software is one of the most troubling major aspects of modern business. Cost overruns, scheduling overruns and outright failures are more common in large software projects than for almost any other aspect of modern business. Yet the problems of software are not insurmountable and some companies have indeed overcome them. Careful attention to quality control, using trained specialists, using modern software estimating and planning tools, using effective tool suite and programming environments and keeping accurate historical data on software can immunise companies against some of the more common sources of software disasters'.

Yet on page 62, Mr. Jones added the following:
'As of 1995, there is no teachable, repeatable method for decomposing very large software systems into sets of smaller components that can be developed concurrently. From time to time decomposition is possible, but the overall inability to decompose very large software structures remains a chronic problem'.

Faced with all the dreams, promises, attempts and failures alluded to in the above articles, only a fully integrated top down approach, supported by a comprehensive tool set could solve the problem. The following would be a blueprint for such a 'dream' machine:

• The approach (technique) would have to be teachable, repeatable and produce results in a fraction of the time of any other technique/methodology on the market today;
• The tool would have to follow the KISS (keep it small & simple - sometimes known as keep it simple stupid) principle and fully support the technique.

This needed 'dream' machine has now been realised and read more by having a look at  the phases, stages, deliverables & sign off documents of the Ripose Technique.