Can you please activate your webcams?

Please choose a sticky note color to use for this meeting

Please take one of these smiley stickers and tell the others how you feel now

  • jj4211@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    That’s about your team and/or your teams leadership, not scrum.

    While true, that cuts both ways, a successful team is not successful because of ‘scrum’, it’s successful because it finds a methodology that works for them, which can be in terms of scrum, but even if no one was chanting Agile buzzwords, that team would still self organize in a similar way, just without the precise buzzwords.

    What’s obnoxious is that a lot of folks, with a vested interest in, say, consulting, will give credit to “Agile” for teams succeeding and then simultaneously call all failures that ostensibly use Agile but fail “not true Agile”. It can be harmless enough when self-organizing, but then it doesn’t really matter if it is “big-A Agile” or not. People hung up on the “big-A Agile” may be expecting to cash in with consultancy money, or use it as a club to assert their authority by their self-proclaimed alignment to ‘Agile’. They are advocating for Agile, therefore if you challenge anything about their direction, they will invoke the magic Agile word to silence criticism about their methods. Once an organization has “acheived Agile”, ironically they frequently close the door on any consideration of methodology reform. “We are running Agile now, whatever you may think we are doing wrong the industry agrees with us because the industry uses Agile, so stop complaining”.

    So Agile may be technically workable, but the frustration is that it is vague enough to allow anyone to do almost anything and still ‘fairly’ claim Agile, but as a brand word it confers unreasonable authority for certain folks. As the most prominent brand word in the world of project management, it is further correlated with the ‘default’ asserted methodology of any crappy group looking toward consultancy/self-help to fix their bad team situation with a bandaid of methodology.

    • Critical Silence@feddit.deOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      They are advocating for agile, therefore if you challenge anything about their direction, they will invoke the magic Agile word to silence criticism about their methods.

      It should be seen as a method that can be adjusted to the team, but this attitude blocks adjustments and improvements even before they start. Its even worse, people will just do anything “Scrum” tells them and reflecting, especially learning from the previous lessons, gets silently lost since the impression overcomes, that it is not allowed. From management side this is fully approved, I mean these people are expensive Scrum Masters, so they know what they do.

      As you mentioned the team is the source of success, not the method itself. The “Don’t” stated previously is on point there:

      You’re bending your team/process to fit agile, and not bending agile to fit your team/process

      • jj4211@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        You’re bending your team/process to fit agile, and not bending agile to fit your team/process

        Yeah, this one is tricky.

        If a methodology is supposed to help, but you don’t change your processes in any way, then it seems odd to assert that you are “adopting” a methodology.

        In fact, I would say that the typical dysfunctional Agile shop basically “bends agile” to fit their process, meaning they undertake a superficial exercise to map a problematic process to Agile terms and declare victory. Sometimes taking the time to actually make the process worse in a way they wanted to, under the smoke screen of “Agile transition”. For example, in my company customers are generally using our projects together, so we had basically a set cadence of release dates. All projects were only allowed to target designated release days (March 1st, June 1st, etc.) A project, if it made sense could skip a release window, but the projects wouldn’t just release 2 weeks differently than all the related projects. Project owners declared this “not Agile” and said everyone just release whenever, much to the complaints to customers that now have a barrage of updates that are in no way synced up, with QA that tried to use the projects as the customer would abolished, so until the customer there’s no one using the “current” editions of the projects together in one place. Agile is perfectly happy with a prescribed cadence (in fact I would say usually I hear the mantra that you try to fit your work to the schedule, rather than letting the work mess up the schedule), but development managers didn’t like the way the release schedule tied their hands so they blamed Agile for a really bad quality move.

        I’m all about processes that fit your team, I just think fixation on Agile branding does more harm than good.

    • MajorHavoc@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Good points.

      One of my measures of an agile team is simply asking if they’re agile.

      I’ve never had an agile team say “yes, we’re agile”.

      Best answer I’ve had was. “we do these standard agile things, we cheat in these ways that work for us, and we’re currently adopting this process that we think we’ll help”.

      Worst answer was “Yes. We’re all SCRUM certified.”