What to do with useful ideas that interfere with work?
Work on large, serious or non-standard projects in most cases requires a special approach, enviable diligence, not a lot of patience and a strong mind. I can say that owners of small studios soberly assessing their resources often refuse such offers for a number of reasons.
In my opinion, the main thing is that for us (small developers) it is very “long money”. No matter how thoroughly the managers document everything in the terms of reference, in real-life development such a project quickly acquires ballast from various proposals, improvements, upgrades, difficulties not taken into account, poor feedback, new ideas, thoughts, etc., which arise in almost all stages of development.
It seems to be all these little things that are not seen separately, and somehow it is not serious to demand an extra charge for them. Since there are a lot of these little things in the process, their implementation leads either to a significant increase in time or to an additional burden on the development team.
')
Partially solves the problem, very detailed tz. but people write it too, and as practice shows, it is still not possible to take everything into account. Therefore, our next step was to split the project into logically complete parts, each of which is paid upon delivery. For example, select:
The number and volume of parts is determined at the discretion of the working group. There is nothing new and revolutionary in this, I think this is the case, or almost the same, the majority do. Because splitting turns “long money” into more or less “fast”, but does not solve the main problem with ideas, additions and other “ballast”.
Recently, in the list of the main stages, we are obligatory (last point) to include “Lapping”, sometimes combining it with verification and primary testing. And in monetary terms, the refinement is not cheaper than the other stages!
Such a simple approach allows you to maintain emotional balance for the entire team and the customer ... We calmly make the project moving from one part to another, anxiously recording all the wishes and ideas of customers, and our own in a separate file.
By the time when the penultimate item in the list is implemented, we get a working alpha. But most importantly:
In my opinion, the main thing is that for us (small developers) it is very “long money”. No matter how thoroughly the managers document everything in the terms of reference, in real-life development such a project quickly acquires ballast from various proposals, improvements, upgrades, difficulties not taken into account, poor feedback, new ideas, thoughts, etc., which arise in almost all stages of development.
It seems to be all these little things that are not seen separately, and somehow it is not serious to demand an extra charge for them. Since there are a lot of these little things in the process, their implementation leads either to a significant increase in time or to an additional burden on the development team.
')
Partially solves the problem, very detailed tz. but people write it too, and as practice shows, it is still not possible to take everything into account. Therefore, our next step was to split the project into logically complete parts, each of which is paid upon delivery. For example, select:
1. Design, layout
2. Build a site
3. Filling the project.
4. User Management
5. Interactive. Forums, comments, notifications, internal mail
6. Billing, etc.
The number and volume of parts is determined at the discretion of the working group. There is nothing new and revolutionary in this, I think this is the case, or almost the same, the majority do. Because splitting turns “long money” into more or less “fast”, but does not solve the main problem with ideas, additions and other “ballast”.
Recently, in the list of the main stages, we are obligatory (last point) to include “Lapping”, sometimes combining it with verification and primary testing. And in monetary terms, the refinement is not cheaper than the other stages!
Such a simple approach allows you to maintain emotional balance for the entire team and the customer ... We calmly make the project moving from one part to another, anxiously recording all the wishes and ideas of customers, and our own in a separate file.
By the time when the penultimate item in the list is implemented, we get a working alpha. But most importantly:
- A wonderful opportunity to evaluate the real benefits of add-ons from our list in terms of a solid project .
- It is when the main work on the project is completed that it becomes obvious that some thoughts were suggested “hot” and there is simply no need and much meaning for their implementation.
- It becomes clear to the customer how many volumes his “trifles” occupy :)
Source: https://habr.com/ru/post/66359/
All Articles