• fer0n@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    I get your point and maybe there’s a better alternative to scrum that keeps the culture and structure intact.

    I might be wrong here, but as I see it scrum is fixing problems by changing the team structure itself. If that structure is really the main issue, you can’t not make that structure change, call it scrum when it actually has nothing to do with it, and then blame your inability to adapt on the methodology you’re not using. Because there are teams that are able to adapt and use scrum successfully.

    • space_comrade [he/him]@hexbear.net
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I don’t think you can truly change anything with these methodologies. At the end of the day most companies are still privately owned companies, and you as a developer will do what the owners and/or the managers tell you to do. The owners aren’t going to delegate important decisions to developers unless it’s a really technical thing. The part where “developers take control” in scrum is bullshit and always will be by necessity of how our economic system works.

      I feel like Scrum and similar stuff just serves to obfuscate real material relations in the company that aren’t going to change no matter how many story points you assign to this or that or how many scrum masters you have. Also it makes micromanagement easier I guess.

      • fer0n@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Developers don’t take control in scrum. They are empowered to work autonomously, which is a big difference. Devs provide the complexity of stories and the PO decides in what order the team is tackling them.

        Scrum doesn’t mean everyone just does whatever they feel like.

        • space_comrade [he/him]@hexbear.net
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          They are empowered to work autonomously, which is a big difference.

          That means nothing to me. Just platitudes. I’ve never felt “empowered to work autonomously” in scrum.

          • fer0n@lemm.ee
            link
            fedilink
            arrow-up
            0
            ·
            1 year ago

            They decide how to implement it themselves is what I mean by that, the user story doesn’t give technical implementation details and it doesn’t give a specific solution. It gives you the problem and reason

      • fer0n@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        If you haven’t already, I’d encourage you to take a look and read the book. At the very least it’s some interesting stories being told.

        • space_comrade [he/him]@hexbear.net
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          1 year ago

          I don’t read such books because they’re almost always written by “consultant” grifters trying to make money off of proselytizing the latest bullshit corporate fad. And it’s almost never based on actual data or a coherent theory, just gut feelings and a few anecdotes. My own felt experience and that of my colleagues is enough to confirm that it’s all just corporate ideology bullshit.

          • CloverSi@lemmy.comfysnug.space
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 year ago

            You’ve never read the book in question… Because you think it’s filled with gut feelings and anecdotes… Which you know, because of gut feelings and anecdotes…