|
|
|
|
|
by JohnFen
1021 days ago
|
|
> like "Scrum Master" who (IMO) feel pressured to create as much process as possible to justify their position Having been trained and acted as a scrum master for a large tech corporation, this doesn't track with my experience at all. I, and the other "scrum masters" (which is an incredibly cringe term) I knew tried to minimize process as much as possible, and weren't concerned with finding busywork to "justify out position" -- especially because our positions were primarily devs. Being a scrum master was extra work on top of our daily duties. In my opinion, the problems with Scrum are because of how Scrum works and what management wants to use scrum for. Being a scrum master was what convinced me that Scrum in particular is extremely problematic and that if you must use an Agile methodology, it should be one of the other ones, not Scrum. |
|
And maybe, a really solid big-tech company with great people who "get it" can largely make Scrum work "well enough". I'm sure you oversaw a lot of products shipping successfully.
Was that because of Scrum, or in spite of it and you might have been even more successful doing something else?
Overall though, I think you recognize how Scrum might devolve in many typical situation, right?
PS: To make it clear, no disparagement is intended in anything I said or say even though the consequences of that might seem like an attack on your profession.