In this month's post Jasmin Wilkins interviews Michael Sahota on Agile leadership and high performance organisations; Fiona Blunsdon explores using the three Scrum questions for your life; Carl Weller looks at managing bugs, Agile development hills and the CEO's role in execution; and Rowan Bunning presents on 'how your culture is shaping your Agile'.
Managing uncertainty and complexity is on most business and IT people's minds as we navigate a world that is rapidly changing and is increasingly unpredictable. This month our consultants share resources and learning on the value of cross-functional and self-organising teams for dealing with complexity, amongst other topics.
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 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: