Meet The Man in the Black Shirt. Donovan Brown is a Principal Cloud Advocate Manager of the Methods and Practices Organization in DevRel at Microsoft. Before joining Microsoft, Donovan spent seven years as a Process Consultant and a Certified Scrum Master. Cloud Methods and Practices are his thing. Donovan has traveled the globe helping companies in the U.S., Canada, India, Germany, and the UK develop solutions using agile practices, Visual Studio, and Team Foundation Server in industries as broad as Communications, Health Care, Energy, and Financial Services. What else keeps the wheels spinning on The Man in The Black Shirt? Donovan's also an avid programmer, often finding ways to integrate software into his other hobbies and activities, one of which is Professional Air Hockey where he was ranked as high as 11 in the world.View the profile
About the talk
In this video we'll show you how Agile tools in Visual Studio Team Services (VSTS) can make planning your next project easier then ever. We'll go over features such as backlog management (Tasks, bugs, features, etc.), Kanban boards, powerful queries using our query language and delivery plans.
Hi, I'm Donovan Brown principal devops manager for Microsoft. I'm a firm believer that could be good at devops. You first have to be good at a job most Visual Studio team services and team Foundation server offer features that you need to manage your work from backlogs and boards to a powerful query language and delivery plans. Let's jump right into the product and let me show you how it works. Here I am on the landing page of my visual studio team Services account where list all my projects and I can actually just click on the work link here and it's going to take me to my product
backlog a product backlog is a prioritized list of all the items your team wants to accomplish in developing this piece of software and then simply click on ADD, when's the item has been added to my backlog I can simply drag and drop it to determine where it belongs on my backlog. I can double click on it and I can see more details. For example, I can apply a story point value. If you want to use this for velocity. I can control who this is assigned to on my particular team. I can go back in and
give it a description and acceptance criteria and even link other items to it and saving it puts all that stuff back inside of the STS for me. What's really nice and I can actually have backlogs at different levels. This one is currently at the story level. But if I go up to the feature, I have one there as well and I can go all the way up to an epic and when I'm at the higher level I can use this plus button here to actually see the how my entire project is made up of all the way down to the task level. If I go back down to my story level actually have some more features on this backlog
that I don't have on the other two, for example, I can turn on forecasting forecasting uses our velocity estimated in story points here on each item and our teams known velocity what you would get after working together for a while. And now the tool is help me determine which iterations I will be able to deliver these particular item if I agree with them, I guess if we take an item and drag and drop it to that particular duration to assign it to that iteration as you can see I can only do these first two items because I would need two more story points to be able to get all of them in
there. And this is the most that I can actually fit. So forecasting is a really cool tool to allow you to help plan what you believe that your team is going to be based on your historic velocity. Not only can I see the backlog at these levels. I can actually go down to the actual iteration itself. And when I do that I get to see some really cool stuff starting lineup. For example, I can start to see capacity play. On the left hand side as my team comes into these items and starts to break them down. We can actually give estimates on these particular items. For example, I want to save work
remaining is 3 and I can't even decide what type of activity is going to be. If this is going to be the pointment designer development enough capacity in each discipline a bad start to estimate my work so that my team doesn't overcome it to delivering something. I can see it by activity type. I can see it by which individual is currently assigned to and I have enough resources of each type in each person to get the work actually done so I can pass it can also be modified here on the capacity to have this allows me to Define all the team members in my team and identify what activity they
played on that particular team. And if there's more than one had on your team, you can actually add an additional activity and then give them a I see per day about particular activity. So I'm going to be doing spending some of my time on deployment and some of my time on development. If I need to have days off I can actually applied days off here as well to make sure I have an accurate record of what my team capable of anything to visual Sprint that only can you view this as a backlog. You can also view these as boards here at the Sprint Logo level. We're looking at a task board. This
shows me they were underneath that have to be accomplished for this to be complete or done my status. I can simply drag-and-drop if I'm done with it what I really like about this as well is that I can come here and quickly adjust the number of hours remaining. I might not complete this task in a day, but it's important for me to update how much work is remaining so that my burn down burn down correctly to me the developers wait till they're done a munition to make sure that we're going to deliver on a Sprinkle but this is very simple. I submitted an
hour left here. There's two hours left here. Am I burn down now is going to burn down correctly anywhere that you see this? Is an opportunity for you to customize what it is that you're viewing? I can customize out task. Look how bugs look and even have a user stories appear on my passport. I can determine which backlogs I want with levels. So if you don't use epic are features, you don't have to go that high how many days we actually work if you work 7 days a week he's going to just that and if I want to show up on my back after work, sometimes prefer that some teams do not and you can
customize that right here at a sport is great. But when you go to a higher level like a story or feature, you're more looking at a kanban board. This is where the overarching item is actually going to move across the board in progress. We have too much work in the act of State before anything else over there. We have to get something out of there and move it into the results to take in this make sure that you get stuff done. And you can adjust those with limited in your definition of done if you need to and just like before I simply drag-and-drop to update my
particular status thing. I like about the kanban board is the ability for me to quickly see how many tasks I can even mark them as complete right here on the kanban board. I can also see what your task have tests on them in this is going to find the acceptance criteria for this particular item. If your team is using get as your Source control directly from this board, you can actually create a new Branch for this particular piece of work. This is going to make an association as you can see them at the bottom between this branch in that particular work item. If you're like me you've created
more branches and you know what to do with a don't even remember why you created them, but when you create a branch from the kanban board that branch and that work on them are immediately Associated together, but it gets even better every commit to this Branch every CI bill that is triggered and every release that is deployed is automatically Associated to this work item. You're going to get into and traceable. Often simply creating a branch. So have any work on him tracking your Source control your building your release all in one product give you the unparalleled traceability from making
a very simple gesture like so here we've been able to look at our capacity planning. We've also been able to look at how we would set up our iterations that are Sprint and we just want to show you that getting started with is very simple inside of the visual studio team Services family places. I want to show you before we leave one of them is the query language what you have lots and lots of work items inside of your backlog can sometimes be difficult to find the one that you're interested in and thanks to our query language. You can come in here with this really nice. Wysiwyg
editor add new criteria and pinpoint the item that you're looking for and then you simply run the criteria and then you'll get back to results down here at the bottom and quickly find the item that you're looking for. There's also a were condoms tap here, which is focused for the individual who's viewing the screen. So now I'm not cluttered up with all the information of other people I get to see all the work at the currently assigned to me. So I know exactly what I can focus on now this I'm drilling into a specific project and I'm seeing the work that has a finding me at the product level.
But if we back all the way back up to where we were at the beginning when we came into this particular application in the landing page, I don't even have to choose a project. There's a new work item item here allowed me to all my work across all the projects inside of this particular Visual Studio team Services account. So regardless every using kanban agile scrum, you're going to be able to find the tool that you need inside of Visual Studio team services to manage your work and manager spreads before I go. I want to encourage you to visit doc. Microsoft.com to learn more about
Buy this talk
Access to all the recordings of the event
Buy this video
With ConferenceCast.tv, you get access to our library of the world's best conference talks.