How do you organize the process of creating websites and what are your main problems?

Question

Freelance

The question is addressed mostly to freelancers.
Describe in general, if it's not difficult for you, where you start the customer's project, how the work proceeds, your headaches and how you "optimized" these pitfalls. I personally gave part of the work to others (at the design stage), and then "finished" the main template for CMS. Everything suited everyone.

Answer 1

1. Discussion of technical specifications with the customer, prices, etc.
2. TK is divided into several parts.
3. If you work on time (payment for an hour of work), then the timer turns on during work.
4. It is not clear what "smuts" are. If there are problems with the order, then I ask Google or on the forums. But I don't give anything to anyone, as you do. So you won't gain experience.

Answer 2

When I was doing freelancing, I did the following:
1. Created a separate area for demonstrating future results on the server and shared access to the ***.***.com subdomain
2. Throw a bare CMS or Framework there, depending on what we agreed to develop on
3. I create a separate page at work.***.***.com. There, at the entrance, there is a simple autorizashka, and inside the page is divided vertically in half. In the first part, once a day I write out what was done and what can be checked, and the customer writes out comments there. On the second half, the initial requirements for the project from the customer are drawn up. So that the client always sees what he initially asked to do and when he once again decides to supplement / change the task, he does not balk at the topic of what he originally wanted.
On this page, a notifier works on posts, i.e. if I write that something has been done, then the client receives an SMS and an email - exactly the same if they leave me a comment.
4. When the project is ready, I receive payment and after that I pour the project to the client.
PS I liked Ivan's scheme with servers :) I took note.
Freelance, he is freelance in Africa, and there were projects both documented and "gray". In the first case, there were no problems, in the second it was necessary to play it safe.
I worked with grays according to two schemes. If the amount is large, then 50-100% advance payment (as agreed, it will turn out), the balance after showing the fully completed work. But if the amount is small, then he worked without an advance payment.
Sometimes there were projects on the customer's servers with VPN access - from the point of view of insurance, everything was quite difficult there. Because it was about large sums, then he made special scripts that killed the project if the 24-hour counter was not rewound. This is in case the customer decides to cheat and simply cut off access. Of course, such manipulations can be hacked at the administration level, but I have not come across such smart people :)

Answer 3

If the project is well paid, then I will gladly give some blocks to third-party (but trusted) developers / layout designers. The design is even more so - it should be done by the designer (hello everyone from the cap). If the project is cheap, it’s cheaper to do it yourself, the question is why take such)