• Implementation of your business solution is a team effort. It must combine the customers' knowledge of the business requirements with our business process and SAP technical skills.
• High quality is not subjective - it demands fitness for purpose and technical robustness.
• Development can be incremental - not everything has to be delivered at once, and delivering something earlier is often more valuable than delivering everything later.
• Resources must be spent developing the features of most value to the business.

We use a framework of controls focused on delivery of high quality solutions to fixed timescales that meet the businesses needs. The key is delivering what the business needs when it needs it.

This is done by using the various techniques in the framework and flexing requirements and scope as required. The aim is always to address the current and imminent needs of the business rather than to attack all the perceived possibilities.

• A fundamental assumption is that nothing is built perfectly first time. The customer does not always know the final result needed, but does know the direction to go in. A useful 80% of the proposed system can be produced in 20% of the time it would take to produce the total solution.
• One of the underlying principles is that fitness for business purpose is the essential criterion for the acceptance of deliverables. This moves away from the approach of satisfying all the bells and whistles. The business requirements are documented upfront in the project charter and would normally be around 10 in number.
• In traditional approaches the focus is on satisfying the contents of a requirements document and conforming to previous deliverables. In our experience, these requirements are often inaccurate or misunderstood. The previous business and computer systems are very much black boxes which may be flawed and that the business needs are dynamic and may change during the project.
• More often than not customer project team time and resources are allowed to vary resulting in delayed delivery and increased expenditure. In our case, the exact opposite is true, time is fixed for the life of a project and resources are fixed as far as possible. This means that the requirements that will be satisfied can change as the business needs them to.