Release Management in a fast paced environment requires skills of people management. Every one's change "Has to go now", "Has client/customer impact" etc., etc. How does manage the wants and needs of all and keep all happy? One has to first determine how to evaluate real emergencies that need to go immediately versus those that need to follow the schedule and go during the change window.
The Release Manager first must learn the complete system and how the parts interact with each other. This way they can see the possible places where additional coordination is needed when projects and prod support are release code on the same cycle. You cannot allow a prod Support branch release and the trunk release to go out in the same cycle. they must merge early and test the heck out of the code prior to release.
You have to learn to ask the hard questions of the managers pushing their team's changes in. What will happen if this change is scheduled for the weekly window versus tonight? If coordination has not been done who gets delayed? How do you smooth out ruffled feathers? Ask the question "What will be the cost of releasing this code this week without all the integration testing completed if the customer finds a bug tomorrow?". Escalate the issues up the chain in case there is any push back and let the senior leadership make informed decisions. You have to do it in a way that no one take it personally.
This is some of the Art of Release Management.
