Modeling the Knowledge Perspective of IT Projects
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
Information technology (IT) projects are often viewed as arenas in which action is paramount, and tasks, budgets, people, and schedules need to be managed and controlled to achieve expected results. This perspective is useful because it encourages the project manager to scope work, manage time and budget, and monitor progress. Another perspective views a project as a place where learning and knowledge is paramount. In this view, projects are seen as a conduit for knowledge, which enters through people, methodologies, and prior learning. During the project, knowledge must be transferred, integrated, created, and exploited to create new organizational value. Knowledge is created, and knowledge can be lost. Within an IT project, this focus on knowledge yields new insights, because IT projects are primarily knowledge work. From this perspective, the project manager's primary task is to combine multiple sources of knowledge about technologies and business processes to create organizational value. These and other views of the IT project are complementary. However, this article focuses only on the knowledge perspective, leaving aside other views. This article is designed to bring together the empirical literature, which has investigated the impact of knowledge perspectives on IT project performance, and to suggest a temporal model of this perspective. In the first part of this article, we consider the knowledge-based view of an IT project and suggest definitions and a typology of knowledge. Then the knowledge risks model (Reich, 200?) is used as a framework within which to collect and examine the empirical data that support the knowledge-based view of an IT project. In the third part of this article, the problem of modeling knowledge and learning within IT projects is addressed. The study begins with the Temporal Model of IT Project Performance (Gemino, Reich, & Sauer, 2008) and discusses evidence that its knowledge-based constructs and subconstructs are influential with respect to project performance. The article ends by proposing a temporal model of the knowledge perspective of an IT project. There are five constructs in this model: knowledge resources, knowledge creation, knowledge loss, project performance, and learning. The content of these constructs and their expected interaction is discussed. Although this stream of work is at its early stages, hopefully it will convince researchers that further investigation into knowledge and learning within projects is warranted because it has the potential to impact both the theory and performance of IT projects.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,001 |
| Études des sciences et des technologies | 0,001 | 0,000 |
| Communication savante | 0,000 | 0,001 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle