Product Owner: "How many more people is it going to take to fix the road?"
Dev Team: "Well, there's a ticket in the backlog to put out the underground fire. It's been in the backlog for five years, and it's a blocker for this "Fix Road" ticket.
Product Owner: "...so, can we fix the road first and then go back and put out the fire a little bit at a time as capacity allows over the next few sprints?"
Standups are a short (hopefully) meeting usually done in a software development environment that tells the team what everyone was and is working on amd what issues are blocking them (i.e., blockers)
Look at you with your company willing to pay for scrum leaders. Many companies like to tout "we're agile" while just slapping some sprints around a waterfall process
This is one reason why standups are traditionally supposed to be done standing up. People have less tolerance for getting sidetracked when they're standing.
Independent Contributor shows up, chainsaws through the tree, then hucks the easily lifted parts onto the shoulder. Then offers some kurt but important advice:
"Like this next time."
Sometimes, it takes an expert to train people in the moment.
And the next FTE who inherits the job has to spend months picking up all of the logs that were chucked to the side of the road. Maintaining an enterprise level project means thinking months ahead. Yes, you can quickly chop down a tree and huck it aside. But what does that mean next month when you need to build another road where you hucked all of the logs?