Why Standards?

We value quality as there are no tangible outsourcing benefits if the quality itself is compromised. Amoebaa has devised a unique 3 point Quality Improvement Process in order to assure that there are no code quality issues in Amoebaa’s work. These points represent the inherent quality improvement guidelines being followed in all our projects.

• Each day the developer will give at least 30 minutes to study the code he/she has written and think of potential improvements in the same. This time will NOT be billed to the client. It the responsibility of the developer to take such time out and work towards code improvisation.

• Each project would undergo a regular pre-decided cycle of peer code review. This entire process would be “black boxed”, i.e., the programmer will not come to know who specifically among his peers is reviewing the code, but the review report would be publicly visible to all. The purpose of the code review would not be to demean or demoralize any one but to encourage best practices and improvise the existing code with a collective thought process.

• Amoebaa would be sending a weekly performance review and feedback form to the onshore project manager so that we can track the problems before hand and get to know any existing or potential issues which the onshore project manager might be facing. The purpose is to avoid escalations and rectify them at "runtime".

Quality is an ever-extending goal - the better you are, the better you need to be. The management of the quality process is endless, and marked only by milestones, never by completion. Amoebaa recognizes that, to fulfill our goal of self-evident quality, we need to constantly improve our deliverables to match the increasing expectations of our clients.

Software Development Methodology

At Amoebaa, all projects follow a Chaos Theory based well-defined project life cycle. We follow standard software development methodology, which helps us to provide very cost-effective and efficient solutions. The following are the various phases of software development life cycle followed at Amoebaa, which commensurate with internationally accepted standards.

Software Development Process

Phase 1 -Elaboration: Requirement Gathering
This is the first phase for every project when our business consultants meets the client to understand the course, design, and platform requirements. These are brainstorming sessions that help determine the over all business objectives and marketing goals. The initial scope of the project is then defined in terms of cost, effort, schedule, and deliverables and functional specifications are generated. Extensive feasibility study is done, after that proposal agreement is signed with client.

Phase 1.1 - Analysis & Design
Specialists from project management, software engineering, instructional design, and graphic design analyzes the client's requirements, design the hardware and software architecture and their implications on product development. Based on the analysis, a design specification document is prepared. Along with this test plans gets generated.

Phase 2 -Construction: Development & Testing
This is the stage where the project is actually off the ground. Amoebaa builds the application in progressive phases or increments upon approval of development specification by client. First the prototype is created, which is functionally complete and runs on the actual platform envisaged or different prototyping techniques are used . Once the client approves the design and the prototype, the production team starts the development process. This is where scripting, creation of graphics, and coding take place. Testing begins right at the prototype phase and continues through various project milestones.

Phase 3 - Transition: Implementation, Deployment and Training
Once the system goes into production mode, comprehensive training is extended to the end-users; not only to administer and maintain it, but also to make them understand the underlying technology and development tools. The end-users are trained to use the application effectively. Follow-up action in terms of close monitoring of the system and applications ensures immediate response to issues.