What should a programmer do at the end of a sprint?

Question

Agile

There is a team of 4 programmers. A sprint is created for 2 weeks. Each programmer has their own tasks. When the sprint comes to an end, programmers who have completed their tasks faster than others take on their colleagues' unfinished tasks. But what to do when there are only 2 tasks left for the sprint, and we have 4 programmers. Two programmers cannot work on the same task because they will interfere with each other. As a result, we have two programmers working, but what about the other two? New Scrum tasks cannot be added to a sprint until it is closed.

Answer 1

Write tests, turn on monitoring, system alert, turn up ci \ cd - in general, deal with technical debt.

Answer 2

For example, there is pair programming .
And let them throw stones at me, but Scrum is not a panacea, but only a convention. In addition to pluses, it also has minuses. You can't live by a plan.

Answer 3

If you have true agile, then there are probably goodies like a gym membership, etc., so go

Answer 4

Tests
Refactoring
Test refactoring

Answer 5

watch memes vkontakte

Answer 6

Take a task from the backlog and get down to business...

Answer 7

If this is not the first time this has happened, then you have the wrong sprint size or backlog size. It seems to me that it’s better to take it with a spare - the total volume completed per sprint is more important, and not 100% completion of all tasks.

Answer 8

Scrum does not prohibit adding tasks to a sprint. Scrum forbids changing the sprint in such a way that the sprint goal becomes unattainable (and "complete all tasks in the sprint" is not such a goal). If the sprint goal becomes irrelevant, the sprint stops and a new one is formed, with its own goal. If the sprint goal is not achieved by the end of the sprint, the sprint is considered a failure, the reasons for the failure are analyzed in retrospect, and the team decides what it needs to change in its work to reduce the risks of repeating this.