Sprint planning and task flow, how to combine?

Question

Agile

Here the analyst is just an example, it could be a developer, a tester, and anyone else

A sprint is planned. Analysts are asked:
- How long will it take you to complete this task?
- About five days.
- And this one?
- Another five.
- Hooray! We have scheduled a sprint.

The sprint has started. And then an interesting thing begins:
- Analyst, help us here urgently, our neighbors cannot cope with the tasks, solve at least one problem for them.
- Analyst, I urgently need to puzzle our junior developers, urgently give them analytics for a couple of tasks on the project that are not difficult.
- Analyst, remember, you made a project three years ago, we want to finalize it, tomorrow we will set up a meeting for you from 15:00 to 18:00, tell you how best we can improve.
and so on....

Question: From the point of view of SCRUM, how is it right? -
1. The analyst should say: "Go far, I have a plan for streaming, streaming according to plan - I won't take a step aside."? But what about team collaboration then?
2. The analyst asks to limit the plan, because he gave the terms in man-days, and not in absolute hours. But the question is - why is this planning at all, and why is it evaluated in days (at least if the sprint is 2 weeks, then we estimate what can be done in two weeks), if it comes in half an hour and requires revision. And then he comes back?
3. Does the analyst grit his teeth and work at night and burn out?
4. The PO must somehow take into account and limit the activity outside the sprint - also a question about cooperation, and in general does it have such opportunities - take into account what it does not know yet? And in general, is there such a practice - to lay in a sprint, let's say 8 hours for non-sprint affairs, if exceeded, send?
5. Other

Answer 1

First, what is not in the sprint is not done. Secondly, the question "for how long will you do this task" does not mean how long it will be ready, but how many hours to do it. There are exactly 40 hours in the working week, if you want other tasks, choose which planned ones to subtract from, that is, what will not be done in this sprint.

Answer 2

Here you need to immediately figure out how many hours a day you have productive work, in addition to answering calls / messages, all sorts of reviews, meetings, coffee and other things. And already evaluate tasks based on this time.
If they ask for something big to do, ask for a task and say "we'll plan for the next sprint." If it is "urgently burning" then write to PM (or whoever needs it) that "a task has been drawn, they are asked to complete it, will we change it in the sprint to something else?". And it’s not a sin to say “I didn’t have time to complete a task from my sprint, because I took an urgent task, so my task will go to the next sprint”, but it’s better to warn your PM in advance.

- Analyst, help here urgently, our neighbors can't cope with the tasks, solve at least one problem for them.

The neighbors have their own PM, let them ask your PM through it. In most cases, after the conversation, it turns out that the task is not so urgent, it will wait until the next sprint.

Answer 3

set a buffer for the sprint in the number of n hours for force majeure

Answer 4

From the point of view of SCRUM, it is not necessary to ask the analyst for how much he will complete the tasks. Planning in Scrum is completely different. Read the Scrum Guide carefully. If something is not clear, ask in the profile communities on facebook, telegram.