393
The Great Software Quality Collapse: How We Normalized Catastrophe (techtrenches.substack.com)
submitted 1 year ago by to c/technology@lemmy.world
134 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 15 points 1 year ago (3 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 5 points 1 year ago (2 children)

    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)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 1 year ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year 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

  • permalink
  • fedilink
  • source
  • parent