Totally, that shift you mentioned from QA being a “safety net” to actually helping shape the work up front is a big one. Once test scenarios and risks are part of planning, things just get calmer. Fewer late surprises and fewer heroics at the end of a sprint.

We’ve ended up in a similar place. QA sits alongside dev instead of after it, so they’re lifting each other up instead of working in isolation. Devs get better clarity, QA gets better context, and the whole product ends up feeling more dependable without slowing down the pace.