Why don't you fix the problem, round 2

As a business, you want to get the most out of your developers, and it makes sense that you want them to work as quickly as they can. Some feel that in order to make your devs work quickly, you have to schedule more aggressively. However, it's pretty unlikely that thats why your developers aren't building as quickly as they could be.

In order to achieve rapid development, you must plan for it, and scheduling more aggressively may actually get in the way, because your developers must write code so quickly that little consideration is given to code reuse. As such, developers will end up solving old problems in new ways. Reinventing the wheel, over and over again, is very time consuming.

Hopefully your developers are voicing concerns about this kind of thing. If they're not, take it as a warning sign; you may have a floor composed entirely of immature devs.

On the other hand, if your developers are spending too much time on administrative tasks it might be wise to see if any of that responsibility can be pushed onto other people.

Put succinctly, you should ensure that the obstacles your developers are dealt with. Closing your eyes and trusting them to deal with it is runs completely counter to the concept of Rapid Development.