MétaCan
Menu
Back to cohort
Record W7117314230 · doi:10.3390/systems14010022

Exploring the Impact of Customer Organizational Culture on Project Agility in ERP Implementation Projects

2025· article· en· W7117314230 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueSystems · 2025
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsUniversité du Québec à Montréal
FundersFonds de Recherche du Québec-Société et Culture
KeywordsEnterprise resource planningAgile software developmentOrganizational cultureProject managementCustomer relationship managementResource (disambiguation)

Abstract

fetched live from OpenAlex

Enterprise Resource Planning (ERP) projects have been the focus of extensive research in recent years. To overcome the challenges associated with these types of projects, one emerging and relatively unexplored stream of research has examined the application of agile project management (APM) in ERP implementation contexts. Despite its growing popularity, APM adoption remains complex, risky, and not yet fully understood. This study focuses on the critical role played by the customer in such projects, as it can either foster or hinder agility. A lack of customer collaboration can often be linked to the customer’s organizational culture (OC). Thus, this study aims to investigate the specific relationship between the customer’s OC and project agility in ERP implementation projects within small- and medium-sized enterprises (SMEs). To conceptualize OC, we adopted the Competing Values Framework (CVF), which distinguishes four cultural types: Clan, adhocracy, hierarchy, and market. Data were collected through an online questionnaire administered to 172 ERP end-users from Canadian SMEs who had participated in their organizations’ ERP implementation projects. The analysis was performed using SmartPLS version 4.1.0.9. The results confirm that customers characterized by a clan, adhocracy, or market culture positively influence project agility, while there was no significant effect of hierarchy culture on project agility. This study addresses several gaps in the literature and offers practical implications. The findings support the idea that vendors should better frame and justify introducing APM in ways that align with each customer’s cultural characteristics within ERP vendor–customer relationships.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.059
Threshold uncertainty score0.997

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.098
GPT teacher head0.363
Teacher spread0.266 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it