Live data from Hacker News

Scrum Sucks

blog.mb-consulting.dev

21–30 of 298 posts

Re: Scrum Sucks

#21
While some of the points in this post are valid most of this is just copy-paste non-sense stated in multiple articles. Of course "Scrum" cannot fix your problems if you have bad engineers who are happy to just "close" tickets or you have an organization where you do not know where to ask "who is knowledable about this business requirement". Scrum is a software delivery methodology which is ok in itself, it is not a silver bullet which will enable you to write great software which meets specification and runs for years without bugs, those things are completely tangential and require a specific set of skills.

Re: Scrum Sucks

#23
I believe that the most valuable aspect of Scrum is the retrospectives. These are recurring meetings where we assess what has been effective and what hasn’t. If the retrospectives consistently focus on the same issues, such as ongoing complaints about test environments, this also indicates a fundamental flaw in the overall architecture.

Re: Scrum Sucks

#24

  Take the retrospective seriously,   as a moment to reflect with a   clear mind, over what turned out   to be a good strategy, how to   iterate on that and praise the   team for the job done.
I suspect you can probably predict how effective a scrum style team is based on how effective the retrospective is.

Re: Scrum Sucks

#25
Bullshit clickbait is bullshit clickbait.

Scrum doesn't inherently suck. Scrum can work if you do it right. It won't if you don't.

Just leaving it up to the individual team leads to the same result. If the team sucks at managing their work, the team will suck at managing their work. It doesn't matter what you follow if you suck at it.

This isn't as catchy and feel-good as the bullshit clickbait that reinforces what you want to believe (that the process is the problem, not you or your team). But it's accurate.

Re: Scrum Sucks

#27
The things I've taken from scrum and use at every team:

- plan in 2 week chunks

- estimate in points (relative size to something you've already done), emphasis on consistent estimates for each dev.

- make sure you define what 'done' means, and make sure it relates to what exactly you are trying to measure (Eg just coding effort, work till feature can ship?, etc). This is probably the most tricky bit.

- capture total velocity every 2 weeks and eventually use the avg for future planning

- review the entire process and modify things that take a lot of time for devs.

Re: Scrum Sucks

#28

Scrum is a decent framework for teaching business stakeholders how to work in an agile fashion, and to force some developers to always have releasable software. But at a certain point people get so attached to the process (or teaching process) that they get scared to take the training wheels off. So yes, Scrum sucks.

[deleted]

Re: Scrum Sucks

#30
I wonder how much of the suckiness is because of scrum, or because of the company that's adopting scrum's existing culture.

I'm not defending some of the ridiculousness of these ceremonies etc. but they're really a symptom of the problem.

Post reply on HN