Lets chat on your topic so that I can bring my outside view and ask.
I will think and discuss (confidentially) the topic with my peers.
Lets have a second chat on the topic to share thoughts and ideas.

You have already a document and need a second opinion?
I will have a look, assess the doc according 12 criteria and send a feedback.
We will do a secured, encrypted document exchange.

prioritize stakeholder requests
You have many stakeholders. All of them are important and have high priority requests. It becomes hard to prioritize the request just on a informal discussion. Use Value estimation principles to give them a numerical figure. Rationalize the arguments and bind them on a given budget.

Flow is more important than maximum speed. Agility is not a tool to maximize efficiency. Squeeze more out of an org, team or process is the old way to do it. Agility is to maximize the work not to do. By the way the resources where focused on the most valuable ones. With the resources allocated the maximum outcome is generated. A KPI suitable for that paradigm is not velocity. If we would use that, the team will drive the velocity KPI, but the generated outcome is still the same – because the outcome can no longer rise. An idea is to measure consistency of flow and predictability. This is valid for Scrum as well as for Kanban. The target is to minimize the variance.

The right team working model and a rationalized value estimation is useless if the contracts do not reflect the principles. Given contract papers enable your organization to implement the enterprise agile working model with economical principles.