• ozymandias117@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    24 hours ago

    We’ll just set up another retrospective meeting and have a lessons learned.

    Then we won’t change anything based off the findings of the retro and lessons learned.

    • PattyMcB@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      22 hours ago

      Post-mortems always seemed like a waste of time to me, because nobody ever went back and read that particular confluence page (especially me executives who made the same mistake again)

      • shalafi@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        22 hours ago

        Post mortems are for, “Remember when we saw something similar before? What happened and how did we handle it?”

        • monsieur_hackerman@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 hours ago

          They should also include the recommended steps to take to prevent the issue again, which would allow you to investigate why the changes you made (you were allowed to make the changes, right? Manglement let you make the changes?) didn’t prevent the issue