MétaCan
Menu
Back to cohort
Record W2809716361 · doi:10.1177/875697280603700307

Longitudinal Analysis of Project Management Maturity

2006· article· en· W2809716361 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

VenueProject Management Journal · 2006
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicInformation Technology Governance and Strategy
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsCapability Maturity ModelMaturity (psychological)OPM3BenchmarkingProcess managementAuditProject managementService Integration Maturity ModelBest practiceProgram managementKnowledge managementEngineeringBusinessComputer scienceSystems engineeringManagementAccountingPolitical scienceMarketing

Abstract

fetched live from OpenAlex

This paper examines and identifies core dimensions of assessment frameworks, including five core requirements for conducting assessments, two key processes of assessing organizations (audit and self-assessment), and two dimensions of improving performance (delivering data and applying data). It discusses the evolution of using maturity models to assess organizational capabilities and the development of maturity models to assess project management competencies. It then outlines a five-level project management maturity model that the authors used to assess the way 550 international organizations practice project management. The paper lists the challenges, advantages, and disadvantages of using this model; it identifies the practices synonymous with improvements in demonstrated maturity. It also compares the results ofdata collected since this benchmarking study's inception, results that show underlying project management trends, such as changes in organizational capabilities and performance. It reviews the impact of these trends on the studied organizations and the way they manage their projects. It concludes by detailing four key—and unexpected—results.

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 categoriesMeta-epidemiology (narrow)
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.813
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0030.003
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.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.016
GPT teacher head0.249
Teacher spread0.233 · 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