MétaCan
Menu
Back to cohort
Record W3125218975 · doi:10.53555/nnbma.v2i2.106

Scope Creep Monitors Level of Satisfaction, Cost of Business and Slippery Slope Relationships Among Stakeholders, Project Manager, Sponsor and PMO to Execute Project Completion Report

2016· article· en· W3125218975 on OpenAlexaff
Gazi Farok, José Alejandro Lugo García

Bibliographic record

VenueJournal of Advance Research in Business Management and Accounting (ISSN 2456-3544) · 2016
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsToronto Metropolitan UniversityYork University
Fundersnot available
KeywordsScope (computer science)CreepWork (physics)BusinessStakeholderStatement of workProject managerProject managementOperations managementComputer scienceEngineeringManagementEconomicsMechanical engineering

Abstract

fetched live from OpenAlex

Scope creep is a change which is an update or addition to the whole or a part of project has been requested when the project is running on significantly an underway. Scope creep increases work with level of satisfactions off as well as any one would expect, but over time the project seems to get bigger and bigger while his or her price remains the same. The stakeholder either seems to think that the “extra work” is within the scope of the original agreement, or simply doesn’t realize that he or she is asking for more than was originally agreed. Either way, the project is losing money. Scope creep is a slippery slope and can be difficult to recover from. Once project manager accepts scope creep from one client s/ he is setting a precedent for the rest, and although s/ he may not have to physically hand over money as a result of scope creep, the effect is essentially the same. More time spent on a project than sponsor anticipated puts s/ he out of pocket.

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.004
metaresearch head score (Gemma)0.001
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.305
Threshold uncertainty score0.628

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.002
Science and technology studies0.0000.000
Scholarly communication0.0000.003
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.262
GPT teacher head0.379
Teacher spread0.118 · 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

Classification

machine, unvalidated

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

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
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".

Quick stats

Citations3
Published2016
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Advance Research in Business Management and Accounting (ISSN 2456-3544)Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207