After just two weeks of project development, it was already clear that the client requires help in the project organization, but not in the development itself. With the new test versions being released, the client can assess the current results and adjust the future direction of the development. Our shared goal with the client is to bring the product into the market site and make sure that the customers will use it. Pretty much anyone in this world can write the code, but not everyone can make a valuable product to its targeted audience. That's why we decided to involve our Head of Delivery.
Due to the continuous changes from our client, the fixed price model that we originally planned didn't work at all, instead we switched to weekly Scrum sprints and Time & Material cooperation model correspondingly. This decision has been specifically done to give the client the most fastest and complete results.
Originally, the client had planned to produce a hybrid platform for both the Android and iOS platforms, using either the ReactNative framework or some other hybrid framework for mobile development. And it seemed pretty reasonable, since the support of both platforms will be sufficiently and initially easier to make, plus it was cheaper. Once each of the application native platforms would be presented as a percentage of 100%, the total costs for two platforms would be 200%, while a hybrid application would require only 150% of the total effort. This is due to the components reusability of the server, which were built on NodeJS and the business logic. Seems pretty obvious as to what kind of direction our team has to choose, right? Unfortunately, the presentation layer for every platform must be done everywhere individually and that's where we hit a dead end.
The first stage lasted two months, resulting in a MVP (Minimum Viable Product). When completed, the client received the iOS application to give his final approval. Based on the initial stage results, the client decided to continue development with our team and began to provide additional user stories and feature requests, which were separately reviewed and estimated. After a total of eight months of development, the product moved from closed beta to the release version.