Transformation im Lifescience-Umfeld ist eine Kette von Änderungsprozessen.

Trotzdem wirken viele Change-Abfolgen strategisch zufällig. Inhalte sind sauber dokumentiert - aber das Zielbild fehlt.

Gerade bei GxP-relevanten Systemen ist das riskant.

Planst Du Deine Transformation vom Endzustand her?

#LifescienceIT #ChangeControl #DigitaleTransformation
https://youtube.com/shorts/uLo4eHJHASs

@avuko

Ah, but he is ' a new special hire ' kinda type without a paycheck which garners future scrutiny! Perhaps his boss is just setting him up for fail / flail, as is the R culture. 🤔

For eXample, using 19-25yr olds without a bit of gov experience to do your bidding literally, without a single person with gov IT experience in their midst, smells really⁴ bad like a setup. 💯

Just the regulations alone not being followed because ' ignorance of the regulations ' doesn't give you a pass, you know, a lá Nixon Quote

" ✌️ (Totally) ... A Crook ✌️"

Keeping the argument simpler though ...

✌️ #ChangeControl🤝#GovIT🤝#Paperwork✌️

😂😭

I.T.'s gonna be interesting when #infosec comes by and rips this server out though for forensic analysis. 😂✌️

I'm going to disagree with the somewhat clickbaity headline here.

Change Control Boards do work, if you know how to run them well. These statistics simply show that a lot of organizations ... don't know how to do that.

Also, it's not an either-or, and pitting CCBs against other valuable risk mitigation techniques helps nobody.

#softwareengineering #risk #riskmanagement #changecontrol #qa #quality #reliability
http://highscalability.com/blog/2023/8/16/the-swedbank-outage-shows-that-change-controls-dont-work.html

(Note: This is now a public thread) @static @milohax @brunoph asked 'I wonder if the bodies doing the upgrade were just following instructions' - they 100% should have been. That's what change control is. The experienced guys write the change control document, other experienced guys look over it to see what was missed, and then hand it off to the ops team to actually do it.

The problem would have been that either no-one thought to add an 'abort if this doesn't complete the upgrade' OR, someone overruled the abort, thinking 'maybe if we upgrade everything else, that'll fix the issues with the first one.

If it's the former, it's a learning experience for the senior networking team. If it's the latter, well, that could be a career ending move for the person who thought they knew better than the change document.

#changecontrol