The scheme of working with freelancers + scrum. brainstorm

Question

Agile

Now we are working according to the following scheme:
1. A list of desired functionality is compiled
2. It is transferred to the Scrum Master.
3. The first item in the list is refined until we reach the tasks that can be dealt with in 3 days without any problems.
4. The Scrum Master composes sprints and distributes them among freelancers.
5. Code review is held on Thursday evening. Together with the code, the reviewer submits a report on the work done in hours and comments on the quality of the code of each participant in the sprint. If the customer is not satisfied with one of the sprinters, then we settle accounts with him and look for a new candidate for the next sprint. This is Friday.
6. All items completed in full are crossed out, all clarifications and alterations are entered at the top of the list of the next Scrum.
7. And on Monday GOTO 3

Advantages:
1. Process is formalized
2. Highest possible quality control
3. Good horizontal scalability
4. Low side costs

Disadvantages:
1. Takes a lot of time to formalize
2. Tie to hourly pay
3. Can only implement loosely coupled sprints
4. Nightly reviews
5. Small sprint size (3 days)

What I want to hear from you:
1. How can this be improved?
2. Philosophical reasoning on the topic
3. Examples from personal experience.

Answer 1

You should describe what exactly you are developing, without this it is difficult to give advice. It's scary to think what could come out of this scheme for more or less complex projects, but obviously you have some kind of specific task for which the code in the form of a patchwork quilt is suitable.

Answer 2

Perhaps Kanban is more suitable for your processes ?

Answer 3

You have a very interesting process! Since I am a scrummaster myself, I will ask a couple of questions, if you will:

3. The first item in the list is refined until we reach the tasks that can be dealt with in 3 days without any problems.

Who specifies? Scrum master? Does he program himself?
And I didn’t quite understand about “until we get to the tasks ...” And if you get there, what happens? Why exactly 3 days

4. The Scrum Master composes sprints and distributes them among freelancers.

What does "sprinting and distributing" mean? Usually, one sprint and all tasks are washed down from it.
Is the code reviewed by a designated freelancer? Or a customer?
Review once a week? Not too much to review in one day?
What kind of participants do you have in the project and on what sides of the barricades are they located? As I understand it, you have freelancers - they work remotely, there is SM - this is the one directly between the customer / PO, and the PO itself. Is there anyone else on your mediation part?
In general, very interesting, I just can not get the full picture yet. But I really like that everything is on rails.

Answer 4

Generally speaking, it is considered good practice to review no more than a certain number of lines at a time, so it is better, IMHO, not to wait for Thursday, but to review tasks as they come in, although in your case this is problematic if you are trying to save time.
True, by the way, it’s not clear to me if you have a review once a week, how do you check whether your comments have been fixed.
I also understood that in the phrase “Scrum Master composes sprints” they mean User Stories, based on the phrase: “Usually sprints are distributed according to the principle “if the sprinter has already done this””. So?