There are cases when the TK provided by the customer is incomplete, poorly compiled, or does not exist at all. What questions then do you ask before starting work and so that later no customer questions arise? Website design is of varying complexity and different quality, but are there any questions of a general nature?

  • one
    GOST! rugost.com/… - yapycoder
  • The most common questions are the price and terms :) - alphard

1 answer 1

In the "site" there are two main components: functionality and design.

  1. In terms of functionality, even the “behavior” of the site is relatively simple: it is described the same way as for any other software, except if corrected for the stateless nature of HTTP . Goals, means, use cases and other options and methods of describing "how it should work."

  2. As for the design, then my design partners usually do this: draw a few sketches from which the client then chooses the one they like. Further, this sketch is drawn in more detail, after which the signatures of both sides are put on this picture, it turns out the status of “Appendix No. (n + 1): Layout” and becomes an integral part of the overall TK on the site.

As for the implementation details (for example, a table or block layout will be used) - it seems to me that they do not have to be indicated in the statement of work, except when it is a) critical b) the customer has a good understanding of this.

The process of writing TK is always time consuming, requires an understanding of the subject area of ​​the Customer. By the way, the question “what do you like about competitors’ products ”works well? :)

Successes!