I don't enjoy it either, to me even though some principles are quite different, it seems like a series of mini waterfalls.
The other thing is that it seemed to remove any creativity of control from the developers. In some cases this is a good thing because developers get stuck in ruts and heads way in the sand. But small tweaks improvements that only show themselves to be available when you get into the code, can't' be done. They'll be put in the backlog, and generally never lifted to the top. And if you put them in, then it 'adds risk to the sprint'.
Ultimately it feels like it removes a lot of fun from the role of developing. Granted a lot of the above stem from the company and not necessarily the process.
Re:Is Kanban the New Scrum?
by willvarfar on Thursday July 05, 2012 @05:18PM
(#4205017)
I feel that way too http://williamedwardscoder.tumblr.com/post/20054342100/agile...
Still, the feeling of being limited in freedom is the greatest annoyance to me and perhaps the fact that there's little room inside sprints for emergencies (at least this was how SCRUM was implemented in the last company I worked at). I really appreciate flexibility in ordering and the execution of tasks and SCRUM didn't grant me this ability.
I wonder if people around here feel the same ...