I like to use the 5 why's method to think about this: Why is "every sprint we either fail to deliver the work we commit to, or deliver work that ultimately fai

I like to use the 5 why's method to think about this: Why is "every sprint we either fail to deliver the work we commit to, or deliver work that ultimately fails the QA process"? Is it you fail to deliver the work because of QA? It sounds like that might be the first why. Why does it fail QA? Lack of unit testing? Are there any patterns in the bugs? Maybe that code is brittle and hard to work with? Dig down, as the reasons for under-performing could be entirely the team, or the team actually over-performing considering the environment. Technical reasons you can fix. People issues you can fix with management, process, etc. If you can do a blameless postmortem, go for it. Maybe you can improve morale by giving people the opportunity to fix their own problems. If you don't think that can happen, then that alone may point toward the problem.