We determine the budget, timing and scope of work for the project. The purpose of the stage: to create a document with goals and objectives, evaluate each element of functionality in hours of work and estimate their cost, describe the technologies, potential risks and responsibilities of the parties.

After discussing general issues, we move on to specifics: we clarify legal issues, sign documents and form a team.

The team's composition depends on the specifics of the project. Animation and sound specialists are important when developing a game, and creating a banking mobile application is impossible without a security specialist. The number of participants in each role may also vary: for every ten developers there may be one analyst and one designer, or three analysts and five designers.

At this stage, all elements of the system are worked out in detail: business processes, necessary functions, security, performance, scalability and fault tolerance requirements are described. All this is collected in technical specifications.

Thanks to our SCRUM development methodology, the process is always visible and understandable, there are concrete results at each stage, all participants in the process support communication, and most importantly, the project is highly flexible and adaptable during implementation, which allows for qualitative changes to be made at all stages of development.

No project can be completed perfectly the first time: errors may occur somewhere. QA, following a pre-designed test plan, checks the project blocks one by one and finds errors.
After bugs are corrected, the project is sent for regression testing - this helps ensure that new changes will not affect the operation of other sections of the application.

Once all errors have been corrected, the application is sent to the end user. Depending on the project, this could be publishing in app stores, integration with other company services, or releasing a new version of the application.

Work on the product does not end after the release. Feedback comes from users, sooner or later errors are discovered, new ideas and suggestions appear. The process begins anew, starting with the analytics and evaluation stage.