> no matter how trivial a thing is, it will be a showstopper for someone I used to work for a big web site that produced standardized requirements documents ah

> no matter how trivial a thing is, it will be a showstopper for someone I used to work for a big web site that produced standardized requirements documents ahead of every project. Part of the standard was the "flexibility matrix": the PM or "stakeholder" who was producing the requirements document was supposed to identify whether scope or timeline was most flexible. Of course, for about five years running after the standard document template came out, every project was "least flexible" on timeline and "most flexible" on scope. We finally started calling them on their impossible timelines and tried flexing the scope by pushing some of the vague requirements off to later releases. The result? They added another column to the "flexibility matrix" called "resources", as in they were willing to hire more people to meet all the requirements in the mandated timeline. That was also not true.