Abstract
Purpose - This study explores the knowledge management perspective of IT projects, based on Enterprise System implementations. The study determined what knowledge is needed in each of the project phases (what for, from what sources), how this knowledge is transformed during the project (what knowledge activities are performed concerning this knowledge), and what knowledge-related artefacts are created. A knowledge management framework for ES projects is formulated based upon the results.Design/methodology/approach - The research has a qualitative exploratory design, based on multiple data sources: documentation, semi-structured interviews, and participant observation. A coding procedure was applied with the use of a pre-defined list of codes, as derived from Knowledge Management literature regarding knowledge types, actors, project phases, and activities. Open coding was used to determine the role of each type of knowledge in the implementation process.Findings - The study examined the significance of the particular types of knowledge of each project actor across the project phases, and identified the specific knowledge activities that need to be performed for a successful outcome. In contrast to existing literature, this study also demonstrates that project management knowledge consists of two components: generic and product-related. Meta-knowledge, i.e., knowledge about other people’s knowledge was also identified as critical in the initial phases of the project. Solution knowledge was identified as the primary knowledge product. It is the result of the integration of company and product knowledge and is embedded into the system.Research limitations/implications - The limitation of this study is that it concentrated on a specific type of the IT project, namely Enterprise System implementation. The results cannot be directly extrapolated to other IT projects.Practical implications - The results of the study may aid in effective staffing for ES implementations and in identifying the necessary knowledge sources. They may also enable the development of relevant knowledge management procedures for a project.Originality/value - No comprehensive Project Knowledge Management framework for Enterprise Systems has been found in the existing Knowledge Management literature, and this study fills this gap in the research.
Purpose - This study explores the knowledge management perspective of IT projects, based on Enterprise System implementations. The study determined what knowledge is needed in each of the project phases (what for, from what sources), how this knowledge is transformed during the project (what knowledge activities are performed concerning this knowledge), and what knowledge-related artefacts are created. A knowledge management framework for ES projects is formulated based upon the results.Design/methodology/approach - The research has a qualitative exploratory design, based on multiple data sources: documentation, semi-structured interviews, and participant observation. A coding procedure was applied with the use of a pre-defined list of codes, as derived from Knowledge Management literature regarding knowledge types, actors, project phases, and activities. Open coding was used to determine the role of each type of knowledge in the implementation process.Findings - The study examined the significance of the particular types of knowledge of each project actor across the project phases, and identified the specific knowledge activities that need to be performed for a successful outcome. In contrast to existing literature, this study also demonstrates that project management knowledge consists of two components: generic and product-related. Meta-knowledge, i.e., knowledge about other people’s knowledge was also identified as critical in the initial phases of the project. Solution knowledge was identified as the primary knowledge product. It is the result of the integration of company and product knowledge and is embedded into the system.Research limitations/implications - The limitation of this study is that it concentrated on a specific type of the IT project, namely Enterprise System implementation. The results cannot be directly extrapolated to other IT projects.Practical implications - The results of the study may aid in effective staffing for ES implementations and in identifying the necessary knowledge sources. They may also enable the development of relevant knowledge management procedures for a project.Originality/value - No comprehensive Project Knowledge Management framework for Enterprise Systems has been found in the existing Knowledge Management literature, and this study fills this gap in the research.