3 ms·
I've always had a problem with the scrum concept of team velocity i.e. assigning story points to tasks and then measuring how many story points a team delivers
by asaph 8y ago
I've always had a problem with the scrum concept of team velocity i.e. assigning story points to tasks and then measuring how many story points a team delivers each sprint. The idea that this yeilds any predictive power is flawed. It's based on the assumption that the team is static. As soon as someone leaves the team or someone new joins, all the historical velocity data becomes useless and you need to recalibrate. The reality is that teams are dynamic. They grow/shrink/change all the time.
- himynameisdom 8y agoThis is up to the team to help other people understand that velocity/productivity is more than likely decrease as team dynamics change. Even if more people are put on a product, the velocity is expected to decrease as those people absorb new responsibilities. Same story for losing people on a product.
- AnimalMuppet 8y agoSure, the team is dynamic. Smart agile people expect that changing the team will change the achievable velocity. Clueless "agile" people proceed as if nothing had changed. But that's not really an agile problem. You can have a waterfall-ish schedule, then the team changes, and management wants to keep the original dates. It's the same problem.