I will say it's having an impact on me personally. In the tech world, we work in 2 week Sprints and Sprints have Stories. Stories are Pointed efforts rated on l

I will say it's having an impact on me personally. In the tech world, we work in 2 week Sprints and Sprints have Stories. Stories are Pointed efforts rated on level of effort that need to be completed within a single Sprints. Developers can only be allotted X number of Points per Sprint. If stories aren't done, then you usually need to reflect on why and improve, typically breaking down high pointed stories into smaller ones. The problem with many organizations face is that instead of leaving a Story open and answering the why, they'll simply close the problem Story and open a new one with the missed worked. This causes problems all over the place and snowballs if not addressed. In my situation, we also cancelled Retros so concerns weren't being raised further compounding things and finger pointing. So what may have started as an over zealous developer with a well intentioned manager can become a trend leading to missed deadlines, cut corners and defective code making it to production. I started to realize that I was no different than Boeing; that I was Boeing and that hasn't sat right with me. So for better or worse, I'm going to be more vocal about things.