The first stage of our development process involves working with you to document the project's purpose, requirements, team, and timeframe. The information we gather during this stage enables us to make informed decisions about how to best implement your project.

purpose

• what is the purpose of the project?
• what business problems does it aim to solve?
• who are the project's end users?

requirements

• what is required in relation to the project's:
  • functionality
  • look and feel
  • usability
  • performance and capacity
  • security
  • maintenance and enhancements
• are there any functional or technical constraints within which we need to work?
• how will the project's success be measured?

team

• who has final approval of the project's deliverables?
• who is our main point of contact in your organization?
• are there other people in your organization that can provide advice during other stages of the development?

timeframe

• when must the project be delivered?
• what is the project's budget?

The second stage of our process involves developing the project's specification documents. These documents detail how we intend to meet the project's requirements.

The project overview provides a summary of information gathered during the scoping phase. The technical design specification provides details relating to the project's functionality and outlines how that functionality will be implemented. The user interface specification provides guidelines for design of the project's "look and feel".

Once the specification documents are approved the project moves into development. We use an iterative development model that allows you to use, test, and approve each part of the project as it's built. This ensures that errors and alterations can be addressed with the least possible impact to the project as a whole.

Party time! When development is complete and the project has been tested to ensure that it meets the requirements set out in stage two, it's deployed to the end users. We then monitor any feedback from users in order to determine what, if any, additions or alterations should be considered during the project's ongoing support and review.

Invariably, end users will provide suggestions for changes to the project once it's deployed. And often, constraints of time and budget will have meant that "wish list" items discussed during the scoping stage were not implemented.

During this final stage we provide ongoing support and maintenance of the project, and periodically review user's enhancement suggestions to determine whether they can be implemented in another round of development.