Heh... I enjoyed the list and I agree with much of the sentiment. However, I feel there are some key areas that are incorrect.

The main problem I find with that list is it shows the a lack of experience working with an effective project manager. And effective PMs are those that rely on some of the underlying concepts of many of those words rather than their buzz-interpretation. For example, identifying what items are in fact "Actionable" vs. abstract, ambiguous dialog is critical to actually accomplishing completed work.

And while it wasn't expounded upon greatly, I felt this statement was a little off: "Everyone else outside of engineering has vastly less working knowledge of the product." To a certain extent, I agree with the concept, but it shows how the gross arrogance of anyone involved in the completion of a project can hurt it. As an engineer, I have some of (if not the greatest) understanding of the execution of function within the product. That does not equate to everyone else having less working knowledge of the product. The "product" is the thing you're *endeavoring* to create. Not that exists in reality. And by the very fact that as engineers, we're stuck in the perspective of establishing the best way to execute/integrate the FUNCTIONALITY being expected of the product. This makes our understanding of the product as it would exist in a perfect balance of form, function, and usability grossly misaligned. I count on qualified UX designers, black-box QA, and effective PMs to achieve as close to that ideal.