We attempt to adhere to the most suitable methodology for each project. Our iterative development model ensures that customers can see how their project shapes up and their feedbacks are incorporated at an ongoing basis.

The main benefit of this approach is that the customer can always see how the project is shaping up, not like waterfall approach where customer sees projects only after one phase is complete. This process reduces rework. UML is used as a base modeling language in each phase.

Here, emphasis is laid on optimizing costs, schedules and quality.

We have expertise in iterative development methodology. We have successfully implemented Rational Unified Process (RUP), Extreme Programming and Agile Methodologies in our projects.

The approach we take for Project Management depends on the type of project. For bigger and more complicated projects, we adhere to the PRINCE2 methodology which gives us a clear understanding of the objectives, plans, risks & timelines of the project. For smaller projects where the end result is known, we prefer to use the Waterfall cycle, which is the most successful type for smaller projects where not many iterations are required and there are lesser chances of going back for major changes.

Agile development is used in cases where the end product is not known. Agile development is suited to problems where the endstate is not well defined, and the overhead of trying to arrive at that definition is not worthwhile Risk Management during a software development lifecycle Risk management is a very important role to play during a software development lifecycle. All methodologies we use, we maintain a risk log right form the Inception stage, where the broadly known risks to the system are recorded. The risk log is regularly updated with the progress in the project and is used as a tool to manage critical risks and take important decisions.