How We Work
In each particular case, we decide which model - Agile or Fixed Cost - we are going to use. Both of them allow to finish the project, without adding to its cost or extending its timeline. Some large scale and complex projects require using both models.
The specifics of each model are as follows:



The Agile software development model offers maximum flexibility. Particularly, it makes possible to alter project specifications and requirements when the development is already in full swing.

The Agile process consists of short cycles - sprints - with the client able to review intermediate results after each cycle.
Sprint
Sprint
Sprint
This model is the best fit in the following cases:
When project requirements and specifications can change on the development stage.

The scale and duration of the project are such that it's difficult to determine in advance its stages and timetable.

The client and the developing team maintain a constant feedback loop. The client can get involved in the development process at any moment.

When it's important to see the results early on. The process allows to get the intermediate results early in the development, and, after each sprint, the team and the customer can track and review the changes.

The product has to be released as quickly as possible. The Agile process allows to minimize the time spent on advance planning.


Agile
1.
Implementation Stages


1
Testing
The Client: On this stage, the client explains to the team the general idea, formulates requirements, and establishes priorities.

The result: At the end of this stage, the developing team has a set of project specifications. The budget and project timetable are also set. User Interface prototypes are created. The stage finishes with the signing of an Application Development Agreement.
2
Building an MVP
The Client: At this stage, the client can review the intermediate state of the project and offer feedback at the end of each sprint.

The result: The result of this stage is the Minimal Viable Product. (MVP) Also at this point, all the following development stages are clearly outlined.
3
Project Development
The Client: The client gives his assessment of the MVP and resumes to track and review the subsequent changes.

The Result: At the end of this stage, the team has a finished product that passed acceptance tests and ready for release.
4
Product Release
The Client: The Client accepts the finished product and supervises its integration into his IT infrastructure.

The Result: This stage ends with the signing of the acceptance certificate by the client.
5
Product Support
The Client: The client uses the product and can formulate and submit requests for its modification.

The Result: The stage ensures a consistent feedback loop between the client and the team while the former uses the product.
The Waterfall development model suits the best projects with their specifications clearly defined in advance.
This model presumes a step by step progression through the development stages. Each subsequent stage begins only when the previous stage is finished. The key characteristics of the Waterfall model are the fixed project budget and the impossibility to change product specifications after development has started.
Using this model is justified in the following cases:
The development process has to be accompanied by the reporting system tracking the resources and time spent on each specific task.

The client can provide the detailed product specifications and these specifications are not subject to change.

The project has to be developed within the specific budget limits.

The client cannot review/participate in the development process.

There are no limits on time and resources available for the project.
The Waterfall Model
2.
The Fixed Cost development process
consists of the following stages
1
Initial assessment
The client: The client presents to the team his business idea, project specifications and goals

The result: At the end of this stage the project team has detailed project specifications and UI prototypes. The project budget and timetable are set. The stage finishes with the parties signing a Software Development Agreement.
2
Building an MVP
The Client: On this stage, the client reviews the minimum viable version of the product and offers feedback.

The Result: The stage results in building a Minimum Viable Product. (MVP) The subsequent stages of product development are also clearly defined.
3
Testing
The Client: The client reviews the MVP and subsequently provides feedback at each cycle of the software development.


The Result: The software that passed acceptance tests and ready for release.
4
Product Release
The Client: The Client accepts the finished product and assists in the process of product integration.

The Result: This stage results in the client signing an acceptance certificate.
5
Product Support
The Client: The client uses the finished product and can formulate and submit requests for modification.

The Result: Support at all the stages of product development and after its release.
We'll find the best solution for you!
Send Request
Enter your contacts
Our manager will call back for consultation