In a recent post in response to the assumptions of APM, other than restating I was "wrong," did not move the discussion forward.
Can APM address things like long lead, design up front, target more than software development, perform cost and schedule trades?
My sense is that the term "project management" has distinctly different meanings between the APM community and the general project management community. Bill Duncan was right long ago when he stated that ..."it does no good to discuss a topic if we can't agree on the basic terminology."
In my experience it's too narrow to talk about "project management" only in the context of agile software development projects and call it "project management." If that is th intent of APM, then it will remain bound to it's agile software development methodology roots, missing the opportunity to expand to a much broader community of project managers having little or not interest in software development.