If you have created a process intended to demonstrate how busy you are, you’re doing it wrong.
If you have created a process in order to justify why you’re going to say “no” to a request, you’re doing it wrong.
If you have created a process that benefits you, but no one else on your team, you’re doing it wrong.
If you can’t measure how much more effective your process has made your team, compared to not using your process, you’re doing it wrong.
A good process helps everyone do their job more effectively, in a shorter period of time than otherwise not using the steps required by its methodology. A great process does this, and is invisible to the constituencies that it serves.
So, if you design a work methodology that coerces people to adhere to a process that you know is meant to separate them from you, is meant to show how busy you are, or that is crafted solely for you to point at a chart on the wall and say “it’s not in this sprint”, you’re absolutely doing it wrong.
End of serving-the-methodology-rather-than-the-customer rant.