News for hackers. Stuff that matters.
Re:The Failure of Agile by eropple on Wednesday May 13, 2015 @11:42AM (#9539775)
Scrum has the particularly noxious side effect of driving underground any sort of drive to improve and to learn new things. An engineer in a Scrum team is an engineer, has his or her lane, and is largely expected to stay in it. Learning? Branching out? No, get your promised tickets done this week. That concerns me; while it's possible for a Scrum-based shop to invest in its people, it's not part of Scrum to really do so. And the people are what matter, at the end of the day, so I find it rather dehumanizing.

(This is a big part of why I'm moving towards consulting--so I can invest in me more often.)

Re:The Failure of Agile by EdwardDiego on Thursday May 14, 2015 @02:01AM (#9543658)
We use Scrum and I disagree with everything you said. It is not reflected in my experiences at all.

But that's the problem of arguing from anecdote.

Re:The Failure of Agile by wnevets on Wednesday May 13, 2015 @12:45PM (#9540203)
why is this "Scrum" specific? Sounds like working a 9-5 at most companies regardless of their development process.
Re:The Failure of Agile by dragonwriter on Wednesday May 13, 2015 @12:50PM (#9540228)
> why is this "Scrum" specific?

Scrum's pre-committed units of work across the team promotes this; its one of the reasons that many groups prefer flow-based methods (which can support regularly-timed releases simply by shipping the features that are ready at the time of the release cutoff) rather than Scrum's cycle-based method.

Re:The Failure of Agile by jasonwocky on Wednesday May 13, 2015 @01:59PM (#9540749)
I don't see how this is true. If you're building slack into your cycle there should be regular investment time available that a pure flow-based system wouldn't have.

If there's no slack in your sprint schedule, well there's your problem.

Re:The Failure of Agile by eropple on Wednesday May 13, 2015 @04:21PM (#9541689)
In my experience, Scrum's work-unit factorization encourages thinking of developers as spherical cows that need no personal development, with slack as a concession to reality that patches the damage Scrum itself causes. And Slack is generally considered to be for technical investment, though, not personal investment.

A good manager could think past that, for sure, but I've never encountered a good manager that felt Scrum was good or necessary for their teams.

Re:The Failure of Agile by s73v3r on Wednesday May 13, 2015 @05:30PM (#9542104)
"If you're building slack into your cycle"

Then management comes over and asks why you're slacking off.