MétaCan
Menu
Back to cohort
Record W63745689

Responding—or Not—to IT Project Risks: Conceptualizing Risk Response as Planned Behavior

2014· article· en· W63745689 on OpenAlex
Mohammad Moeini, Suzanne Rivard

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

Study designTheoretical or conceptual
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

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.

Bibliographic record

VenueInternational Conference on Information Systems · 2014
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsHEC Montréal
Fundersnot available
KeywordsTheory of planned behaviorRisk perceptionPsychologyRisk managementProject risk managementControl (management)Social psychologyApplied psychologyRisk analysis (engineering)Knowledge managementPerceptionProject managementComputer scienceBusinessEngineeringProject management triangle
DOInot available

Abstract

fetched live from OpenAlex

Prior research suggests that IT project managers’ risk response behavior sometimes differs from the prescriptions in the literature. Conceptualizing performing a risk response as planned behavior, this study draws upon the theory of planned behavior (TPB) and develops a model to enrich the understanding of the relationship between perceiving risk and enacting—or not—a risk response. The model includes the TPB constructs—behavioral attitude, perceived pressure and perceived control. It also leverages the notion of ‘background factors’ in TPB that allows the inclusion of antecedents of behavioral attitude, in the present study, perceived risk of project without the risk response and perceived risk of enacting the risk response. The research design comprises three studies. Study 1 selected three specific risk responses. Study 2 elicited IT project managers’ beliefs about each risk response. Study 3 (in progress), tests the proposed model—enriched with the elicited beliefs—for each risk response.

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.

How this classification was reachedexpand

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.002
metaresearch head score (Gemma)0.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.923
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

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

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.108
GPT teacher head0.393
Teacher spread0.286 · 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