Measuring Team & Individual velocity

Question

Hello Community,

In my project, I'm dealing with a few challenges. Below are the most notable one's -

1. Tracking Team's true velocity for a sprint

2. Tracking an individual team member's velocity

To describe the first challenge in a little more detailed, we have a lot of stories in our sprint which get spilled over the current to the following sprint, because either Dev is still in Progress or QC activity is still pending. As a result, how can I determine the true velocity that we delivered for a give sprint.

The second challenge is more of a residual challenge as a result of the first one. It's equally difficult to determine the velocity of an individual. I don't intend to micromanage my team but this data will help me understand more about how productive an individual is. Appreciate any helpful inputs.

Regards,

Raj

Rajasekhar Maddela · Answer

ok makes sense. Thanks.

Daniel Deng · Answer

Yes, dependency is another headache. We usually identify dependencies in Sprint planning and try to decouple dependencies as much as possible for the coming sprint. However, if you have to plan a story with dependencies into your sprint and finally that dependency blocked the story by the end of the sprint, you may split that story into 2 part

1. The work you have done for this story in this sprint. This one stays in the current sprint and will contribute to the velocity.

2. Remaining work of the story, which depends on external factors. This one should be moved to the next sprint or the backlog

Rajasekhar Maddela · Answer

Thanks Daniel, agreed.  However, what if the user stories have dependencies (say API) provided by other teams? I guess such kind of factors cannot be brought under our purview.