I'm not sure this works right for NOTICE files.
For example, commons-logging might include some code written by a third party but licensed under an APL2.0-compatible license (including BSD, etc). In that case AIUI we remove copyright and license information from the files , and put it into NOTICE instead. This keeps the code uncluttered, while putting the contributor info for the project ancestry into one easy-to-find place (NOTICE.txt).
So it is not just a matter of taking the organisation property from the pom; a single mvn module can have multiple entries in its NOTICE file.
To be doubly-clear: a single maven module (that is, a single pom.xml file) may correspond to many lines of text in the NOTICE file, acknowledging every single copyright holder to code contained in that single maven module. AFAIK, it is not possible or appropriate to put one organization tag in a pom for every line we need in the NOTICE for that module.
For a notice inside a single JAR, I don't believe it is a legal requirement to acknowledge the copyright holders of jars it depends on. In fact I would prefer to NOT do that. The dependency information is explicitly present in the pom, and each of those dependent jars should contain its own acknowledgements.
Whether an overall NOTICE is needed for a downloadable bundle that contains multiple jars is debatable. I think not; there is a LICENSE file (APL2 of course) which is all that is relevant for most people.