• o_d [he/him]@lemmygrad.ml
      link
      fedilink
      arrow-up
      15
      arrow-down
      1
      ·
      1 year ago

      The problem is that only 1 organization that I’ve worked for has actually tried to implement it correctly. The rest just say “yeah we do Agile SCRUM” but it becomes obvious quite quickly that no they do not. Just because we throw stories on a Jira board every 2 weeks and move them around does not make it SCRUM. I suspect this is partially the reason that some people have a negative view of it. They’ve only done “SCRUMfall” and assume that’s all it really is.

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

        Almost everything in Scrum can be seen as protecting the team.

        ONE example (there are many):

        Problem: vague requirements

        Solutions in Scrum:

        • Acceptance criteria on stories need to be clear
        • whole team grooms the story, everyone understands it and does planning poker to agree on costs. If the team doesn’t all understand it, it doesn’t get past this point
        • only fully groomed stories get into a Sprint and get worked on.
        • EVEN IF YOU GOT IT WRONG, you demo what you did every sprint, and the stakeholders can ask for additional work in a future story, reducing the cost of getting it wrong once.
        • TrustingZebra@lemmy.one
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Almost everything in Scrum can be seen as protecting the team.

          Funny, in ny team it’s the opposite. Our team leader is protecting us from the Scrum BS that is forced on us by upper management.