How does a team successfully move from an internally-hosted centralized version control system to Git running in Visual Studio Team Services? Hear how one group of developers did this by taking along the people, adapting their processes, embracing the technology, in a culture open to change.
• How did we transition the team and learn the new tools and processes?
• What did the team do to maintain version history after the change?
• Do you have to be "all-in" on VSTS? Actually, no. Learn how we integrated our other development systems with VSTS
• Why did we want to move, and have we realised those benefits?
• Where to next? Are we satisfied with what we've achieved, or are there new goals to aim for?
David has been creating software for over 25 years. He has a passion for continual learning and improving quality, and enjoys being in and creating environments where these happen. A Microsoft MVP (Development Technologies), he run the Adelaide .NET User Group.
By day, he works as a Senior Developer at SixPivot. In his spare time he contributes to numerous open source projects (including some of his own), and is a package moderator at Chocolatey.org