Shane Ross introduced Daniel Scott-Raynsford of IAG New Zealand at our client event a couple of weeks ago, and in the process he provided some context on why we approached IAG to speak. Many examples of successful DevOps, Agile and Cloud adoption focus on start-up and high-growth companies who are able to bake in these approaches from the start, unencumbered by legacy technology, strict regulatory controls and deep-rooted structures and ways of working.
In New Zealand the scale of most solutions, and the dev teams working on them, are tiny compared to global software companies. Yet many developers, architects and CxOs I work with, want to do things 'because Netflix does it' – especially when it comes to MicroServices.
This article is republished from my original Setting up a new VSTS project post on fantail.io.
Visual Studio Team Services (VSTS) is an Application Lifecycle Management tool - it handles the whole lifecycle of software development from idea to requirements, planning, development, code reviews, build and release. It is designed to support your team no matter what methodologies or languages you use. While most users pay for a license or use their MSDN subscriptions to log in, Microsoft make VSTS freely available for teams of up to 5 users. I am going to use my free account to plan and develop a new project, and share some tips along the way.