MétaCan
Menu
Back to cohort
Record W3090259606 · doi:10.1108/ijmpb-01-2020-0028

Does one project success measure fit all? An empirical investigation of Brazilian projects

2020· article· en· W3090259606 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

VenueInternational Journal of Managing Projects in Business · 2020
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsToronto Metropolitan University
Fundersnot available
KeywordsProject managementContext (archaeology)OriginalityProject stakeholderProject management triangleOPM3Measure (data warehouse)Process managementScale (ratio)Knowledge managementComputer scienceProject planningSoftware project managementProject managerBusinessSoftwareEngineeringSoftware developmentSociologySystems engineeringQualitative research

Abstract

fetched live from OpenAlex

Purpose The purpose of this research is to identify and accumulate knowledge on the existing developments on project success measures. The authors aim to contribute to this debate by providing both researchers and project management professionals with reliable contemporary project success criteria that permit generalization for a proper assessment regardless of the type and context of the project. Design/methodology/approach Data were collected from 264 Brazilian project managers from a range of industries, sectors of activities and business areas with different levels of experience. Data analysis was performed using the R software package. Findings In this research, the authors propose a general performance measure of project success where different projects can grade differently using the same scale. The data analysis validated five constructs of the developed model in the Brazilian setting. Originality/value Most of the actual project success measures used in project management literature have been tested in a specific industry or sector. Combinations of the type of project, industry, sector, project nature, stakeholders and other variables make each project unique. Thus, any effort to find a context-specific tool of measure will be an endless endeavor. To fill this gap, more general project success criteria need to be explored to offer a common point of comparison between projects. This is the motivation of the present study.

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.002
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.133
Threshold uncertainty score0.624

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0020.003
Science and technology studies0.0000.000
Scholarly communication0.0000.003
Open science0.0020.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.210
GPT teacher head0.410
Teacher spread0.199 · 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