MétaCan
Menu
Back to cohort
Record W3192828292 · doi:10.1080/09537287.2021.1909168

The impact of project portfolio management practices on the relationship between organizational ambidexterity and project performance success

2021· article· en· W3192828292 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 · 2021
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsStantec (Canada)
Fundersnot available
KeywordsAmbidexterityBusinessScope (computer science)PortfolioKnowledge managementProject portfolio managementProject managementProcess managementManagementComputer scienceEconomicsFinance

Abstract

fetched live from OpenAlex

Some studies suggest that organizational ambidexterity is best orchestrated through individual projects. However, stand-alone individual projects are relatively limited in scope, while suffering from susceptibilities to horizontal and vertical segmentation. This may render them poorly suited to serve as conduits for organizational ambidexterity. By contrast, organizations which deliver projects in portfolios, often in order to maximize resource utilization, may discern that these also provide better conduits for organizational ambidexterity. This study examines not only the extent to which project portfolio management (PPM) practices impact orchestrations of organizational ambidexterity, but also whether these orchestrated PPM practices impact further lead to superior project performance. Data were collected from one hundred and sixty PPM stakeholders spread across eight countries in the Middle East November 2016 to January 2017. The study finds portfolios performance to be strongly and highly correlated with organizational ambidexterity. Furthermore, the more organizations exhibited efficient project-portfolio-management practice, the more they were found to develop ambidextrous capabilities.

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.004
metaresearch head score (Gemma)0.006
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.008
Threshold uncertainty score0.792

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.006
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0010.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.166
GPT teacher head0.423
Teacher spread0.256 · 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