I'm currently reading the very readable Microsoft Secrets by Michael A. Cusumano and Richard W Selby (1998).
I’ve been reading how they "buffer" their projects in a critical-chain-like way. You can read the appropriate parts of the book by following the links on this page which lists the pages with the word "buffer" on them using amazons "search inside" feature. [you may have to login to amazon after the first click].
I especially like their project management principles at the bottom of page 64 because they combines elements of critical chain [principle 2] and agile thinking [principles 2, 3, 4, 5]:
1. Let people do their own schedules
2. Build in buffer time for the unseen delays that always occur
3. Assume change will happen so don't waste time trying to write complete specifications upfront.
4. Manage by milestones, starting with the most difficult things first
5. Focus on customer problems, not technologies or processes
6. Move people around, to mix the good and bad.
