3 ms·
> Hiding behind processes like scrum will not save you. Even in the best case scenarios, enterprise shops and startups are faking progress by breaking user stor
by emodendroket 5y ago
> Hiding behind processes like scrum will not save you. Even in the best case scenarios, enterprise shops and startups are faking progress by breaking user stories into tiny little pieces or simply working stories over many sprints "are we there yet?", dragging out timelines for simple work to obscure the fact that the teams are lost, the business people are clueless, and developers are disinterested
This seems to be its own rebuttal. If no process can save a bad workplace, why is killing off Scrum going to make things better?
- lumost 5y agoAt the very least it would show that the team is willing to change. I work with one team that is absolutely convinced that work shouldn't be planned more than 2 weeks in advance. They have had a goal to produce a product for the last 2 years that there is practically zero progress towards.
- alkonaut 5y agoBut scrum doesn’t say “don’t make plans” it says “be prepared to change plans”. You can (and should) still keep long term roadmaps, track progress towards long term goals and so on. A situation like the one you describe is one where you’d prescribe a methodology, be it scrum or something else, because the team seems to lack one.
- chrisseaton 5y agoBecause, as they say, Scrum is used to mask the lack of progress, and so the underlying problem is not addressed. If you took away the curtain people would be forced to confront what's behind it.
- wk_end 5y agoIf a troubled workplace’s response to its troubles is, “might as well do something, who cares if it works”, that’d at least help explain why it’s troubled.
- emodendroket 5y agoThat seems like a better plan than “let’s do nothing.”