> Executives who interpret "Story Points" as "how much time is that going to take"
aside, but I have yet to meet a single person (dev, qa, pm, exec) who doesn't do this.
back
1 comments
so nobody understands why we use "story points" instead of time estimates? I feel like some people do appreciate that its not about the number of points but the quantitive difference between the items up for work.
In my experience the vast majority has completely abandoned the idea of story points or team velocity, they are just an (unnecessary) proxy value for time estimates. And god forbid you suggest something like planning poker to make the estimates somewhat accurate.