Netta Iivari

The relationship between organizational culture and the deployment of agile methods

ContextSystems development normally takes place in a specific organizational context, including organizational culture. Previous research has identified organizational culture as a factor that potentially affects the deployment systems development methods. ObjectiveThe purpose is to analyze the relationship between organizational culture and the post-adoption deployment of agile methods. MethodThis study is a theory development exercise. Based on the Competing Values Model of organizational culture, the paper proposes a number of hypotheses about the relationship between organizational culture and the deployment of agile methods. ResultsInspired by the agile methods thirteen new hypotheses are introduced and discussed. They have interesting implications, when contrasted with ad hoc development and with traditional systems development methods. ConclusionBecause of the conceptual richness of organizational culture and the ambiguity of the concept of agility the relationship between organizational culture and the deployment of agile systems development forms a rich and interesting research topic. Recognizing that the Competing Values Model represents just one view of organizational culture, the paper introduces a number of alternative conceptions and identifies several interesting paths for future research into the relationship between organizational culture and agile methods deployment.

Varieties of user-centredness: an analysis of four systems development methods

Based on an extensive literature analysis, this paper examines user‐centredness in the context of systems development as a multidimensional concept composed of four aspects: user focus, work‐centredness, user involvement and system personalization. Each dimension loads user‐centredness with different meanings. The four dimensions can be used for evaluating systems development methods and approaches as to what extent and in what sense they adhere to the ideals of user‐centredness. To illustrate this, the dimensions are applied to the analysis of four allegedly user‐centred systems development methods: Goal Directed Interaction Design, Contextual Design, Scenario‐Based Design and Human‐Centred Systems Development Life Cycle. The analysis shows considerable variation in how these methods address the four dimensions of user‐centredness.

Varieties of User-Centeredness

This paper critically examines user-centeredness as a multidimensional concept along four aspects: as user focus; as work-centeredness; as user participation; and as system personalization. Each aspect loads user-centeredness with different meanings. It is discussed whether user centered design can be considered an information systems development approach on its own. In its current form, we do not see it as a separate approach, because it is neither horizontally nor vertically complete, and because of the overall confusion regarding its goals, principles and practices. The four dimensions identified can be used for evaluating information systems development methods and approaches to what extent they adhere to the ideals of user-centeredness.

The standard of user-centered design and the standard definition of usability: analyzing ISO 13407 against ISO 9241-11

ISO 9241-11 and ISO 13407 are two important standards related to usability: the former one provides the definition of usability and the latter one guidance for designing usability. We carried out an interpretative analysis of ISO 13407 from the viewpoint of the standard definition of usability from ISO 9241-11. The results show that ISO 13407 provides only partly guidance for designing usability as presumed by the definition. Guidance for describing users and environments are provided but very limited guidance is provided for the descriptions of user goals and usability measures, and generally for the process of producing the various outcomes.

“Constructing the users” in open source software development: An interpretive case study of user participation

Purpose – The purpose of this paper is to report findings from an interpretive case study on user participation in the open source software (OSS) development context.Design/methodology/approach – Through an empirical, interpretive case study and a literature review utilising the metaphor of text in the analysis, this paper provides a refined conceptualisation of user participation in OSS development.Findings – The paper reveals that different kinds of meanings have been attached to users and to their participation. User participation is both direct and indirect in the OSS development context. Some user groups actively take part in OSS development, while others are merely represented in it. Different kinds of intermediaries “representing the users” are identified.Research limitations/implications – The research is based on one case study on a small but active OSS project with an interest in users. Other kinds of OSS projects should be analysed. The analysis was focused on a discussion forum, but users can ...

Enculturation of user involvement in software development organizations - an interpretive case study in the product development context

It is widely accepted that users should be involved in the interactive systems development. Ho wever, involving the users is often difficult and quite rare in software development organizations, especially in the product development context. We took a culturally oriented approach in the analysis of the position of user involvement in two software development organizations operating in the product development context. We analyzed how user involvement is modified and interpreted in the cultural context. This meaning negotiation - enculturation - process was the focus of empirical examination. Empirical material was gathered and analyzed by employing an interpretive research approach. The results suggest that there exist clear differences in how user involvement, has been encultured in the case organizations. The case organizations employ different approaches to user involvement, and differing strategies for the facilitation of user involvement. As an implication for practice, we emphasize the importance of understanding the cultural context in which the user involvement is to be initiated, and suggest that different approaches to user involvement might be selected in differing cultural settings.

The interaction between organizational subcultures and user-centered design-a case study of an implementation effort

Usability is a quality characteristic of a software product or system. User-centered design (UCD) is an approach focusing on making systems usable. However, improving the position of UCD is widely recognized as a challenge. This paper reports results from a case study, in which a small software development company was introduced to UCD principles and activities, and thus expected to change their current practice. The paper takes a culture-oriented approach to the analysis. The focus is on the interaction between organizational culture and UCD, organizational culture being conceived as a set of subcultures. The results indicate that there exist differences: 1) in the views of the nature of UCD; 2) in the motives for implementing it; and 3) in the experiences gained and interpretations made of the use of it in relation to each subculture. The implications for the prospective research and practice are discussed.

Empowering the users? A critical textual analysis of the role of users in open source software development

This paper outlines a critical, textual approach for the analysis of the relationship between different actors in information technology (IT) production, and further concretizes the approach in the analysis of the role of users in the open source software (OSS) development literature. Central concepts of the approach are outlined. The role of users is conceptualized as reader involvement aiming to contribute to the configuration of the reader (to how users and the parameters for their work practices are defined in OSS texts). Afterwards, OSS literature addressing reader involvement is critically reviewed. In OSS context, the OSS writers as readers configure the reader and other readers are assumed to be capable of and interested in commenting the texts. A lack of OSS research on non-technical reader involvement is identified. Furthermore, not only are the OSS readers configured, but so are OSS writers. In OSS context while writers may be empowered, this clearly does not apply to the non-technical OSS readers. Implication for research and practice are discussed.

Usability cost-benefit analysis: how usability became a curse word?

Usability is an important quality characteristic of software (SW) products and systems. Usability cost-benefit analysis models outline the potential benefits and costs of usability. This paper contrasts usability cost-benefit analysis literature with an empirical case in industrial setting, in which usability cost-benefit considerations (along with other usability activities) resulted in usability becoming a curse word. An interpretive case study was carried out in a SW development organization. Empirical analysis reveals that clearly divergent meanings and motives were attached to usability and its cost-benefit analysis in the organization. Increased sales and reduced development costs were strongly emphasized as benefits of better usability. However, very surprising meanings were attached to them both. Furthermore, the increased development costs associated with better usability were the main failure factor of the whole usability improvement effort. Implications both for theory and practice are discussed.

With best intentions: A Foucauldian examination on children’s genuine participation in ICT design

Purpose – Children have been recognized as an important user group for information and communication technology (ICT) and methods for involving them in ICT design have already been devised. However, there is a lack of research on children’s genuine or authentic participation in ICT design as well as a lack of critical research scrutinizing how “children” and “their participation” actually end up constructed in ICT design. The paper aims to discuss these issues. Design/methodology/approach – An intervention involving children in ICT design following the research strategy of nexus analysis was implemented. A qualitative data archive of this intervention is examined through a Foucauldian lens. Findings – The study reveals that numerous discourses were relied on when talking about “children” and “their participation” in the case project: the discourses of participation, equality, domination, segregation, rebellion, and patronization were identified. Moreover, “children” were constructed as equal partners and ...