A Glossary that is Comparative and Linked
Using the right engine oil is key to a smooth running engine. In a similar way, communicating with the right vocabulary is essential to a smooth running project. But the vocabulary of project management is not only extensive but tends to consist of different "dialects" according to the type of project and the technology involved. Even in the same area of project management application, there can be many "interpretations" of a particular term, or label, as the quotations in this Glossary demonstrate. Indeed, many seemingly familiar terms mean very different things to different people. For example, this Glossary lists no less than thirty definitions of the word "Project". True, many of the definitions are similar, but the meanings are by no means identical. Equally, some terms have labels that look the same but refer to very different things. For example: "Change Management" and "Management of Change" are very different practices.
It would be nice if everyone agreed and understood the same meaning for a given label. But language is a living lexicon leading to changes over time and, in any case, authors are entitled to define terms in their own way to suit their particular purpose. Language serves us much better this way. However, it does mean that it is essential to establish a set of terms for each program or group of projects, especially where meanings are significantly different. Miscommunication represents a significant risk to project success.
Hence the purpose of this Glossary – to help you see what others think and to make the best selection for your particular project environment. As you will see, web technology allows us to provide links within the definitions quoted, to connect to terms defined elsewhere to facilitate your better understanding. This version 5.0 contains around 6,500 entries covering 4,250 discrete terms.
Of these, over 150 entries refer to the new and emerging discipline of project portfolio management.
We believe that a copy of this Glossary should be a part of every project manager's toolkit, not just for reference, but also for the wealth of knowledge that it contains – all from respected sources. In passing, we have noted that there is a tendency for some authors to provide a glossary of terms having identical meanings as those quoted elsewhere but slightly different grammatical construction. This is presumably to avoid copyright infringement. In our view, this is a most unfortunate consequence of copyright laws infringing on freedom of expression, sequestering knowledge that is already in the public domain, and unnecessarily compounding risks in communication.
Acknowledgements
We are indebted to the many people who have contributed
to this glossary whether wittingly or unwittingly. In particular
to Graham Wideman for creating the software capable of generating
this Glossary and to Penny Schneider for the web site art work.
For comments and suggestions, Email to: max_wideman@sfu.ca
|
