DEV Community

Discussion on: Story Points and Time

 
elorz007 profile image
mikel.sh

You misunderstood what I said. I said comparative estimation has been proven to be more effective than absolute estimation. I didn't say that scrum/agile has been proven anything and I don't claim such thing. Whatever works for your team is good, call it whatever. In my opinion, Scrum/Agile provides some guidelines and some empirically tested tools/resources to deal with common issues that developer teams face and it's one of the best starting points known so far.

And I agree that "you have been doing it wrong" is a common response. But is not a way to dismiss criticism, it is an attempt to say that anything that you apply incorrectly will lead to wrong results and by the looks of your comment you/your company applied or understood agile in the wrong way. Thus, you should be criticising your specific way of applying those rules not the whole methodology. Or you could criticise the way that many companies dogmatically apply scrum, of course.

I also have an academic background in software engineering (which means nothing, by the way, it is an authority fallacy) and I also think there is tons of bullshit, I completely agree with you here.

Also, yes, Scrum might be one of those "hype cycles", so what? It means people trying new stuff and techniques, trying to improve themselves and their processes? Seems to me like a good thing to happen.

Finally, what I criticised was your attitude of "I know it better than the rest, I would do it my way not caring about what others do/want". Not only I would not criticise people who "speak up" and give their opinion against our processes, I would love if they did. It would give us great opportunities to improve ourselves. And I constantly try to avoid having an environment where people are not "in position to call out their PMs".