We all knew it

    • wewbull@feddit.uk
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      A lot of places seem to view it as “we just work from the backlog” with no requirements on when features are delivered, or their impacts on other parts of the project.

      You still need a plan, goals and a timeline. Not just a bucket of stuff to get done.

    • ture@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      And also because it’s a comfortable cover up for any kind of money saving stupidity. We don’t need proper requirements engineering, we’re agile. We don’t need an operations team we’re doing an agile DevOps approach. We don’t need frontend Devs, we’re an agile team you all need to be full stack. I have often seen agility as an excuse to push more works towards the devs who aren’t trained to do any of those tasks.

      Also common problem is that still tons of people believe agile means unplanned. This definitely also contributes to projects failing that are just agile by name.

        • RamblingPanda@lemmynsfw.com
          link
          fedilink
          English
          arrow-up
          0
          ·
          5 months ago

          Especially the last part. Writing a single word into a jira ticket doesn’t make it a story, epic or sub task. You’re too lazy to specify, that’s not what agile is meant to be.

          • magic_lobster_party@kbin.run
            link
            fedilink
            arrow-up
            0
            ·
            5 months ago

            I don’t know how many times I have been waiting for the product manager to get out of their meeting so they can help me clarify what they really mean with their “high priority” ticket only consisting a vague title.