For every customer our process is different depending on the specific project and the customers need. You may have a specific version control system you want usedor your own bug tracking system. We work around your needs.
Daily Reports
You will receive a report in the morning that shows you the work done the previous day for every person working on your project. This is an excellent way to stay up to speed and more importantly to raise flags if your priorityies are not being worked on
Weekly Reports
These. For customers that are directing the developers on a daily basis, this are not needed.
Milestone Reports
For customers that are directing the developers on a daily basis, this are not needed.
Shared Development Server
We maintain a dedicated
Source Control Management
You always have access to your latest source code. Our internal procedures are that programmers go no more than two days without checking in code.
If there are any conflicts in the source (the client changes the same file as a devloper), the manual synching is done by our developers at the next code check-in.
Automated Builds
The build process can include making the latest installer, it can also generate remote upgrade files. Often at the end of the build process automated testing (see below) is kicked off
Automated "Smoke Testing"
Smoke tests catch problems at the earliest stage. They are run every time after the automated build process. These can range from a simple test that simply hands values to a procedure and checks the output to a long running complex process. An example of this is our
Quality Assurance
On some projects we have dedicated testers who test full-time for one client. This is very useful on large, complex products. We also have testers that are used as needed on projects. They as needed as module is ready or towards the end of a milestone.
The testing can involve only manual testing or it can involve automated testing and test script creation and manual testing together.
