What effective project development methods do you use?

Question

Time Management

Faced with the problem of effective project development, I would like to know who, what and how is used for the most efficient application development. I work solo, several projects at the same time, but I understand that the time for their development is significantly blurred and everything could be done much faster.
Interested in perhaps some methodologies of this type as Scrum, but for one developer. :-)
Or what action plan do you draw up and what tasks are divided into. It's just that with each new project there is a hope that everything will be done on time and in most cases - the deadline burns out and it turns out to be a mess.

Answer 1

This is apparently due to the fact that a new project is starting to be done while the old one is being finalized. Keep this in mind and just add time to the new project. Plus, take the time to design the TK, at least just for yourself. If the project has to create things that have not been encountered before, it is better to first find out what these things are and how much time they will have to spend on them. It is still impossible to accurately calculate the end date of the work.

Answer 2

1. Development of a new project. At this stage, the tasks necessary to start the project in work are discussed. At the output, a list of tasks divided into groups with an estimate of the execution time for each. Over time, I came to the option of dividing into subprojects:
1.1. Layout of the main template with site pages. The CMS is deployed, the template and the main pages of the site are implemented without dynamics, the implementation of modules with the usual html statics. The goal is to demonstrate cross-browser compatibility, design elements.
1.2. Implementation of the client side. Here the main functionality of the site is implemented, the implementation of the logic of modules, the creation of database tables, html static modules are replaced by dynamics.
1.3. Implementation of the admin part.
2. Product support. Fixing bugs, periodically discussing new tasks with the client, their subsequent evaluation and planning. At the output of the task with an estimate by time and date of implementation.