No, nothing of the sorts.
As part of the team we all know, usually, the details of the projects we are working on, details that we cannot expect a manager to follow or know for each project, because there are a lot of details and many projects. A lot of them overlap in discovery, development, execution and deployment and also have different priorities.
And it is my understanding that managers also need to prioritize given sudden issues, emergency requests, and so on.
Anyways, with that info, we can decide who is the best fit for it given the experience they have had or not with specific projects.
Also it is usually not that hard.
You don’t get a backup 2 days before your time off, indeed, more often than not, it is asked with a lot of anticipation.
Also, most of the time when you go on time off, you are encouraged to have all of your projects deliverables ready for when you are out.
That way, your teammates doing the backup are just checking in on the project and available for general questions.
Personally, I like to leave documentation as well for my backups so they know what to expect. It’s not strange to have changes that imply more work for the backup so the extra context helps a lot.
frayedpickles@lemmy.cafe 1 week ago
I would default to assuming that this is a professional job, so making sure you’re covered in case something goes wrong is expected and also reasonable to expect from coworkers. If there’s conflicts (I don’t think I can support this while you’re gone because I’m gonna be tall busy with x), you go to your manager and ask them to figure it out. But by default, it’s likely you know who is best equipped to support because they are already working with you.