How about I kick it off?
Our setup was originally VSS (no really, but like, an eon ago) so naturally we transitioned to TFS and TFVC.
Our current deployment stack makes use of MSBuild, PowerShell and Sitecore Packages.
This allows us to manage, not just Sitecore content and code, but Azure infrastructure at the same time.
We are currently on the market for some new tooling: winning this race at the moment is TFS-hosted Git, Unicorn, TeamCity, Octopus Deploy, Azure Resource Templates and Desired State Configuration (which is, of course, PowerShell fundamentally). The TFS-hosted Git is probably the most contentious item there, and may end up being BitBucket or the like.
The original stack was designed for simplicity - minimum tooling footprint and minimum infrastructure requirements for clients.
The new tooling is designed to improve throughput, deliver feature branching and feature toggles more easily, and make the delivery of packages to INT and UAT more robust. From UAT the process will become manually triggered, but will still operate through automation, giving customers a chance to take pause and signoff in UAT, and allowing us to accumulate changes for delivery into production, so as to not disrupt the live environments too often.
Azure Resource Templates and DSC allow us to automate the provisioning of our Blue/Green environment for production releases. Not just new code, new hardware! New everything!