The IT2Max development team adopts project methodologies based on the client's project specifications and requirements. We mainly use two common methodologies in our company.
Waterfall Model:
Many traditional software development projects follow the waterfall model. In this case projects are similar to the Software Development Life Cycle (SDLC) which includes 5 main phases: Requirements Phase, Design Phase, Development Phase, System Testing, Release to Production.
The problem with waterfall models is when using this model each phase relies on the preceeding phase that needs to be completed begore moving on.
Once the analysis phase is finished, the whole project system will be design and documented. This phase is followed by project planning and budget creation. Once it's approved the system is developed, tested and release to live.
In real development environment this approach leads to great degree of inflexibility especially when complex proects are under development. Also the nature of this model makes it more difficult to change or modify passed tasks or modules once they are completed. You can imagine that let's say once requirements are writen this aproach doesn't allow changes during execution of the project.
When we can use Waterfall Model:
A waterfall model with feedback can be very effective choice to design a system that is clearly described. In this case only a few minor changes can be made in system design or its requirements. Also Waterfall model creates completed results in each phase being done and forever.
Agile Development:
Lately, companies have started to use Agile development processes and offshore outsourcing to realize incremental gains. The benefits that attract companies already doing offshore or companies already doing Agile development are quite different, however, as are the teams' motivations for blending the two processes.
Communication takes center stage, between the business users, the internal IT team, and the offshore team. Short iterations force frequent reviews so business people can approve functionality or provide feedback before too much time or money has been spent on that milestone. Agile development indirectly saves organizations money because it produces higher-quality code that meets customer needs, but cost savings aren't typically the key benefit.