Not an idle question about web development
The question is the following (and, in this case, not idle). No, I will first describe the situation.
A certain regional company has conceived to make a modern advanced web store with a bunch of services. The management instructs the manager to find contractors. That addresses to the first (got). Those call the sum. Expensive, refuse. Find others. Those agree to start work, begin to clarify the technical task, which has never been written. The base matrix of the technical task appears. The second is called the approximate price. Expensive, the manager refuses. With already received initial TZ finds the third. Those begin to lay out the TZ on the shelves, according to the services, the TZ begins to slowly acquire a human, close to the technically working kind, some still call the price. The customer (manager) is bargaining, they decide to do it in stages and break the payment in stages. As these are already third-party contractors, the responsible manager already knows a bunch of technical terms and approximately sees the structure of the project as complex stages and problem areas. With the third, they agree to start at least with something - they make sketches of the “first page”, offer options for the logo, markup for the modular grid, basic information architecture (sat down, systematized the data - the catalog, information sections ...).
Here the manager remembers that - yes, it's expensive. And begins to look for a fourth contractor. Having on hand. Quite a real TK, a developed information architecture, a logo and even site sketches that stipulate that “we have this, but THIS DESIGN DOES NOT COME TO US, we NEED A LITTLE CHANGE HERE AND HERE.” In the fourth, the process does not necessarily stop, there may be fifth, sixth, etc. As the information progresses, the information is added, the technical specifications are improved, and more and more blanks and related items appear.
The chain breaks, as a rule, quite by chance, in conversations in PM, detective research even allows to detect all the nodules of the chain (companies or groups of developers who have participated in the preparation of TK for free and other things, including manager education).
')
I have seen a similar chain in the last 2 years for the third time. The question is this. How common is this practice, and how are similar customers usually treated. By the way, an interesting opinion from both the potential customer of a large project and the developers.
A certain regional company has conceived to make a modern advanced web store with a bunch of services. The management instructs the manager to find contractors. That addresses to the first (got). Those call the sum. Expensive, refuse. Find others. Those agree to start work, begin to clarify the technical task, which has never been written. The base matrix of the technical task appears. The second is called the approximate price. Expensive, the manager refuses. With already received initial TZ finds the third. Those begin to lay out the TZ on the shelves, according to the services, the TZ begins to slowly acquire a human, close to the technically working kind, some still call the price. The customer (manager) is bargaining, they decide to do it in stages and break the payment in stages. As these are already third-party contractors, the responsible manager already knows a bunch of technical terms and approximately sees the structure of the project as complex stages and problem areas. With the third, they agree to start at least with something - they make sketches of the “first page”, offer options for the logo, markup for the modular grid, basic information architecture (sat down, systematized the data - the catalog, information sections ...).
Here the manager remembers that - yes, it's expensive. And begins to look for a fourth contractor. Having on hand. Quite a real TK, a developed information architecture, a logo and even site sketches that stipulate that “we have this, but THIS DESIGN DOES NOT COME TO US, we NEED A LITTLE CHANGE HERE AND HERE.” In the fourth, the process does not necessarily stop, there may be fifth, sixth, etc. As the information progresses, the information is added, the technical specifications are improved, and more and more blanks and related items appear.
The chain breaks, as a rule, quite by chance, in conversations in PM, detective research even allows to detect all the nodules of the chain (companies or groups of developers who have participated in the preparation of TK for free and other things, including manager education).
')
I have seen a similar chain in the last 2 years for the third time. The question is this. How common is this practice, and how are similar customers usually treated. By the way, an interesting opinion from both the potential customer of a large project and the developers.
Source: https://habr.com/ru/post/5182/
All Articles