How to draw up a technical task for the development of a service?

A

Adam Stebalsky2016-06-07 05:27:02

PHP

Adam Stebalsky, 2016-06-07 05:27:02

Hello!
The task is to draw up a technical task for a backend developer.
How to compose it correctly? Which points should be described in more detail, and which should not? What does a PHP programmer want to see ideally?

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

V

Vladimir Borutkin, 2016-06-07
@Atanvar

Business processes and functional scenarios should be described

A

Andrey, 2016-06-07
@AndreyMyagkov

In addition, it is necessary to describe the criteria for the delivery of the project, i.e. the service must be able to do something, on such and such a platform, for such and such time, with such and such a load.

A

anton achehe, 2016-06-07
@mr-achehe

Planned traffic

V

VekaVeka, 2016-06-23
@VekaVeka

Judging by your statement of the question - personally for your case, you need to explain in simple human language what you want to get as a result.
And the developer you work with must be experienced. He will translate your Wishlist into his technical language.
If you had experience, the system would be different: it would be necessary to set tasks very specifically and the developer could be less qualified.
An important point:
Do not take it for granted that something is usually done, etc.: the developer can interpret unspecified questions as he wants at his discretion. If you don’t have an hourly pay, but a fixed one, then of course, he will make unspecified questions according to the simplest option, with which you will then get a lot of problems.