Objectives for Structuring a PMKS

For our PMKS objectives we may again borrow from Forsberg's observations on
the essentials of a project management model.[13]
That is, to create a PMKS that:

Is explicitly and operationally defined as to structure, variables and
relationships

Is obviously valid and intuitive to all project stakeholders

Is generally applicable throughout the project environment in a way that
accounts for the complexity and dynamics of the project process...

Is validated empirically in the real project world

To this we might add the following practical considerations:

Is simple, logical and understandable, but comprehensive and flexible

Keeps the number of hierarchical levels within practical limits

Builds on existing project management understanding

Uses familiar terms and phrases that facilitate both electronic and non-electronic
retrieval of information relevant to project management.

Identifies and cross-links to hierarchies and word sets that apply to more
than one branch of the structure

Does not impose any proprietary view of project management.

With reference to item 9, the cross-linking suggested would highlight both
overlaps between areas of project management application and the 'fractal' nature
of project management. A 'fractal', by the way, is defined as a geometric shape
having the property that each smaller portion of it can be viewed as a reduced
scale replica of the whole - a common feature of the project management process.

If we can meet these lofty objectives, then perhaps we might arrive at a useful
and near-universally accepted structure.