Introducing a new series of short videos from ITQuick, Inc. In the first season, we described in detail what roles make up the development team and answered customers’ perplexing question, «Why so many people needed for my project?» And in the second season, we answer an even more consequential question: «Why is it so expensive?»
Developing custom software products to meet individual business needs is a more expensive endeavor requiring ample time and financial investment over a longer period of time than those new to it sometimes anticipate. The decision should be taken thoughtfully and deliberately. The client needs to have an idea of the development process and to understand its stages. We present all the necessary information to make these important decisions, including new videos on our YouTube channel.
We will tell you how tasks are set when designing a new IT-product, how the project architecture is born from conception – ideas and process logic, how much time it takes, how technology stacks are selected, how communication with the customer is conducted, and of course how to calculate the approximate cost of the product or service. All these questions lead us to the concept of MVP (Minimum Viable Product) — a product that has minimal, but sufficient features to meet the needs of new startup customers.
Our first video of the new season is devoted to the stages of MVP development.
Stages of MVP development
MVP development is always the creation of something new, which did not exist before. In many ways, this process is similar to constructing a building, when first we think about what we are going to build, for what needs, then we make a project, choose contractors and building materials, bring the project to life and then, if necessary, make some changes.
When working on an MVP, our experts distinguish three main phases:
- Design (business process design, process design)
STEP I. Design
1.1 Business design
During the initial interview with the customer, the business analyst discovers what ideas need to be implemented and makes a detailed description of all necessary functions. In other words, the analyst determines the functional perimeter.
Based on this data, a description of user scenarios and screen layouts are created.
1.2 Process Design
- The next stage involves the inclusion of an architect who develops the general top-level architecture. And also at this stage, the optimal technology stack is chosen.
- All this gives us a basis for the creation of a top-level development plan and the role composition of the necessary team. And it allows us to give an initial estimate of cost and timing.
STEP II. Production
Unlike a normal construction site, where it’s impossible to make changes to the foundation, in the development of an IT product, the design is iterative. You make a part, test it, change it if necessary, test it again, move on to the next part. At any moment, you can go back any number of steps and make the necessary changes in the so-called «foundation.» The entire process is divided into two-week stages for ease of management and transparency. This approach is called Agile.
STEP III. Development
As a rule, you don’t need very highly skilled developers to keep the system up and running. This is usually taken care of by a Junior or Middle-level developer from the customer’s side. Sometimes, if required, we help conduct interviews and find the right person for the customer’s team.
But if you need to modify the software or add additional features, this is where you need Middle+ and Senior developers. And you know we can always be counted on to provide them, if needed!
In subsequent episodes, we will elaborate on each individual stage and tell you about their features and pitfalls, and you will learn how to avoid common mistakes! Follow our episodes and subscribe to our channel!
Thank you very much.