0:00

[MUSIC]

Â In this lesson,

Â we are going to learn about an important concept in agile planning called velocity.

Â To learn about velocity, let's take an example.

Â Let's say, you are in a new country and you are on a road trip

Â from point A to point B which is about 300 miles apart and

Â I ask you how long will it take you to go from point A to point B?

Â You may answer like I don't know what kind of roads are going to be.

Â What kind of traffic it is.

Â So come back after and hour or two, and

Â I'll tell you how long it's going to take me.

Â So after you have driven for awhile,

Â let's say in the first hour you covered 50 miles.

Â And in the next hour, you covered 45 miles.

Â So if I come after two hours and I ask you,

Â how long do you think now it'll take you to reach to point B?

Â You may say, well, it's 40, 50, 45.

Â Approximately, I'll say, 50.

Â Ad so, it'll take me and I have driven for two hours.

Â So I think it's going to take me another four hours.

Â So, my velocity is approximately 50 and I have another 200 miles to go.

Â So, it's about four more hours.

Â Similar concept is used in agile planning.

Â So, velocity is amount of work that a team.

Â So, it's about team.

Â A team is getting in a sprint.

Â And then again, then it depends on the team or the project.

Â For example, in your case, the road matters, the traffic matters or

Â the people who are in your car matters.

Â So if you have kids, you might take more breaks.

Â And if you are just single, then you might just go faster and

Â you don't did as many breaks.

Â So again, it depends on a lot of factors.

Â But whatever is the team velocity is what we use.

Â So, how do we calculate velocity?

Â So to calculate the velocity for a sprint that you just finish, let's say,

Â you just finish the sprint and you want to calculate the velocity for that sprint.

Â You basically take all the stories that you finished.

Â Let's say, you finished three stories with estimate of five, three and ten and

Â you add them together.

Â So in this case, it's going to be the velocity for

Â that sprint is going to be 18.

Â Now, velocity is also used for predicting or

Â selecting stories for an upcoming sprint.

Â So let's say, you just finished as you can see in the table here,

Â the sprint 21 to 27 and their velocity.

Â So let's say, you are about to start the sprint number 28 and

Â you want to know what velocity you should use to pick the number of story for

Â a sprint 28, then there are several ways you can do.

Â The first one very simple.

Â You may say, well, I'm just going to use the velocity of the last sprint always.

Â So if I'm doing a sprint 28, I'll just use the sprint, the velocity for sprint 27.

Â So in this case, if I use that technique, I'll just use the velocity of sprint

Â 27 which is 23 and that's what I'll use for sprint 28 for planning.

Â The another concept you can use is average of last x sprints.

Â So in this case, if I use the last three sprints,

Â then the predicted velocity or the velocity that I will use for

Â planning in sprint 28 will be the average of sprint 25, 26 and 27.

Â So the velocity for sprint 25 is 25, 26 is 27 and then for sprint 27 is 23.

Â So I add them together and take an average, it comes out to be 25.

Â So for sprint 28, I will take stories worth 25 points.

Â The third style of calculating velocity is the velocity range.

Â So in which, you calculate the minimum and

Â the maximum velocity for the last x sprints.

Â So in this case, if I was using the last three sprints,

Â then to calculate the velocity range for spring 28, I will be using spring 25,

Â 26 and 27 and the minimum is 23 and the maximum is 27.

Â So, I will be using the minimum is 23 and 27.

Â So, the range is going to be 23 to 27.

Â Now if you look at sprint 23, you see the velocity of 54.

Â That sounds like anomaly.

Â So unless it was pretty natural, they must have something special or

Â something has happened.

Â But in this case, you would escape that velocity.

Â So in case I was using the last five, if my method was to use the last

Â five sprint for calculation, I would skip sprint 23.

Â Now, there are several situations that you will encounter as you will use velocity.

Â So, let's take some of those situations that you in which you may have to adjust

Â your velocity or not.

Â 5:01

So what if you are just starting a new leads and new project, and new sprint?

Â You don't have any history of your sprint.

Â So, what will you do in this case?

Â Well, what you can do is you can take few sample stories from your backlog and

Â the team can get together and just say,

Â pick stories that we think we can get done in a sprint.

Â The team may want to task it out like talk about it.

Â Task it out how to do those stories, so they have a better idea.

Â But in a nutshell,

Â they want to pick a few stories that they think they can do in a sprint.

Â And then just the total or sum them up, sum up all the estimates and

Â that becomes your starting velocity to plan for the sprint.

Â Another situation or situations you may encounter is more people are joining your

Â next sprint or somebody new joined, or few people are leaving the team,

Â or people are going on vacation.

Â So, how do you handle these situations?

Â Should you add just your velocity for that?

Â Well, the point is to continue to use the velocity of previous first sprint,

Â except in the case where most of the team is going.

Â So for example, in case of holidays when most of the team is out,

Â then you may want to register it.

Â But in most cases, it averages out.

Â So you don't need to do any adjustment, especially for these specific situations.

Â Because let's say, a new team member joins.

Â Then they're going to take some time to get used to and

Â sometimes in the beginning, although they may contribute.

Â But they would also take some time away from people who are going to explain them

Â or get them up to speed.

Â So, and you don't know the new team member.

Â What is the impact on the team velocity he or she would have?

Â So that's why it's best to just continue to use the velocity from the previous

Â experience, then another situation you may encounter, what if the estimate were off.

Â So you were working on a story that estimated to be tree, but

Â actually took you four or more.

Â So, should you adjust these velocity for the estimator or should you just estimate?

Â Well, generally it averages out.

Â So the recommendation is no need to adjust the estimate for

Â those stories, but in case where you have the new learning.

Â So let's say, every screen, we learned a new stuff that hey, now,

Â going forward, we need to do both browser checking and

Â most of the screens are now going to take double the time or more time,

Â then all the stories related to this kind of work.

Â We should adjust their estimates.

Â In those cases, yes.

Â If there is a new learning and there's a bunch of stories that will be impacted

Â from it, you should go to your story backlog and update the estimates.

Â But other than that, the story, the velocity and

Â the averaging will take care of that.

Â So, that's all about velocity.

Â