MétaCan
Menu
Back to cohort
Record W74833669 · doi:10.17705/1cais.02609

Developments in Practice XXXIV: Application Portfolio Management

2010· article· en· W74833669 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

VenueCommunications of the Association for Information Systems · 2010
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsQueen's University
Fundersnot available
KeywordsRationalization (economics)PortfolioProcess managementCorporate governanceProcess (computing)CategorizationBusinessKnowledge managementProject portfolio managementManagement scienceComputer scienceProject managementManagementEngineeringEconomicsFinance

Abstract

fetched live from OpenAlex

APM is the ongoing management process of categorization, assessment and rationalization of the IT application portfolio which allows organizations to identify which applications to maintain, invest in, replace, or retire. To understand current APM strategies and practices, the authors convened a focus group of senior IT managers from a number of organizations. Results of the focus group discussion pointed to the need to develop three inter-related APM capabilities: (1) strategy and governance, (2) inventory management, and (3) reporting and rationalization. To deliver value with APM, organizations must establish all three capabilities. Experience suggests that organizations tend to start by inventorying applications and work from the “middle out” to refine their APM strategy (and how it is governed) as well as to establish efforts to rationalize their applications portfolio. As such, APM represents a process of continual refinement. Fortunately, experience also suggests that there are real benefits to be reaped from the successful development of each capability. The paper concludes with some lessons learned based on the collective experience of the members of the focus group.

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.002
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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.983
Threshold uncertainty score0.322

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.003
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.013
GPT teacher head0.254
Teacher spread0.241 · 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