I should appreciate members viewpoint if there would be a benefit for creation or update where such exist of a PM Taxonomy which would also if you see appropriate to include PM methodology (most popular on a global basis is PRINCE2), PM organizational maturity model (I suggest P3M3) and Portfolio, Programme and Project Offices (P3O).
From my perspective what makes a taxonomy more useful than a mere term list or glossary is the presence of relationships between its terms. Relationships between pairs of terms are bidirectional (reciprocal). Broadly speaking there are three kinds of relationships:
1. Equivalence: between preferred and non-preferred terms
2. Hierarchical: between broader and narrower terms
3. Associative: between related terms
The most basic controlled vocabularies and authority files have at least the equivalence relationship. Classification and categorization schemes, thesauri, and nearly all taxonomies have hierarchical relationships and usually associative relationships as well.
Relationship types are often denoted by labels, with the corresponding abbreviations or codes, between pairs of terms or preceding the various related terms for a selected term. The following is a list of the most common such labels, although you may in my opinion choose a different designation in each case.
- Equivalence: USE/ UF (use/ used[d] for)
- Hierarchical: BT/ NT (broader term / narrower term)
- Associative: RT (related term)
Thoughts on a PM Taxonomy which could encompass the various documents described above would be appreciated. Comments, suggestions and thoughts most welcome.