Project Management Approach

Projects are carried out to achieve the ultimate goal. Our project manager keeps this goal in mind throughout the whole process and checks it regularly with the client so as to be able to adjust it in good time if necessary and to ensure that the result of the project is amended accordingly. Perfection is a desirable aim, but the feasibility of processes and systems has high priority with us. We use proven standards, tools and methodologies to carry out projects.

Prince2

Prince2 is applicable to all projects, and is highly flexible. Prince2 sees the basic principles of good project management as follows: ‚A project is a finite process with a clear beginning and end. It seems so simple, but in practice it appears that defining a goal is very difficult. By applying Prince2 characteristics, we help you to do so.,

We always use:

• The Business Case: Commercial justification for the project. This document answers the questions: What benefits does the project have for the organisation, to what extent does the project contribute to the corporate objective and how do the revenues of the project weigh up against its costs?

• Product Based Planning: A plan which is based on the products which have to be delivered in the interim and at the end of the project.

• Organisation: A defined organisation structure for the project which consists at minimum of a project manager, a client and a steering group.

• Stages: Manageable and Controllable stages of management. By subdividing a project into stages, the elements to be managed become clearer and hence more manageable.

• Management by Exception: The steering group only meets when really necessary. This is at the delivery times for stages when approval must be given for the completed work and a new stage can be started. So there are no weekly meetings with fixed agendas and unnecessary time-consuming discussion groups.
  

Rapid Unified Process (RUP)

RUP is a widely used methodology for iterative software development. Bearing in mind the time which it takes to build large software systems, it is not possible to create a whole system in one go. Requirements can change during the course of development as a result of technical limitations, changing requirements / wishes or a clearer understanding of the nature of the problem. Iterative development lets you break the project down into a number of subproducts and deliver each of these separately. This reduces the risk that the end product will not be what the customer wants. The customer can now give feedback for each subproduct, which can then be taken into account during the development of the next subproduct.