1/8/2024 0 Comments Defect process in agileStory points and velocity were designed in a way to be fine tuned for accuracy in short time increments and as a result, velocity cannot be compared across different teams and it cannot even be used to compare the performance of the same team over different time periods because the very meaning of a story point shifts for the team through time. This is usually more than enough fidelity to get a sense of how much work the team can accomplish in the present iteration. Now we ask how many tasks can we do in this iteration and very likely that number will be similar to the number of tasks that was completed in the last iteration or perhaps even the one before that. If every task is a small, manageable piece of work that can be done in less than four hours then we don’t have to assign story points to tasks because everything is a small. I know that some work doesn’t lend itself to be done in small chunks but in most situations I’ve been able to find ways of breaking down tasks into small chunks and I find that it’s very valuable when I do this. Rather than spend time teaching teams about story points and velocity, I much rather show teams how to break features down into small homogeneous tasks that can be achieved in less than four hours. I hate velocity because I’ve seen it misdirect managers and team members far more often than I’ve seen it provide valuable information. One of the things that you’re not going to find in this seven blog posts series on measuring the software development process is measuring velocity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |