How to organize the process of constant improvement of the company's websites?

Question

Project management

Our IT department in a non-IT company maintains something like 20 sites and a large self-written CRM. Resources are in working condition, but are constantly being redesigned, both from scratch and simply with the refinement of existing functionality. In addition, there are many minor improvements at the level of content management: remove the link there, pictures there, etc.
About the team: IT department of 4 people (3 with knowledge of layout and with grief in half programming and one programmer). I am one of the layout designers with the function of manager and admin. In addition, there are outsourcers who connect when we can't cope. And an internet marketer.
There is only the head of the company directly, who is almost always available and himself forms most of the requirements for projects.
Question:in what methodology to look to organize the process?
The development itself is not in-line, i.e. there is no conveyor of finished products, the existing one is being constantly refined. Do it once and never forget. Requirements change often, of course. There are no clear roles in the team, because the team is small and there is a lot of work.

Answer 1

In your case, it will be good to combine support and Kanban. The process in this case may look like this:
1. Through support, customers leave requests, where they describe what they need.
2. The manager sorts these requests, clarifies them (adds the necessary information) and can somehow classify, for example, Site or Infrastructure or something else. The manager can evaluate the complexity of applications on a scale of X, L, M, S.
3. Team members, as far as possible, take for themselves those tasks that suit them in terms of class and complexity. Perform work and drag the card to the "Done" state.
4. The manager accepts the completed work and marks the application as completed, or rejects it for completion / alteration. The customer receives a letter stating that his application has been completed, and then he looks, rejects or accepts its decision.
There is a minimum of interaction in this process, everything is visible on the Kanban board. You can see where the plug is, who is sitting picking his nose, etc. As a tool in which such a process can be organized, I can advise devopsboard.ru

Answer 2

I must say right away that I am not an expert in this field, but I am facing similar problems now.
What I can advise: each person should mind their own business. If you are a manager and admin, then only deal with these tasks. Instead of 3 unfortunate typesetters, it is enough to take one normal one and keep one from outsourcing in reserve (you never know what).
I don’t really understand what level your projects are, but I think that you should set up your work through git plus read about project management in general (there are many services where you can create a team, give each task and track the whole thing).

Answer 3

1) Store development in git or another top-control system.
2) Write tasks in gitlab, for example, there you can distribute tasks to someone specific, and set the "weight" of the task, and indicate the time in milestones, and at the same time, a fairly simple tool.
3) As written above, 1 (!) Person is responsible for setting the tasks, preferably able to clearly define the task and break it into stages if necessary. If someone wants to set a task - through him, otherwise it will rush f * pa over bumps - whoever is in what much.
4) Control! Checking tasks every 2-3 days, or more often, distribution of pendels / goodies. Some arrange a social competition with pennants and stars out of this, personally it annoys me more than motivates / pleases, but here everyone decides for himself.

Answer 4

JIRA will save you
all sorts of CI - you are unlikely to master, but learn to systematize

Answer 5

Also https://rovertask.com/ will help. Here you can work by priorities, keep track of tasks (in-line or chaotic), keep all correspondence and delimit the work of each area of ​​work (marketing, layout, programming) in separate chat rooms. Such a task messenger for a small team.