Sprints, user stories, definitions of done, daily stand-ups, backlog grooming, sprint planning, retrospectives, burn-down charts, pair programming, technical spikes, continuous integration, test driven development, specification by example, refactoring…
We regularly receive enquiries from people looking to attend our Certified ScrumMaster (CSM) courses, which are delivered by our Certified Scrum Trainer Rowan Bunning from Scrum WithStyle. Sometimes the questions are from people with little or no project, product or Agile experience. If you are in this situation, then in this post we will help you understanding whether Certified ScrumMaster training is right for you.
In my blog post Changing columns on a VSTS sprint board I was asked the following question in the comments:
"I added my custom states to my Task work item and they're showing up on the sprint board, but the Active and Resolved columns are also showing, even though I hid the Active state in the workflow. Is there something else I need to do to hide the Active and Resolved columns on the sprint board?"
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: