I think it’s important to make those requests as minimal as possible. If we have a well oiled system of Jira tickets, estimates, and expectations for each sprin

I think it’s important to make those requests as minimal as possible. If we have a well oiled system of Jira tickets, estimates, and expectations for each sprint, these one off requests fly under the radar and impede engineer performance and expectations You could have a percent of each sprint dedicated to one-offs, but then are they really one-offs in the colloquial sense? The smaller the team and org, the easier it is to handle the one-offs (imo), because we can more directly connect the request to tangible impact more often. At the very least, in a small co your manager (or C suite executive) would easily back you up as the engineer if other executives were questioning output or something etc etc In larger orgs the extra communication burden makes the one off requests more expensive