"it does have a twist towards the end where the team self-organized to follow a process that worked for them and made them better aligned towards the Agile Principles: Scrum."

Yes, because it is published in the Scrum propaganda mill - "Serious Scrum".

" many scrum teams working on complex software systems trying to fit in their testing cycles in two week scrum cycles."

Yes, because they are preoccupied with Scrum ceremonies, instead of their build/test pipelines.

"Our team decided to invest in Quality Assurance practices starting with Static Code Analysis, Healthy Code Reviews, and BDD along with the goodness of CI and CD." - yes, and then things started to work! I.e., the answer had nothing to do with Scrum: you shifted your focus to DevOps practices.

The problem with Scrum is that Scrum encourages focus on things that don't matter that much - the "ceremonies" - and shifts attention from things that DO matter. Many Scrum Masters tend to obsess over "is that a proper story?" and "Are our standups effective?" instead of how thorough the tests are, how rapid the test and build systems are, what the production defect rate is, etc. I.e., they distract the teams from what matters.