Approach

We know that the project success depends on excellent communication. Thus, we work with you to put together a process that allows development of complex systems.

Human Resources:

Our team becomes an extension of your team, with a Project Leader who is responsible for major communication, coordination and technical supervision of the project. The entire team is available via email, phone, and instant messenger; and as needed, we fly out and spend time (days, weeks, or months) working along-side your team.

Technology & Processes:

Code Repository:
Each project has a Web accessible Source Control System that is hosted by AMC Bridge or you (SVN is most popular solution)

Bug Tracking:
Each project has a Web Accessible Bug tracking system (Bugzilla, Mantis, Jira are typically used)

Time Tracking and Project Management tools:
This area varies widely from project to project – it could be Excel files stored in the Source control system, Microsoft Project, your organization’s time tracking system, or our own Time Tracking system.

Project code structure:
A Dev->Test->Production code structure is widely used, where Dev is the area of current development; Test is the area where “latest” version of code resides and most QA is performed; and Production is version of the code currently released to customers or are for the most stable version.

Submissions and Builds:
A weekly build schedule is most popular. There is predefined day of the week when developers have to submit “ready to test” items to the dev version of the code. The submitted code is built, run through the regression tests and moved to Test area for further testing. Finally, most project also have automated daily/nightly builds of the development area to insure the code compiles, this process also include simple reduced regression.

Quality Assurance:
Our developers are required to unit test code before submitting to the system. QA automation is leveraged as much as possible – through both custom automated tools, as well off-the-shelf tools are used. QA procedure and specs are developed along with the project and executed by dedicated team members on the Test version of the code. Reported issues are tracked in the bug tracking system and assigned based on priority and severity.

Release and Documentation:
Release timing and frequency varies by project. If needed, our team can produce Documentation and Release Notes.