MétaCan
Menu
Back to cohort
Record W4385777000 · doi:10.5267/j.jpm.2023.7.001

MCDM approach to investigate the effectiveness of SCRUM events in minimizing risk factors in project management

2023· article· en· W4385777000 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Project Management · 2023
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsnot available
Fundersnot available
KeywordsScrumAgile software developmentComputer scienceProject managementProcess managementScope (computer science)Systems engineeringEngineeringSoftwareSoftware developmentSoftware engineering

Abstract

fetched live from OpenAlex

Traditional project management methods have been used for many years in the implementation and management of projects. With the publication of the agile manifesto in 2001, the interest in agile methods increased and successful results were obtained in the execution and solution of complex projects with agile approaches. Agile approach consists of different structures that can be named as framework or method. Among these agile methods, which are selected and applied according to the suitability and purpose of the project, the most frequently preferred one is SCRUM. In this study, SCRUM, an agile project management technique that has been used frequently in recent years in order to develop a flexible project management process, has been examined, and the effectiveness of the events of the SCRUM technique in minimizing the risks that arise in project management has been evaluated. Determining the effectiveness of these SCRUM events, which each agile project team implements in turn, is very important for the correct and effective allocation of resources. For this purpose, a multi-criteria decision-making model has been proposed to evaluate the effectiveness of 4 SCRUM events within the scope of this study. While the importance weights of the 24 project management risk factors proposed in the solution phase of the created model were determined by the SWARA method, the SCRUM events were evaluated with the WASPAS, COPRAS and EDAS methods and the solution values found by three different methods were compared.

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.006
metaresearch head score (Gemma)0.000
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.457
Threshold uncertainty score0.512

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0060.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.003
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.001
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.038
GPT teacher head0.301
Teacher spread0.263 · 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