SoylentNews is people
SoylentNews
Ah, it has finally happened: the first publication that has declared that Scrum is dead. Apparently, the over-paid consultants have relieved the under-clued bosses of all the money they can, so it's time for the next fad.
Scrum works, of course. Just about any software development methodology works, as long as you have good people working in a disciplined team. If you have a lousy team, adopting the latest fad isn't going to help you.
Iterative development is an old technique. I knew of it as far back as the 1980's, but writing this submission, I see that it has roots much farther back. In software, all the way back to the 1950s. In product development generally, it goes back at least to the 1930's, when Walter Shewhard proposed short "plan, do, study, act" cycles for product improvement.
So: let's take bets. What will the next fad be? TFA says it will be the "open development method". What do Soylentils think the consultants will be selling our bosses in five years?
(Score: 1) by nitehawk214 on Wednesday November 18 2015, @04:16PM
I can't agree with this more. I worked for a big company that has been waterfall (at best, but more like Big Ball of Mud [laputan.org]) for years. New owners come in, shake up management, declare we are all going to do SCUM now! (is it SCRUM or scrum? what does SCRUM stand for?)
About half the employees get some training on it (my team wasn't on the list), and the best I can see is that some of those teams try to do a daily meeting instead of a weekly one. Ended up with a dozen people standing at the end of my row talking while I had my headphones on trying to ignore them. (quips of "get a room" were met with hostility)
My boss had like 20+ direct reports, so he had no idea what any of his employees were doing. And anytime we tried to sit down and talk as a team it took 2 hours, so we didn't even meet monthly. It would take so long we would never get our jobs done. I made sure to never speak up in meetings, lest I cause hundreds of dollars of damage to the company by wasting 10 minutes of 20 people. Result, nothing changed except terminology. Senior management did not care as long as we pretended we were scrum and got our jobs done.
The dozen people in that daily scrum meeting quit doing it after a while when half of them were remote employees and its really hard to have a quick 15 minute meeting when so many of them were on the phone.
My current job does a thing we call scrum, in so much that we usually meet 4 times a week and talk about stuff for 10-30 minutes. Even though we use git and bitbucket, scrum is useful for doing group code reviews on big pushes, or designing new components. Our team has 4 members (3 dev + 1 qa), and I would say 6 is the absolute most for a scrum, maybe less if they are all developers. "Scrum master" is simply the supervisor/dev lead, I know its not necessarily supposed to be a boss, but I can't see how it can work any other way.
"Don't you ever miss the days when you used to be nostalgic?" -Loiosh