• mvirts@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 days ago

      Taking on too much work in a sprint for sure. In my perfect world all sprint tasks get done early, but I always find myself taking on too much.

      • Alexstarfire@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 days ago

        We usually start out small and add in more work once we finish that. It’s a lot easier that way. I’d say maybe half to 2/3rd of what we finish is what we planned to begin with.

        I will say that if management doesn’t listen to timelines then there’s not gonna be much you can do to prevent stress.

  • EnderMB@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 days ago

    If your sprints never stop…they’re not sprints. The clue is in the name.

    Velocity should be manageable, and it’s understandable to see some highs and lows. The problem with many of these points reflects that modern software engineering (like many corporate careers) is pushing for more efficiency than is sustainable in the long term.

  • badcommandorfilename@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    5 days ago

    I don’t explicitly disagree with any of the points, but I think that the mini deadlines at least lead to a successful outcome rather than a failed project.

    The example is steering a ship or driving a car - you need to look at the map or the road at regular intervals (even if they are “false deadlines”) to make sure you’re on track.

    I’m on the highway, there’s no corner coming up for ages so I don’t need to look at the road for a few minutes – dead person

    Scrum/Agile gets a lot of negative press these days, but I haven’t seen a practical alternative yet. Enlighten me if you know of the perfect project management system 🙂‍↕️ - I’d genuinely like to figure something out.