I followed a few links, and didn&#x27;t see much background information about Ben&#x27;s experience with companies using JIRA at scale; from the tone of the posted sounds like he is seen some bad management and action.<p>But here&#x27;s another point of view; at work we (among other things) train and consult companies on effective use of JIRA. As best we can tell, our students and clients are well-intentioned, trying to use JIRA for good, not for evil. They often want something similar to what Ben wrote about, to get numerous projects and teams across a large organization using the same tracking tool (JIRA) in approximately the same way, with local variations as needed but avoiding pointless variations.<p>I&#x27;ve actually not heard of any of them trying to &quot;ensure velocity parity&quot;, but rather the typical goal is to be able to roll up and understand project status and progress across a large and sprawling organization working on goals that far exceed what an individual team could do. This seems like a worthy and important goal.