Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I work at Webs and we also recently abandoned scrum for a more kanban approach. While all points in the article resonated with our company, the biggest problem we had was not delivering projects on time.

We focused too much on fitting as much work into a sprint as possible for maximized throughput. The problem with that, especially when you have alot of projects going on at the same time, is that alot of work was being burned across the board, but the needle for each individual projects didn't move forward fast enough and we ended up missing deadlines.

Another problem with scrum is that it turns creative developers into code monkeys, and this in turn lowers code quality. Developers are constantly worried about trying to meet deadlines for the next two weeks rather than taking the time to do things correctly. This ultimately creates technical debts and hurts the team in the end.

(also, if you're a manager and you use the developer points burned in order to rate performance and distribute bonus, then fuck you)



I very much agree with the last point. Objective evaluation of a developer is much more than burned down points.

I worked at Amazon and could see evidently that Scrum was turning good developers into mediocre ones. But not many raised a finger against it as Scrum was seen as the norm. And there was no scientific way to establish this fact.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: