A calendar wouldn’t work, because (a) when something urgent comes up everything else needs to be shuffled down by a few hours, (b)it’s overkill for a job that largely consists of (1)take work off of board (2) do work (3) get next work item off board. (The fun bit is doing those work items, of course.)
As for “What would happen if some of them didn’t happen” - security scans wouldn’t be completed, so we wouldn’t be allowed to implement, features wouldn’t be added, so customers would be unhappy, documentation wouldn’t be written, so things would be done wrong. I don’t do any of these things for no good reason - they’re all carefully thought about, estimated, and planned in to each two-week iteration, and if something isn’t worth doing, we don’t plan it in in the first place!
(Obviously sometimes the facts change, and so we need to change priorities, dump things from the iteration, etc. But that doesn’t stop us from having the plan in the first place.)
EDIT: As I can’t add further replies to this topic, I’m editing this comment instead:
It’s not death. But it’s important for my job and for the service we provide to our customers.
Customers have functionality they want. We have a queue of work items that they have asked for,specced out. This is my to-do list.
You seem to be saying that I shouldn’t keep track of those work items, the order they want them in, etc. but should instead come in in the morning and make a vague stab at what they might like yet. This seems bafflingly odd to me. I can’t help but feel that I am badly misunderstanding something, because I cannot understand why keeping track of the list of things that customers have asked for, and the numerous tasks necessary to move that code into production, is a worse approach than just doing whatever seems important off the top of my head each morning.