Assumptions
We are assuming that the PMKS will be used to
- Assemble knowledge and experience that is encompassed by project management
and clarify what is excluded
- Provide a basis for comparing features and practices in different environments,
cultures and areas of application
- Run electronic and non-electronic information searches based on the contained
PMKDs
- Establish a reference baseline and checklists for the benefit of academics
and practitioners alike in their education, training and application endeavors
Included in our assumptions should be the founding definitions of the PMKS
model. Given our goal, these would be the definitions we adopt for the terms
"project management", "project", "management" and "success". The more convincing
and focused we can make these definitions, the more likely we are to succeed
in achieving collective buy-in of the structure. Given the stated objectives,
we propose the following. Note, however, it is not so much the exact wording
but the content that is important.
- Project Management: The art and science of managing a project from
inception to closure as evidenced by successful product delivery and transfer.
- Project: A unique process or undertaking designed to create a new
product or service.
- Management: The act of planning, organizing, coordinating, commanding,
and controlling.[14]
- Success (project success): The perception of satisfaction on the
part of the customers, i.e. those who will use the product, firstly with the
resulting product or service, and secondly with the process that achieved
it.
14. Fayol, H., General and Industrial
Management, IEEE Press, NY, Rev. ed. 1984.
|
Objectives
for Structuring a PMKS
