Scrum Sucks
21–30 of 298 posts
Re: Scrum Sucks
#22Re: Scrum Sucks
#23Re: 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
#25Scrum 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
#26Re: Scrum Sucks
#27- 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
#28Scrum 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.
Re: Scrum Sucks
#29Re: Scrum Sucks
#30I'm not defending some of the ridiculousness of these ceremonies etc. but they're really a symptom of the problem.