If you are the owner of an IT-business and you want to create or update your own website, you may be interested in the project evaluation by technical specialists. You can put all the work on the project on a team of programmers and do other things, but then there is a serious risk of getting out of the output is not what they were expecting. In this material, LENAL specialists will tell you how to properly evaluate the project and find an understanding with the technical partner.
In order to test the viability of the idea, you need to properly evaluate the project, calculate the possible budget, establish the desired deadlines and choose the specialists for its implementation. As in the game of chess, two players are needed to implement the project - the owner of the product and the technical partner.
First of all, you need to have a clear vision of the future of the project. Think about what you expect. Then bring those wishes to those who must embody the plan. It is in vain to expect a detailed assessment after an approximate description of the project idea, so your explanations should be as clear and structured as possible.
The ideal scenario is the creation of a working group from different departments of companies. In this case, you will have a complete description of the product at all stages of production, after which the team will form the general business requirements. Especially important this stage is in E-commerce when the off-line retail business goes digital. You should care for many details: process synchronization, product specificity, digitized product range, integration with ERP and CRM systems, payment method, delivery, and more.
Perfect if you have certain specifications or requirements. If not, describe the product and specify what problems your customers are going to solve. At this stage, you should have answers to the following questions:
- What is the purpose of the project?
- Who is your audience?
- Is there any examination, documentation for the future project?
- What is the planned load?
- How will the project be used?
- Who manages the development?
- DeLains and the budget.
Understanding the target audience and its characteristics will help the technical partner to create a project for the end user, so before starting to work on the project, you need to elaborate in detail your target user:
- description of the ideal client (habits, motives, problems);
- definition of channels of communication with the client;
- the main points of interaction with you (details of site navigation, filling out an application form, finding a contact page, etc.)
- customer behavior model, decision-making process and factors affecting it;
The format of filing business requirements does not matter. It can be a presentation or just a list sent by e-mail.
For example, if your product is a parking service, then you should understand that the main problem for your users is to find a free parking space and disappointment in case of its absence. Your solution to the problem is booking a place in advance with a prepayment.
The points of interaction are the following (User case): the user enters the application, chooses the time and place for parking, pay for it. This way, you save your customers' nerves and save time.
Again, before starting your project - imagine the problems that you help solve the client and the way to solve them.
Monetization of your project's model
We have already determined what does the customer, why and how to help him. The next step is to define the project monetization model. What can you earn and how to do it?
Sometimes, especially in E-commerce, this can be demonstrated by avoiding complex tables. You can simply explain that the costs of attracting and selling on the Internet are 3 times cheaper than in offline mode, so the margin will increase from 30% to 45%, and this will be enough to understand how it works.
This stage is also very important for understanding what kind of UX you will have in the futur, since the UX design is a powerful tool for impacting users. For example, if a business owner is interested in purchasing from $ 100 or more, then the very right UX can motivate the client to do this by offering additional products, services and services.
General features and limitations of the project
- Features of integration. The product owner describes what should be integrated with what, technical specialists form the project architecture;
- Terms of delivery; Limitations in real work;
- Budget constraints (approximate amount planned for investment in the project).
Project versionarity is a widespread phenomenon abroad. The first version of the project is launched as soon as possible in order to test its hypotheses and hear user reviews and then refine the product.
Ukrainian customers prefer to "polish" the product until it looks flawless before demonstrating it to the world. However, it would be wiser to start work shortly so that they can immediately receive feedback through user interaction.
The technical partner usually requires information on how big a product is, what features it will have and how the product owner plans to implement future versions of the product.
Both your and your technical partner's team should know what tasks to fulfill first. This will help you focus on the most important tasks, as well as optimally distribute downloads for the entire duration of the project.
TECH PARTNER'S SIDE
After the owner gives form his/her side all the necessary information, his role in this process is over and it remains only to wait for the result. Now it's a move on the technical partner, which should make a qualitative analysis on the basis of these requirements.
What can the owner of the product expect?
Detailed analysis of project features
A professional technical partner will do his best to familiarize yourself with your project as if it were his own. You can make the following if your technical partner requires all of the above information. If he just asks for a list of functions for your project - avoid it.
You can also test the engagement rate of your technical partner by having an online or offline meeting with him, asking him to describe your product. This way, you will have an idea of whether your views are the same.
Once you understand that your views are the same, it's time to develop a scheme of implementation - determine actions that will lead to a successful project. It is possible to organize work differently, but more often IT-companies divide work on sprints (certain periods of time) and make a list of functions to which they will work during this period.
Detecting project's architecture
Taking into account all project features - delivery terms, budget and integration specifics, the technical partner needs to develop the infrastructure and take into account all the project's databases, on the basis of which the architecture of the project and its component system (micro-services, etc.) will be built.
Detailed structure of work split
An experienced technical partner can take one step further and invite you to split the project into modules, each of which will have a fixed price. This will give you the right to manage your project and costs according to your budget. In addition, it can help you evaluate the risks and how to deal with them.
Why do you need it? You will have all the documentation that can be implemented by any team in case you are not satisfied with the cooperation with the current partner.
What about Agile?
Of course, there is a place for Agile. But any business has certain limitations both in the budget and in the deadlines. Any project requires analysis, and if you choose a flexible way, then the place for the preliminary evaluation does not remain.
If you choose an iterative method, you just need to know the rate per hour of the technical partner's team (time & material).
But, if you decide to make a really good product, get ready for the hard game. Do not leave room for misunderstandings. The more detail you will discuss all the details of the project, the more accurate the assessment.