Making IT succeed today involves much more than technology considerations. Modern ways of working rely on people working together in high performance teams, placing increasing emphasis on people having strong soft skills. So in this post, while we have consultants sharing technology learning on MicroServices, VSTS and Azure, we also have consultants sharing learning on cognitive bias and the human and organisational considerations for Agile adoption and transformation.
This article is republished from my original Automatically Logging PowerShell in to Azure post on fantail.io.
I've been working with Azure Resource Manager templates a lot lately, as an easy, repeatable way to create deployment environments for my code. ARM templates are a JSON description of a resource or grouping of resources and can be applied to create or update an environment. This means you can roll out a new environment quickly and easily - perfect for quickly setting up a Dev or Test system, and you know that if you use the same templates to configure Production you won't have any surprises, or "Well, it worked in Dev..." conversations.
The best thing about ARM templates for me is how easy it is to generate them. If you have a resource group, you can create a template by clicking on the Automation Script button:
This article is republished from my original Adding Personas To Work In VSTS post on fantail.io.
During the week I finished adding the requirements I started in my previous post. I found I needed a few more features - one about Security and one covering setting up the development projects and builds. I also discovered an extension for VSTS that will help me keep focused on the users while I work. VSTS has a marketplace where you can see all the extensions and install those you think are useful. The one I will install is Personas, by Agile Extensions.
This article is republished from my original Setting up Requirements in VSTS post on fantail.io.
Last week I started a new project with VSTS, setting up some Git repos for my code. Now it's time to set up some requirements and planning for the development. I chose to set up an Agile project last week, which is one of 3 default project types in VSTS. This affects a number of things, including the form the requirements take and the development process used. Agile is the most flexible, and is the one that I use most often. Requirements are added to a project as Work Items:
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.