Recently our team has decided to give points to the chores. They had an argument that:
- Velocity defines team's capacity to deliver the work and if chores are not counted in velocity it won't reflect the true capacity of the team. As teams pick chores as per the business priorities/urgency i.e. in some sprint 1 or 2, in other up to 5 chores so, they feel the more chores they have the lesser would be velocity/capacity of the team in that sprint which might not be true.
- They feel chores also add value to the product i.e. if we have some duplicate logic and we plan to remove it as a chore. In long run, it would help us deliver and test things faster and hence, it delivers value indirectly to the user.
What could be downside of this approach?