Join Doug Rose for an in-depth discussion in this video Check your velocity in TFS, part of Agile Project Management: Comparing Agile Tools.
- [Instructor] Now that we've seen our cumulative flow diagram, and again, that's all the stories in the backlog in this little diagram and how many of them you've completed and how many of them are active. But now we're going to look at the team's velocity chart, so the team's velocity is the average number of user stories that they can complete, sort of, over time. If a team completes 14 user story points in one sprint and 15 user story points in another sprint and 16 user story points in the third sprint then their velocity will hover around 15, so it sort of evens out over time, and the longer your team works together the more stable their velocity.
So, again, I'm not in love with this kind of storyboard chart here because I think that it's a little too much. I mean we've only got three user stories in here, but once it gets to be dozens or hundreds this could be quickly overwhelming. I'm not a big fan of regulating the flow because I don't think that quite works with product backlogs, but this is a very good way to kind of create these diagrams. And so if I take using GPS to find likely matches, and this is one of the user stories that we're working on in our current sprint.
You can see because two out of the three tasks have been complete, and I'm going to move it over to active because it's in our current sprint, and you'll see there's a little bit of flow. A little bit of whoosh and then here we have our velocity diagram. Now we have five and 13 which gives us a team velocity of this first sprint of 18 user story points, and you'll see that the five and the 13 are broken down by user story points, so this was five user story points, and it's closed.
And this is 13 user story points, and it's still active, still being worked on because there's one task left, and you can see that in this little velocity diagram here. You've got your five here that's green. It's been completed, and your 13 that's sitting here on the top that is yet to be done. This can give you a pretty high level view of your team's velocity for this sprint. Now I don't know how valuable it is right now because we only have three user stories and we've only gone through one sprint, but over time as you get greater number of bars in this little bar chart it'll give you a better idea of how your team is doing in terms of sticking to their velocity.
In our next video we're going to wrap up TFS, and we're going to talk a little bit about some of the things that you should watch out for when using this program.
- Remembering agile values
- Evaluating different agile tools, including cloud-based options
- Creating a backlog with Excel
- Setting up sprints in JIRA
- Portfolio planning in VersionOne
- Creating tasks in Microsoft's Team Foundation Server
- Running reports with CA Agile Central
- Checking team analytics in CA Agile Central
- Deciding which tool fits your team