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

Implementation of multi-criteria decision making approach for the team leader selection in IT sector

2016· article· en· W2604119440 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 · 2016
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicCollaboration in agile enterprises
Canadian institutionsnot available
Fundersnot available
KeywordsMultiple-criteria decision analysisTeamworkSelection (genetic algorithm)Ranking (information retrieval)Team software processTeam compositionTeam effectivenessComputer scienceQuality (philosophy)SoftwareKnowledge managementTeam managementPoint (geometry)Process (computing)Work (physics)Rank (graph theory)Software developmentOperations researchSoftware development processEngineeringArtificial intelligenceMathematicsManagementEconomics

Abstract

fetched live from OpenAlex

In the era of technology, the demand of the software development increases at a very high speed, as software has touched the human's life in all aspects. The better quality software development acquiring minimum development time leads to the team work in which a group of people has been formed that work together in a team for the software development. One of the most significant issues in effective and efficient teamwork is the team leader selection because the team leader is the person in any team that is going to handle all types of managerial activities such as leadership, motivation to others, etc. The team leader selection process may be dependent on numerous conflicting selection indexes that make it a Multi-Criteria Decision Making (MCDM) problem. In the present research, an MCDM approach namely, Euclidean Distance Based Approximation (EDBA) which is based on the calculation of the composite distance value for each alternative from a hypothetical optimal point is presented. The result of this study provides a comprehensive ranking of team leaders that leads to the right selection of team leader in information technology (IT) sector.

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.001
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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.942
Threshold uncertainty score0.284

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.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.052
GPT teacher head0.356
Teacher spread0.304 · 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