As with any large project, a Web application development project requires an effective plan. This helps ensure its successful implementation, compliance with established deadlines, and a given quality; these are necessary conditions for laying a foundation for cooperation and collaboration. An effective plan for the project implementation stems from the experience and qualifications of the Contractor and, as a rule, fits into one of the internationally recognized methodologies for software development.
Today's market offers a variety of such methodologies, each of which has its advantages and disadvantages. Our employees have extensive experience in contract software development and can competently select the appropriate project-specific methodology (considering the characteristics of both the project and the Customer). However, the company's management prefers and uses for the majority of projects such recognized approaches as SCRUM/XP and RUP, not forgetting about the old tried waterfall model.
SCRUM/XP - Agile development
We use flexible methodologies to ensure we meet your project timelines and budget. These methodologies allow you to see the development at interval stages and make changes directly during the process. We divide the entire project into relatively small segments based on a time period of two to three weeks. At the end of each segment, you'll be able to review the project and know that that it is proceeding according to the plan or see the need to make alterations. You remain actively involved in the process, determining what should be accomplished by the end of each sprint and milestone. Instead of spending so much up front time on document preparation and coordination, we begin to develop a functional Web application immediately and give you the tools and opportunities for iterative interaction with project development and any necessary plan correction.
RUP (Rational Unified Process)
Formally, the RUP also applies to agile methodologies and involves an iterative model of software development. It allows us to quickly change requirements, identify, and eliminate risks in early stages of the project, as well as effectively control the quality of your product. However, in comparison with other flexible methodologies, RUP is more documented and "strict." It provides guidance to all stages of the project development: from modeling to the final software version.
Duration of iteration varies from two to six weeks. Each iteration involves fulfilling certain procedures and preparing certain documents in the UML (Unified Modeling Language). We use RUP because it unites the advantages of modern (agile) and traditional (cascading) methodologies. We find this approach is optimal for implementing technically complex and large-scale projects when documentation is obligatory.
