Answer the question
In order to leave comments, you need to log in
Terms of reference for the site: a pitfall or a lifeline?
When the customer contacts the web studio regarding the development of the site, after preliminary negotiations, a technical task (hereinafter referred to as the TOR) is drawn up. The more detailed the nuances of the future site are spelled out in the TOR, the fewer questions and misunderstandings will arise in the relationship between the customer and the developer in the future. So, the TOR, which describes the future product in detail, down to each "screw", does not allow the customer to say in the future that something does not work as it should, because everything is written in the TOR.
On the other hand, the TOR, compiled by the developer in general phrases from the words of a customer who had no experience in the development of customer sites, allows an unscrupulous developer, having created a limping website prototype on both legs, to say that nothing more was written in the TOR.
So, what is TK after all: a lifeline for both parties in resolving disputes over the created product, or a pitfall in the relationship between an inexperienced customer and an unscrupulous developer? Hence the question: who makes up the TOR, and who needs it more?
Answer the question
In order to leave comments, you need to log in
Firstly, the TOR is necessary for the customer to understand what he still needs
. Secondly, the TOR can change during execution
. Thirdly, the ideal option is for the contractor to focus on the main idea within the budget. But not everyone and not everyone can.
0.
TK
=
["...need a website, more or less, how's that... and add ...."
] Maximum depth of nesting levels of subsections in TK: DEEP
5. DEEP>3: TK+1 = [section text of one of the upper levels of TK], GOTO p.1
PS: In general, TK is to bring mutual understanding, not conflicts. ..
The customer himself, as a rule, is not able to draw up a competent technical specification. The TOR should be compiled by a technically competent specialist, fully taking into account all the wishes of the customer and the capabilities of the developer. If the TOR is drawn up correctly (and conscientiously implemented), then subsequently no questions will arise. But about a separate fee for improvements: the client cannot always imagine exactly what he wants, because the fee must be demanded only for really large alterations. Unless, of course, the performer wants to stay in the industry as a result.
A competent TK is an image, and at the same time a concept of your project, on the basis of which the contract will be created.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question