MétaCan
Menu
Back to cohort
Record W2093598336 · doi:10.1108/01409171211247703

Aligning organizational values in systems development projects

2012· article· en· W2093598336 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

VenueManagement Research Review · 2012
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicInformation Technology Governance and Strategy
Canadian institutionsQueen's University
Fundersnot available
KeywordsAgile software developmentOriginalityKnowledge managementValue (mathematics)PerceptionOrganization developmentEnthusiasmQualitative researchComputer scienceProcess managementPsychologyBusinessSociologySocial psychology

Abstract

fetched live from OpenAlex

Purpose The purpose of this paper is to examine the antecedents and implications of aligning the organizational values embedded in a systems development approach (e.g. agile) with the organizational values of project team members. Design/methodology/approach A qualitative case study approach is used to examine systems development project teams at three organizations, each using a development approach that incorporates different organizational value dimensions. Interviews were conducted with developers, systems analysts, and managers regarding their systems development experiences. A structured coding of the interview transcripts was then completed to enable analysis of value dimensions. Findings By comparing the dominant values between the project teams and their development approach, varying degrees of alignment were identified. Where alignment is high, perceptions of the systems development process are associated with satisfaction and enthusiasm; where alignment is low, perceptions focus on frustration and discontent. Research limitations/implications Based on the study's findings, four propositions pertaining to the antecedents and implications of IS values alignment are outlined for examination in future research. Practical implications The findings from this study can aid managers who are considering the use of a new systems development approach or evaluating the effectiveness of their current approach. By determining the degree of information systems (IS) values alignment, organizations may be able to customize their development approach to be more consistent with the team's values, in order to minimize negative development process perceptions and increase project performance. Originality/value This research extends past studies of organizational values and alignment by introducing the concept of IS values alignment.

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.004
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
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.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
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.002

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.116
GPT teacher head0.333
Teacher spread0.217 · 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