MétaCan
Menu
Back to cohort
Record W4408771665 · doi:10.51594/farj.v7i2.1850

Improving team productivity and financial services efficiency with agile story points

2025· article· en· W4408771665 on OpenAlex
David Iyanuoluwa Ajiga, Oladimeji Hamza, Adeoluwa Eweje, Eseoghene Kokogho, Princess Eloho Odio

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

VenueFinance & Accounting Research Journal · 2025
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsBank of Canada
Fundersnot available
KeywordsAgile software developmentProductivityBusinessResource (disambiguation)Process managementKnowledge managementComputer scienceEconomics

Abstract

fetched live from OpenAlex

This paper explores using Agile story points to enhance team productivity and efficiency in financial services, highlighting their benefits, challenges, and future implications. Story points are essential for estimating task complexity, risk, and effort, offering a flexible approach to sprint planning and resource allocation. The paper discusses the role of story points in improving communication among teams, increasing predictability, and ensuring timely customer delivery. Additionally, it examines the challenges associated with subjectivity in estimations, the influence of team dynamics, and the difficulties of scaling Agile practices in large financial institutions. Recommendations are provided for optimizing story point usage, scaling Agile across teams, and ensuring the necessary technological and organizational support for maximizing productivity. The findings emphasize that, with the right framework and leadership buy-in, Agile story points can drive significant improvements in efficiency within the highly regulated financial services sector. Keywords: Agile Story Points, Team Productivity, Financial Services, Resource Allocation, Sprint Planning, Scaling Agile

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.005
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.585
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0020.000
Scholarly communication0.0020.004
Open science0.0010.001
Research integrity0.0000.001
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.029
GPT teacher head0.307
Teacher spread0.278 · 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