Development Methodology 

All tasks are estimated and grouped into releases with an aim of delivering highest priority functionality first.  All tasks are approved by the client prior to being developed. 

Release Approach

We follow a best practice approach Development/Test/Staging/Production environments to minimise risk in deployment.

When the client is hosting the production environment internally, we prefer if the production and staging environments are both maintained by the client and as homogeneous as possible.

We provide deployment packages and documentation so that no access to your production environments is necessary.

Testing Methodology

1. Release initiated to new environment (e.g. staging environment)
2.  Internal testing by development team.
3. Client testing
4. Each bug submitted in a separate email with screenshots as appropriate.
5. Critical bugs are fixed in the current release.  Non-critical bug fixes are integrated into the next release.
6. Client approval

At the end of each release, we perform limited internal testing, including testing by resources not otherwise working on the project.  We perform testing on each environment we release to, before requesting the client starts testing. At this time we provide guidance to testers on testing approach suitable for the project.

We ask that each bug/change is submitted in separate emails, with screenshots where appropriate. Critical bugs are fixed in the current release.  Non-critical bug fixes are integrated into the next release.
When no critical bugs are found, the client is asked to approve the release.

What are Bugs

"A reproducible coding error that causes an unexpected defect, fault, flaw, or imperfection in a computer program." In other words, if any of the developed software does not perform as the developers intended, it is most likely a bug.

You can tell it is a bug when:

• The incorrect behaviour can reliably be reproduced
• The application crashes to code. (does not include 3rd party applications, experiencing bugs)
• The application displays incorrect values
• The application is missing specified functionality that was agreed in the specification review process or screen mock-ups

Visibility to client

 Task Visibility.
As each task is completed, we send a ‘Done’ email describing what was done. This often includes screenshots, and gives you the opportunity to review work while it is fresh in the developer’s mind. Changes and fixes identified at this early stage ensure the best value for your investment.

Project Cost Visibility
Each week upon request you can receive an update on project work completed to date, invoiced amounts, and approved amounts.

Deliverable Visibility
We maintain a testing server for you. Testers can remotely view the content on this server giving you the opportunity to provide early feedback on release deliverables.