Is Work System Theory a Practical Theory of Practice?

This paper describes an exploration of whether ideas related to pragmatism, practical theory, and practice theory provide potentially useful directions for extending work system theory (WST), which is an outgrowth of an attempt to develop the work system method (WSM), a flexible systems analysis method for business professionals. After summarizing WST’s basic premises and its two central frameworks, this paper uses a positioning map to explain reasons for considering relationships between WST and a number of topics related to practical issues and practice theory. Based on that positioning map, the subsequent sections discuss relation-ships between WST and UML, Goldkuhl’s workpractice theory, and the more general notion of practice theory. A concluding section briefly addresses a set of questions related to whether WST is a practical theory of practice. This paper\u27s comparisons of WST with the three theoret-ical perspectives for describing and understanding systems could be a step toward greater practical application of IS research related to the nature and evolution of activities, processes, routines, and practices involving the use of technology in organizational settings

How Does the Lens of Pragmatism Help in Understanding, Using, or Improving Work System Theory?

This paper explores linkages between work system theory (WST) and central concerns of the SIGPrag community related to theorizing the IT artifact and its organizational and societal context. The first part of the paper provides background about the development, basic ideas, and underlying premises of WST. In addition to summarizing older facets of WST, it summarizes three new extensions of WST, a service value chain framework for looking at service systems in terms of service concepts, a metamodel (Alter, 2010a) for looking at work systems in more depth than is supported easily by the work system framework, and a concept classification matrix (Alter, 2010e) that can support analysis and design activities and that might provide a way to organize a body of knowledge for the IS field. The second part of the paper returns to the questions about the fit and synergy between WST and the interests of the SIGPrag community. While it is clear that WST fits with central themes in pragmatist IS interests and research, such as usefulness, action, change, and knowledge, the potential synergy between WST and existing research topics in the SIGPrag community is not obvious

A Workaround Design System for Anticipating, Designing, and/or Preventing Workarounds

Idealized system design produces requirements reflecting management intentions and “best practices.” This paper proposes a workaround design system (WDS) for anticipating, designing, and/or preventing workarounds that bypass systems as designed. A WDS includes a process and an interactive “workaround design tool” (WDT) for identifying and evaluating foreseeable workarounds based on work system theory and a theory of workarounds. This paper summarizes the conceptual background and explains the form, use, and implications of the proposed WDS and WDT. The idea of WDS addresses significant gaps in practice and research. Designers should have methods for identifying likely obstacles and anticipating and evaluating a non-trivial percentage of plausible workarounds. Methods for identifying workarounds might help in training work system participants. Researchers might use WDS to explore why specific responses to obstacles did or did not occur. The lack of methods related to anticipating, designing or preventing workarounds implies that WDS may prove fruitful even though it is impossible to anticipate all possible workarounds

Nothing Is More Practical than a Good Theory … except possibly a Good Paradigm or Framework or Model or Metaphor

This research questions the frequently repeated, taken-for-granted aphorism that “there is nothing more practical than a good theory.” It seeks to demonstrate that there is no reason to believe that theory is more practical than good paradigms, frameworks, models, metaphors or good versions of other conceptual artifacts. It identifies different types of conceptual artifacts along with nine criteria for evaluating conceptual artifacts. It validates four premises related conceptual artifacts by examining different types of conceptual artifacts associated with work system theory (WST)

Customized agile development process for embedded software development

Agile software development has grown in popularity starting from the agile manifesto declared in 2001. However there is a strong belief that the agile methods are not suitable for embedded, critical or real-time software development, even though multiple studies and cases show differently. This thesis will present a custom agile process that can be used in embedded software development. The reasons for presumed unfitness of agile methods in embedded software development have mainly based on the feeling of these methods providing no real control, no strict discipline and less rigor engineering practices. One starting point is to provide a light process with disciplined approach to the embedded software development. Agile software development has gained popularity due to the fact that there are still big issues in software development as a whole. Projects fail due to schedule slips, budget surpassing or failing to meet the business needs. This does not change when talking about embedded software development. These issues are still valid, with multiple new ones rising from the quite complex and hard domain the embedded software developers work in. These issues are another starting point for this thesis. The thesis is based heavily on Feature Driven Development, a software development methodology that can be seen as a runner up to the most popular agile methodologies. The FDD as such is quite process oriented and is lacking few practices considered commonly as extremely important in agile development methodologies. In order for FDD to gain acceptance in the software development community it needs to be modified and enhanced. This thesis presents an improved custom agile process that can be used in embedded software development projects with size varying from 10 to 500 persons. This process is based on Feature Driven Development and by suitable parts to Extreme Programming, Scrum and Agile Modeling. Finally this thesis will present how the new process responds to the common issues in the embedded software development. The process of creating the new process is evaluated at the retrospective and guidelines for such process creation work are introduced. These emphasize the agility also in the process development through early and frequent deliveries and the team work needed to create suitable process.Siirretty Doriast

Nothing is more practical than a good conceptual artifact... which may be a theory, framework, model, metaphor, paradigm or perhaps some other abstraction

This research commentary proposes a way to make progress in the IS discipline’s inconclusive discussion about the nature and role of theory. In some ways, the creation and testing of theory seems to be the primary goal of IS research. Despite that, there are persistent questions whether theory has become a fetish in the IS discipline and whether the routinized production and testing of mid-range theories is little more than an uninspired script that reduces the value and interest of IS research. This paper reframes the discussion around the idea of ‘conceptual artifact’ that has been discussed widely in educational psychology for over a decade. Conceptual artifacts are abstract knowledge objects that can be produced, tested and improved. This paper recognizes the value of both abstract knowledge (conceptual artifacts) and non-abstract knowledge. It explains that theorizing produces, evaluates or improves useful conceptual artifacts that may or may not be theories. It validates four premises related to conceptual artifacts by showing that theorizing related to work system theory created or used many different types of conceptual artifacts. It identifies nine criteria for evaluating conceptual artifacts and shows that some of them differ from typical criteria for evaluating Gregor Type IV theories. As a whole, it argues that that privileging theory over other types of conceptual artifacts may not be beneficial in pursuing the research questions that the IS discipline needs to study

Theory of Workarounds

Although mentioned frequently in the organization, management, public administration, and technology literatures, workarounds are understudied and undertheorized. This article provides an integrated theory of workarounds that describes how and why workarounds are created. The theory covers most types of workarounds and most situations in which workarounds occur in operational systems. This theory is based on a broad but useful definition of workaround that clarifies the preconditions for the occurrence of a workaround. The literature review is organized around a diagram that combines the five “voices” in the literature of workarounds. That diagram is modeled after the diagram summarizing Orton and Weick’s [1990] loose coupling theory, which identified and combined five similar voices in the literature about loose coupling. Building on that basis, the theory of workarounds is a process theory driven by the interaction of key factors that determine whether possible workarounds are considered and how they are executed. This theory is useful for classifying workarounds and analyzing how they occur, for understanding compliance and noncompliance to methods and management mandates, for incorporating consideration of possible workarounds into systems analysis and design, and for studying how workarounds and other adaptations sometimes lead to larger planned changes in systems

Using ontology for the representational analysis of process modelling techniques

Selecting an appropriate business process modelling technique forms an important task within the methodological challenges of a business process management project. While a plethora of available techniques has been developed over the last decades, there is an obvious shortage of well-accepted reference frameworks that can be used to evaluate and compare the capabilities of the different techniques. Academic progress has been made at least in the area of representational analyses that use ontology as a benchmark for such evaluations. This paper reflects on the comprehensive experiences with the application of a model based on the Bunge ontology in this context. A brief overview of the underlying research model characterizes the different steps in such a research project. A comparative summary of previous representational analyses of process modelling techniques over time gives insights into the relative maturity of selected process modelling techniques. Based on these experiences suggestions are made as to where ontology-based representational analyses could be further developed and what limitations are inherent to such analyses