Comment on Weaknesses of agile and Scrum

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

• 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

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

      I jokingly suggested a similar crusade against sprints, because the nature of my team’s work isn’t prohibitively time-boxed either.

      Wasn’t expecting the people sitting on that zoom call with the power and influence to make such a change to actually agree

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

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

      That is only something useful if you can use the retrospective to through out Scrum. Otherwise it is yet another Scrum timewaster.

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

      One of my project managers once described scrum as agile with training wheels. Which I think is a good description. It is useful for teams new to agile but once you get going you can start to throw out the parts that you don’t need or that don’t work for your team. But still useful to get you going initially.

      source

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

        @nous That's a good way of putting it!

        source