How to plan the deadlines in scrum development methodology?

Question

Task Management

The situation is as follows, when developing the project functionality, improvements to the developed functionality are identified that need to be put into operation as soon as possible, but in the near future everything is busy with planned work on other projects (usually 1-2 months in advance), so there is an overlap of work on each other and respectively, the delay, but here the plus is that the client knows the deadline for completing the task. I see a scheme in which planning takes place for 1-2 weeks from the pool of accumulated tasks, respectively, the additional ones that have arisen. work can be planned in the next 1-2 weeks, and everything seems to be fine. But what about planning? after all, as a rule, the client of the developed functionality wants to immediately know the implementation period, because if the task does not fall into 1-2 week planning, it is in uncertainty in terms of time.

Answer 1

a) If the amount of rework has little fluctuation: Based on the available statistics, calculate the average resource spent on rework. Allocate it for this purpose and do not include it in the planning of other projects. At the same time, if no improvements are required in some period, this resource will still be connected to help in other projects.
b) If the amount of improvements has strong fluctuations

• If there is only one customer for these projects , coordinate with him the priorities for improvement / new functionality and move the planned dates.
  
• If the customers are different - in projects where improvements are expected, do not violate the scrum recommendations. Those. move iteratively, including new features and improvements in each sprint in accordance with their priorities in the backlog.