MétaCan
Menu
Back to cohort
Record W2920097760 · doi:10.1080/09537287.2019.1567859

A dimensional analysis of stakeholder assessment of project outcomes

2019· article· en· W2920097760 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.

Bibliographic record

VenueProduction Planning & Control · 2019
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsConcordia University of Edmonton
Fundersnot available
KeywordsProject stakeholderProject sponsorshipStakeholderStakeholder analysisProject managementProject managerProject management triangleProject charterProject planningStakeholder managementProject risk managementProcess managementBusinessExtreme project managementProject teamProject portfolio managementWork breakdown structureOPM3Knowledge managementPublic relationsEngineeringPolitical scienceComputer scienceSystems engineering

Abstract

fetched live from OpenAlex

Driven by an interest in developing a deeper understanding of stakeholder interests, this study undertakes a dimensional analysis of how different stakeholders assess project outcomes. Most importantly, in our analysis, we take into consideration the largely unaccounted-for conceptual difference between project success and project failure. Data were collected over a 2-year period (between 2013 and 2015) from 1631 project stakeholders in nine countries. We analyzed the survey data using three-way Multidimensional Scaling. We found that most project stakeholders tend to be more specific in their assessment of project success than when assessing project failure. We also found that most stakeholders attached maximal and different levels of importance to different dimensions of project outcomes. In particular, we found that when assessing project ‘success’, project stakeholders appear more focused on project effectiveness. On the other hand, when assessing project ‘failure’, project stakeholders appear more focused on efficiency. Understanding how stakeholders assess and prioritize project outcomes is of particular interest to project managers as it enables them develop a clearer understanding of individual interests of various stakeholders. For stakeholders themselves, such an understanding helps limit possible disruptions to the project emanating from contesting decisions made by the project manager.

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.003
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.011
Threshold uncertainty score0.741

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0020.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.131
GPT teacher head0.415
Teacher spread0.285 · 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