For projects, whose targets are well defined at the start of the project, the waterfall model (business spec –> technical spec ->development -> acceptance test) is most often used.
With this methodology, all deliveries are will be defined at start time. Normally, the customer provides his business specification, which contains all functionality he wants. This is then turned into a technical specification by us, defining how the requirements are implemented.
After all specifications are mutually agreed upon, the implementation (development) work starts.
Because of its inherent documentation detail, this model is especially suited for offshore projects.
The Agile Software Development Model keeps the development process flexible and lean.
This model focuses on targets rather than following processes.
The Agile Model is preferred, if targets are not very clear at the beginning, or if frequent and detailed consultations are necessary throughout the project, or if special creativity is required.
It is a model for a true development partnership.
The commercial basis is always T&M.
The V-Model combines Agile and Waterfall Models. It offers more flexibility than the traditional Waterfall Model, but also more stringent process execution than the Agile Model.
As steps and milestone are usually variable, the contractual basis is mostly T&M.
NearShore Solutions works, depending on the individual project requirement, with any of these models.