Weaknesses of agile and Scrum

Comments

• mspencer712@programming.dev ⁨1⁩ ⁨year⁩ ago

  Do you keep a shopping list? A personal to-do or reminders list? You should stop because that’s a ritual and rituals are clearly bad.

  I mean, no, you should keep the rituals that help you work better and discard the rest. Which is what successful agile teams are already doing.

  source

  • btaf45@lemmy.world ⁨1⁩ ⁨year⁩ ago

    you should keep the rituals that help you work better and discard the rest.

    For those using Scrum, that means keep backlog list and discard everything else.

    source

    • TerrorBite@meow.social ⁨1⁩ ⁨year⁩ ago

      @btaf45 @mspencer712 The whole point of Scrum is to use the retrospective to stop doing what doesn't work and start doing what does.

      At one point, when my team's workload changed to less-timeboxable work, we threw out the entire concept of sprints and just used kanban instead, and stayed like that for a year. We still did retrospectives on the old sprint cadence though.

      source

      • -> View More Comments
• darq@kbin.social ⁨1⁩ ⁨year⁩ ago

  I have my complaints about Agile, but a bit different from this list. Teams I've worked in have generally tried to spec in quality control measures into story points, to prevent some of the issues mentioned, for example.

  My issue is almost always just that the top half of the organisation does not, and will never, conceptualise a software project like agile demands. Business will always want X scope within Y time. And Agile demands that at least one of those to be variable. The backlog represents scope organised by time. Want X features complete? Check the backlog to see when they'll be done. Want to deliver after Y time? Check the backlog to see what features will likely be ready by that time.

  But business will not accept that. They have scope requirements and deadlines to deliver within.

  source
• MajorHavoc@lemmy.world ⁨1⁩ ⁨year⁩ ago

  This is perfect.

  I’m going to save this and refer to it, along with the half arsed agile manifesto.

  source
• fubo@lemmy.world ⁨1⁩ ⁨year⁩ ago

  The more ritual and incense-waving you wrap around your work, the more likely it is that someone is going to spend all their time on ritual and incense-waving and none on actually creating value.

  source

  • DmMacniel@feddit.de ⁨1⁩ ⁨year⁩ ago

    Are you questioning the Omnissiah!? The Machine God will not favour your next build!

    source

    • ck_@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

      My thoughts exactly 😂

      source
• dallen@programming.dev ⁨1⁩ ⁨year⁩ ago

  Kinda comes across as someone complaining about how their company implemented agile. The only thing I can relate to is long sprints around the holidays, which I don’t see as an issue.

  I’ve only worked for 20-30 person companies so maybe it’s a corpo thing? The post reads like a list of red flags that would have me looking for a new job pronto.

  Seems to be more a problem of shitty management than agile vs waterfall.

  source
• 0x0@programming.dev ⁨1⁩ ⁨year⁩ ago

  Seems to me you’ve had issues with how people (mis)implement agile in your company, which is a common problem. Managers can’t get their heads out of their waterfall ass. Agile’s not to blame though, i’ve worked in teams where it was a breeze to work in scrum and quite helpful, so don’t blame the tool.

  Put a chimpanzee behind the wheel of a Ferrari and you’ll still have problems.

  source