This short article provides an approach to adapt the Scrum concept of velocity to traditional project teams that are working without using the sprints/iterations of Agile project frameworks. In Scrum, velocity is how much product backlog effort a team can handle in one sprint.
This can be estimated by viewing previous sprints, assuming the team composition and sprint duration are kept constant. The approach proposed in this article use the concepts of Task Value Time and Delivered Value Time. This is used to produce some XVelocity measures that could show interesting aspects like: how much business process and technology the team knows, when you compare the Delivery with the Estimation, or how much the team knows about itself if you compare the Delivery with the Commitment.