[geomcentral]

How does this work in a Scrum context?

I want to get stuff done but I need to raise a ticket, have the priority agreed, and get it planned into a sprint. Then after these layers of 'asking for yes' I am allowed to work on something without scrutiny. Let's say I wasn't subject to this process, my pull request would still need someone to approve it.

Is there a way I can adopt the approach of 'asking for no' with these constraints? Or does it only apply in high autonomy workplaces?

[mooreds]

I don't see how this works in the context of scrum as I've seen it done, except in the weak case of you getting to raise the ticket of whatever topic you'd like.

I guess you could ask for no around specific implementation details too? So if you are working on ticket XYZ that could be solved in N ways, you could pick one that might be a bit out of the norm (but still solves the problem) and 'ask for no'.