The first meeting with the customer, we squeeze the maximum.
I have been working on custom software development projects for several years and often at the beginning of my work, I was worried about how I can extract the maximum amount of useful and structured information about the future system. Indeed, more often than not, even for a commercial offer, it is necessary to present both technologies and exemplary methods of implementation, and this can all change the price. Yes, and about the timing would be nice to tell.
I managed to find the best option for myself.
At first meetings, I always dreamed of capturing thoughts, because you will agree, not every person can express thoughts consistently and structured. Most often, the customer has light chaos in his head with a kaleidoscope of beautiful views of the future system, as well as beautiful pictures of how his business instantly goes uphill immediately after implementation. And if you ask questions without a clear plan, meetings can take a long time.
Now I act according to the plan and this allows me to immediately win in many areas:
What is my plan?
')
I stock up with plain and colored pencils, a sharpener, an eraser, and a drawing album. It is much more convenient than a set of sheets, and the paper is denser, which allows it to not crumple when wiping.
It will help to remember some important moments from the meeting, if you forget them later, when analyzing the results. And in any case, it never hurts to refresh your memory. Just do not forget to warn the person that your meeting is being recorded, maybe he will be against it, although the likelihood of this is small.
You can meet in offices, although personally I like in a cafe more. All the same, our offices are usually completely uncomfortable places, and for a meeting and a good conversation, you need a cozy place, it would be better with a delicious coffee or tea. But of course the cafe should be without loud annoying music, and that meeting will be spoiled.
Maybe you need a computer to show the client some previous results or, say, to evaluate the work of certain interface elements in action. However, try to spend less time on the computer, otherwise you risk getting stuck and moving away from a constructive, clear conversation. Use the computer only in question-answer mode.
Get an overview of the system. What will do for whom is intended. Ask the customer to clearly describe the system in two paragraphs, describe all users and roles. Here's a tip that will help you: Imagine that the system is completely clean. Who will be the first to enter information there? What is this information? How it will be there to make?
I personally try to use action lists and UML notation. It is convenient, immediately structures information, it is easy to analyze and draw conclusions, and also to anticipate bottlenecks, which you should immediately pay attention to.
I draw two types of diagrams: action diagrams and structural composite diagrams. Also, if we discuss the interface, I try to make an outline of the interface and mark important points with colored pencils.
Here is a small example, written according to the customer:
There are workers in the production department. They compile the lists of equipment, fill in their properties and positions of the list. And, by the way, they attach files to the list positions, well, you can make them in a pop-up window.
As a result, we get two diagrams. One shows the actions of workers in the production department, the other is the relationship between entities.
Diagrams do not claim to be complete, they serve only as an example of documentation. In addition, you can distribute the interface in blocks and figure out whether to make files in a pop-up window or not.
If you continue to work with the project, then after the meeting it is a good idea to transfer everything from paper to electronic form, at the same time to refresh and supplement.
Results in the form of such diagrams, as well as possibly short stories (userstories), in the case of vague requirements, can be easily sent to the customer, no special knowledge is needed to read them.
In fact, you have already saved a lot of time, because you laid the foundation for the future worthy and complete project documentation. For such a detailed and illustrated technical task, you will be thanked not only by the customer, but also by future programmers.
Interesting projects and successful discussions!
Original: http://www.steinzeig.ru/2007/12/09/rabota-s-zakazchikom-pervaya-vstrecha/
I managed to find the best option for myself.
At first meetings, I always dreamed of capturing thoughts, because you will agree, not every person can express thoughts consistently and structured. Most often, the customer has light chaos in his head with a kaleidoscope of beautiful views of the future system, as well as beautiful pictures of how his business instantly goes uphill immediately after implementation. And if you ask questions without a clear plan, meetings can take a long time.
Now I act according to the plan and this allows me to immediately win in many areas:
- I save my and others time by reducing the number of meetings. This is especially relevant in connection with the craze for personal effectiveness.
- I immediately show myself a professional with a certain approach to work. This gives me extra points and takes them away from potential competitors.
- I am deeply immersed in the system and I can already write a preliminary statement of work for performers on it or on its separate part (in case the system is large).
What is my plan?
')
Preparing for the meeting
Writing accessories
I stock up with plain and colored pencils, a sharpener, an eraser, and a drawing album. It is much more convenient than a set of sheets, and the paper is denser, which allows it to not crumple when wiping.
Dictaphone
It will help to remember some important moments from the meeting, if you forget them later, when analyzing the results. And in any case, it never hurts to refresh your memory. Just do not forget to warn the person that your meeting is being recorded, maybe he will be against it, although the likelihood of this is small.
A place
You can meet in offices, although personally I like in a cafe more. All the same, our offices are usually completely uncomfortable places, and for a meeting and a good conversation, you need a cozy place, it would be better with a delicious coffee or tea. But of course the cafe should be without loud annoying music, and that meeting will be spoiled.
A laptop
Maybe you need a computer to show the client some previous results or, say, to evaluate the work of certain interface elements in action. However, try to spend less time on the computer, otherwise you risk getting stuck and moving away from a constructive, clear conversation. Use the computer only in question-answer mode.
A meeting
Where to begin?
Get an overview of the system. What will do for whom is intended. Ask the customer to clearly describe the system in two paragraphs, describe all users and roles. Here's a tip that will help you: Imagine that the system is completely clean. Who will be the first to enter information there? What is this information? How it will be there to make?
How to fix?
I personally try to use action lists and UML notation. It is convenient, immediately structures information, it is easy to analyze and draw conclusions, and also to anticipate bottlenecks, which you should immediately pay attention to.
I draw two types of diagrams: action diagrams and structural composite diagrams. Also, if we discuss the interface, I try to make an outline of the interface and mark important points with colored pencils.
Here is a small example, written according to the customer:
There are workers in the production department. They compile the lists of equipment, fill in their properties and positions of the list. And, by the way, they attach files to the list positions, well, you can make them in a pop-up window.
As a result, we get two diagrams. One shows the actions of workers in the production department, the other is the relationship between entities.
Diagrams do not claim to be complete, they serve only as an example of documentation. In addition, you can distribute the interface in blocks and figure out whether to make files in a pop-up window or not.
How to finish?
If you continue to work with the project, then after the meeting it is a good idea to transfer everything from paper to electronic form, at the same time to refresh and supplement.
Results in the form of such diagrams, as well as possibly short stories (userstories), in the case of vague requirements, can be easily sent to the customer, no special knowledge is needed to read them.
In fact, you have already saved a lot of time, because you laid the foundation for the future worthy and complete project documentation. For such a detailed and illustrated technical task, you will be thanked not only by the customer, but also by future programmers.
Interesting projects and successful discussions!
Original: http://www.steinzeig.ru/2007/12/09/rabota-s-zakazchikom-pervaya-vstrecha/
Source: https://habr.com/ru/post/17627/
All Articles