Mobile application developer brief: 15 key questions to ask the client
The mobile marketing market is constantly growing, new developers are coming, new interesting projects are being created. We try to keep up with the times. That is why our community is now called Digital Professionals Hub and you can read materials not only about the features of web development, but also about topical issues that a mobile application developer can touch.
So let's start with the main thing! Before proceeding with the development, it is necessary to clarify in detail all the requirements of the customer.
In order to develop a successful application, you need to do everything right from the very beginning. The main number of conflicts between the customer and the developer is due to the lack of documents defining the details of what needs to be worked out. Not all questions are required to fill out, but it is very important to immediately convey to the client the importance of working through the task from the first steps.
The first part of the brief: questions to help determine which particular application your customer needs
To begin with, we will understand what the customer’s company is doing, and what purpose it has in ordering an application from you. What kind of results the client is going to achieve with the help of the application: to help increase the influx of customers directly, to collect the target audience, to increase sales, to implement the mobile part of the integrated advertising campaign, to speed up or optimize logistics processes (something else?)
So, questions that will help determine with whom you are dealing, and what kind of application your client needs.
')
1. What does your company do?
2. How do you plan to use the application in your business?
3. What type of application do you need? (here it is worth pointing out for clients a brief description of the types of applications)
4. What results do you want to achieve with this application?
The second part of the brief: the definition of the functional and technical features of the application.
Let's go to the application itself. To make life easier for the client and not to force him to explain on fingers what functionality is required from the application, ask him to show several examples of such applications. Let him note that he likes in these applications, and what he sees in them cons. So the customer will more fully define the list of basic functional blocks.
Not less important is the question for which platforms the application should work: here the client will most likely need your help - he is unlikely to understand the intricacies of compatibility. Tell him about the features and benefits of various platforms and technologies, the client will be grateful for your help. For example, iOS leads in North America and Europe, but in Russia, Africa and Asia, Nokia Symbian is the most popular platform.
We determine the functionality and technical characteristics:
5. Give examples of such applications.
6. What exactly do you like about these examples?
7. What solutions in such applications do not you like?
8. List the main functionality of the future application:
10. For which platform should you implement the application in the first place?
The third part of the brief: the post-development stage, technical support and update support
It is very important to discuss who and how will support and update the application. The customer may entrust support to you, or may wish independence. Are there any IT specialists in the company who can do this? If there is no such expert, you will most likely need an application management system with a user-friendly interface.
So, the final group of questions:
11. How should the data be updated in the application?
12. Is there a need to develop a site application?
13. Who will be involved in technical support of the application? Is maintenance required after warranty service of this application?
14. Is there a need to create an application management system?
15. Who will own the copyright to the application and in what form (exclusive or non-exclusive rights)? This question should not be left "by default"
And the last is the contact information of the client.
Find out who the customer will oversee this project. It is useful to understand whether this person is an IT specialist or not: it will help you choose the language of communication with the contact person. Check all methods of communication: e-mail, Skype, work and mobile phone numbers.
Drawing up such a brief will allow you to make a commercial offer, and a client to see a professional in you.
So let's start with the main thing! Before proceeding with the development, it is necessary to clarify in detail all the requirements of the customer.
In order to develop a successful application, you need to do everything right from the very beginning. The main number of conflicts between the customer and the developer is due to the lack of documents defining the details of what needs to be worked out. Not all questions are required to fill out, but it is very important to immediately convey to the client the importance of working through the task from the first steps.
The first part of the brief: questions to help determine which particular application your customer needs
To begin with, we will understand what the customer’s company is doing, and what purpose it has in ordering an application from you. What kind of results the client is going to achieve with the help of the application: to help increase the influx of customers directly, to collect the target audience, to increase sales, to implement the mobile part of the integrated advertising campaign, to speed up or optimize logistics processes (something else?)So, questions that will help determine with whom you are dealing, and what kind of application your client needs.
')
1. What does your company do?
2. How do you plan to use the application in your business?
3. What type of application do you need? (here it is worth pointing out for clients a brief description of the types of applications)
4. What results do you want to achieve with this application?
The second part of the brief: the definition of the functional and technical features of the application.
Let's go to the application itself. To make life easier for the client and not to force him to explain on fingers what functionality is required from the application, ask him to show several examples of such applications. Let him note that he likes in these applications, and what he sees in them cons. So the customer will more fully define the list of basic functional blocks.
Not less important is the question for which platforms the application should work: here the client will most likely need your help - he is unlikely to understand the intricacies of compatibility. Tell him about the features and benefits of various platforms and technologies, the client will be grateful for your help. For example, iOS leads in North America and Europe, but in Russia, Africa and Asia, Nokia Symbian is the most popular platform.
We determine the functionality and technical characteristics:
5. Give examples of such applications.6. What exactly do you like about these examples?
7. What solutions in such applications do not you like?
8. List the main functionality of the future application:
- What should an application be able to do?
- What are the main functional blocks you can select?
- How will the application be used by the end user?
10. For which platform should you implement the application in the first place?
The third part of the brief: the post-development stage, technical support and update supportIt is very important to discuss who and how will support and update the application. The customer may entrust support to you, or may wish independence. Are there any IT specialists in the company who can do this? If there is no such expert, you will most likely need an application management system with a user-friendly interface.
So, the final group of questions:
11. How should the data be updated in the application?
12. Is there a need to develop a site application?
13. Who will be involved in technical support of the application? Is maintenance required after warranty service of this application?
14. Is there a need to create an application management system?
15. Who will own the copyright to the application and in what form (exclusive or non-exclusive rights)? This question should not be left "by default"
And the last is the contact information of the client.
Find out who the customer will oversee this project. It is useful to understand whether this person is an IT specialist or not: it will help you choose the language of communication with the contact person. Check all methods of communication: e-mail, Skype, work and mobile phone numbers.
Drawing up such a brief will allow you to make a commercial offer, and a client to see a professional in you.
Source: https://habr.com/ru/post/130395/
All Articles