• Starting projects with a commitment to the correct strategy, architecture, technology and methodology is critical.
• Understanding the client's requirement is essential.
• Manage the total project with the client to minimize risk while maximizing the return on the client's current technology investment.
• Field a winning, experienced project team with the technical expertise to enable success.
• Always work to enhance the relationships between the client's IT group and their user communities.
• Maintain a focus to deliver not only an application, but the fulfillment of the client's real business needs.
• Mindfully handle project details with the understanding they often possess changes in direction, problems and solutions.
• Make Knowledge Transfer a key part of the project plan.
• Partner and Mentor with the client to ensure self-sufficiency.

Methodology
   
The method not only addresses the developer's view of project development but also that of all the other parties who are interested in effective system development, including the users, project managers and quality assurance personnel.

• Many system development projects fail to meet the expectations of the end users. Such project failures can be classified into one of five basic types:
• The system fails to meet the business requirements for which it was developed. The system is either abandoned or expensive adaptive maintenance is undertaken.
• There are performance shortcomings in the system, which make it inadequate for the users' needs. Again, it is either abandoned or amended incurring extra costs.
• Errors appear in the developed system causing unexpected problems. Patches have to be applied at extra cost.
• Users reject the imposition of the system, for political reasons, lack of involvement in its development or lack of commitment to the project.
• Systems are initially accepted but over time become unusable and so pass into disuse.