Ahhh, I have been waiting for this

Notify the resistance! We're moving in. THUD is making some noises that I don't like. We've been more or less left alone for a while. Now, after a week straight of meetings, management is starting to make noises about adding process, changing features, shipping product, etc. Unfortunately, people tend to be a little mealy-mouthed around here, so the MO when you try to nail someone down on an answer is to try to make it someone else's decision (preferable someone not in the room), thereby spreading the responsibility and blame. The correlary is that THUD has gone into CYA (cover your ass) mode and made some noises about changing back to the old way of doing things so we have a "predictable path" (old way being non or ad-hoc process, constantly shifting priorities, and trying to hide behind the spec - which never exists in a complete and current form - when things start to go to shit).

Delicate times. Despite approaching the end of a second sprint successful out of the gate, change is still feared. How to bring him in to the process more meaningfully (he's forever in meetings) , give him the illusion of driving micro control (he won't currently accept macro-level controls of setting priorities and trusting the team to make good decisions) without allowing him to fuck up the process. Suggestions?