Because anything else is completely arbitrary. I mean, we ARE measuring things in "points", but with the understanding that 1 point ~ 1 hour of work.
> Why is management tracking the amount of story points every developer completes in a sprint?
Because they want metrics on productivity. I don't entirely blame them.
> Why are you not working on the highest prio stuff in the sprint?
As mentioned, because management really wanted to see us complete 40 hours of work every week, and getting close to 40 hours done per week was more important than priorities. If something couldn't be finished before the end of the sprint, they thought it was better to push it to the next sprint, rather than leave something incomplete at the end of a sprint.
> Of course sprints look useless if you're doing them like that. Do you even have a clear sprint goal you're working towards?
I was on a QA team writing test code. I specifically was writing security tests, while others wrote functionality or stability tests. Each sprint goal was effectively just "Write these tests".
Because anything else is completely arbitrary. I mean, we ARE measuring things in "points", but with the understanding that 1 point ~ 1 hour of work.
> Why is management tracking the amount of story points every developer completes in a sprint?
Because they want metrics on productivity. I don't entirely blame them.
> Why are you not working on the highest prio stuff in the sprint?
As mentioned, because management really wanted to see us complete 40 hours of work every week, and getting close to 40 hours done per week was more important than priorities. If something couldn't be finished before the end of the sprint, they thought it was better to push it to the next sprint, rather than leave something incomplete at the end of a sprint.
> Of course sprints look useless if you're doing them like that. Do you even have a clear sprint goal you're working towards?
I was on a QA team writing test code. I specifically was writing security tests, while others wrote functionality or stability tests. Each sprint goal was effectively just "Write these tests".