Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Scrum is a cancer

twitter.com

Post reply on HN
Print view View original

261–270 of 486 posts

Re: Scrum is a cancer

#262

Post by dorinlazar »

SCRUM solves a problem the X poster is too young to know. I'm mildly amused, he has no idea what SCRUM is about and why the ceremony is a lot better than the sleepless nights and the crunch time spent rewriting the application in the last month before release.

Pepperidge Farm remembers!

Re: Scrum is a cancer

#263

Post by Yhippa »

berniedurfee wrote: post #258

Lol, I was on a team that was required to stand during standups, even though we all sat together and could just swivel our chairs around. One dev flat out refused to stand. I can still see the pulsing vein on the neck of the project manager who so wanted to scream ‘You will stand during the standup dammit!’

The reason I have heard about this is that standing is fatiguing and discourages people from going on and on. I get it but I think it's strange.

Re: Scrum is a cancer

#264

Post by yesbut »

rightbyte wrote: post #206
yesbut wrote: post #188

Earlier quoted context omitted.

Problems aren't resolved unless people shine a light on the problems.

Sure, but "Stop going along to get along" is how all these agile processes spread in the first place. Opponents were ridiculed and bullied by proponents for being boring, old, unmodern, not team players, not using best practice or whatever. And way too many programmers were actual believers for grumpy safeguards to be able to keep things in check. I think a cooperative approach might be better to get rid of agile or…

I think it's just best to call out BS when it pops up. That would have put a stop to this before it ruined everything. Cooperation is good, but people need to be told they are wrong. It's ok to be wrong. Everyone makes mistakes.

Re: Scrum is a cancer

#265

Post by rai_guy »

xedrac wrote: post #147
tasubotadas wrote: post #93

Earlier quoted context omitted.

The guys here come to the scrum retrospectives, stay silent the entire time, and then complain that scrum sucks.

I've spoken up in many retrospectives, but when nothing changes, it's hard to take them seriously. What's the point of a retrospective if your feedback is simply discarded?

[flagged]

Re: Scrum is a cancer

#266

Post by some_guy_in_ca »

marcus_holmes wrote: post #116
zug_zug wrote: post #13

Interesting phenomenon happens at my place which is scrum + Safe. Our team gets publicly dinged if we "carry over" tickets between sprints, so if we finish our work with 2 days left the manager asks not to start anything new. The process is a performance within a performance, literally getting told NOT to do more work. This is what happens when you have chart-oriented-development (particularly jira's toxic charts). Y…

This. I moved from being the Main Tech Guy at a startup to being a backend engineer at a mature company running Scrum. I was amazed by how little work anyone did at the mature company. People obviously doing f-all during the day. If we finished our sprint 3 days early then we just pretended to be working (what is the point in having a standup every day when there are no tickets to work on?). It was painful. I constan…

As a consultant with 25 years of experience in enterprise software for sizable corporations and universities, I have observed numerous development shops. The number of individuals in corporate America who accomplish little throughout the day is astonishing. This phenomenon aligns with the Pareto principle, wherein 20% of the workforce completes approximately 99% of the tasks and the rest are dead weight.
Post reply on HN