Q. Why use methods?
A. A method defines a reproducible path for obtaining reliable results

To suit our customer's project management requirements and to achieve in depth business analysis we are able to follow a variety of methodologies, including DSDM, UML and PRINCE. In this way we can ensure we develop flexible solutions that meet our customers' business requirements on time and on budget. We have also developed our own proprietary methodology LADDER which is explained further below:

Listen in this most crucial of phases we ensure we spend enough time listening to the customer and understanding their business culture. We undertake interviews with user groups to identify clearly the project objectives. Also in this stage any restrictions on use of particular technology including any existing legacy systems or security considerations will be illuminated.

Analyse after the fact-finding mission is complete we will draw up a conclusion to our findings in a document that will detail fully our understanding of the customer's requirements. Research into any new technology combinations is also carried out to ensure compatibility and integrity of the software solutions with any existing IT infrastructure or legacy systems. If the project is large enough an overall testing strategy is also defined during the analysis phase.

Design using information architecture diagrams, use cases and other modelling tools we will create comprehensive functional specifications to allow us to communicate our vision of the solution to the customer. The program flow will be visible and the customer will be able to feedback any changes. We also strongly believe in presenting our customers with prototypes to ease the visualisation of the end product. Choice of technologies and a system infrastructure are also detailed at this stage.

Develop well into the project lifecycle, the first line of code is written. By careful planning, research and analysis during the previous phases the code development phase should throw up no surprises. It is just a case of following the design and performing the necessary quality assurance testing at each logical stage i.e. unit testing, component testing and high level testing. Wherever possible we believe in using the iterative development model, this is where the customer will see the results of each "module" or "section" of code and can feedback if the functionality is not what they initially intended or if their functional requirements have developed since the original discussions.

Enable the code has been written, the functional specifications adhered to, the application in the test environment has been put through its paces but there is still a much work to be done. During the enable phase the application is deployed and tested in the live environment and any last anomalies are ironed out. It is all too easy to underestimate the importance of the this phase and once again careful planning and asking all the relevant questions during the analysis phase will help to minimise any last minute hitches. Also during this phase training is given, user manuals supplied and support is provided as the customer becomes familiar with the new application.

Review again a commonly overlooked phase and one that is vital to forward looking organisations. Although during an iterative development methodology the review process is made on an on-going basis it is still vital that once the application is deployed and the intended user group are now using the application in anger that a final review phase is undertaken. Interviews are carried out and feedback gathered to identify any discrepancies between the original vision for the application and the real usage. Although this is the final stage of the project lifecycle it can also be considered as the beginning of the next cycle of development. Looking into the future to further optimise and enhance the interactions of your customers, suppliers and colleagues.