Systems development methods and usability in Norway: An industrial perspective

This is the post-print version of the Article. The official published version can be accessed from the link below - Copyright @ 2007 Springer Berlin HeidelbergThis paper investigates the relationship between traditional systems development methodologies and usability, through a survey of 78 Norwegian IT companies. Building on previous research we proposed two hypotheses; (1) that software companies will generally pay lip service to usability, but do not prioritize it in industrial projects, and (2) that systems development methods and usability are perceived as not being integrated. We find support for both hypotheses. Thus, the use of systems development methods is fairly stable, confirming earlier research. Most companies do not use a formal method, and of those who do, the majority use their own method. Generally, the use of methods is rather pragmatic: Companies that do not use formal methods report that they use elements from such methods. Further, companies that use their own method import elements from standardised methods into their own

Business Value Is not only Dollars - Results from Case Study Research on Agile Software Projects

Business value is a key concept in agile software development. This paper presents results of a case study on how business value and its creation is perceived in the context of agile projects. Our overall conclusion is that the project participants almost never use an explicit and structured approach to guide the value creation throughout the project. Still, the application of agile methods in the studied cases leads to satisfied clients. An interesting result of the study represents the fact that the agile process of many projects differs significantly from what is described in the agile practitioners’ books as best practices. The key implication for research and practice is that we have an incentive to pursue the study of value creation in agile projects and to complement it by providing guidelines for better client’s involvement, as well as by developing structured methods that will enhance the value-creation in a project

Influential factors of aligning Spotify squads in mission-critical and offshore projects – a longitudinal embedded case study

Changing the development process of an organization is one of the toughest and riskiest decisions. This is particularly true if the known experiences and practices of the new considered ways of working are relative and subject to contextual assumptions. Spotify engineering culture is deemed as a new agile software development method which increasingly attracts large-scale organizations. The method relies on several small cross-functional self-organized teams (i.e., squads). The squad autonomy is a key driver in Spotify method, where a squad decides what to do and how to do it. To enable effective squad autonomy, each squad shall be aligned with a mission, strategy, short-term goals and other squads. Since a little known about Spotify method, there is a need to answer the question of: How can organizations work out and maintain the alignment to enable loosely coupled and tightly aligned squads? In this paper, we identify factors to support the alignment that is actually performed in practice but have never been discussed before in terms of Spotify method. We also present Spotify Tailoring by highlighting the modified and newly introduced processes to the method. Our work is based on a longitudinal embedded case study which was conducted in a real-world large-scale offshore software intensive organization that maintains mission-critical systems. According to the confidentiality agreement by the organization in question, we are not allowed to reveal a detailed description of the features of the explored project

Historical roots of Agile methods: where did “Agile thinking” come from?

The appearance of Agile methods has been the most noticeable change to software process thinking in the last fifteen years [16], but in fact many of the “Agile ideas” have been around since 70’s or even before. Many studies and reviews have been conducted about Agile methods which ascribe their emergence as a reaction against traditional methods. In this paper, we argue that although Agile methods are new as a whole, they have strong roots in the history of software engineering. In addition to the iterative and incremental approaches that have been in use since 1957 [21], people who criticised the traditional methods suggested alternative approaches which were actually Agile ideas such as the response to change, customer involvement, and working software over documentation. The authors of this paper believe that education about the history of Agile thinking will help to develop better understanding as well as promoting the use of Agile methods. We therefore present and discuss the reasons behind the development and introduction of Agile methods, as a reaction to traditional methods, as a result of people's experience, and in particular focusing on reusing ideas from histor

Scaling up the Planning Game: Collaboration Challenges in Large-Scale Agile Product Development

One of the benefits of agile is close collaboration of customer and developer. This ensures good commitment and excellent knowledge flows of information about priorities and efforts. However, it is unclear if this benefit can be leveraged at scale. Clearly, it is infeasible to use practices such as planning game with several agile teams in the room. In this paper, we investigate how a large-scale agile organization manages, what challenges exist, and which opportunities can be leveraged. We found challenges in three areas: (i) the abil-ity to estimate, prioritize, and plan; (ii) the context of planning with respect to working environment, team build-up, and team spirit; and (iii) the ceremonial agreement which promises to allow leveraging abilities in a given context

Self-similar disk packings as model spatial scale-free networks

The network of contacts in space-filling disk packings, such as the Apollonian packing, are examined. These networks provide an interesting example of spatial scale-free networks, where the topology reflects the broad distribution of disk areas. A wide variety of topological and spatial properties of these systems are characterized. Their potential as models for networks of connected minima on energy landscapes is discussed.Comment: 13 pages, 12 figures; some bugs fixed and further discussion of higher-dimensional packing

Autoreactivity and Exceptional CDR Plasticity (but Not Unusual Polyspecificity) Hinder Elicitation of the Anti-HIV Antibody 4E10

The broadly-neutralizing anti-HIV antibody 4E10 recognizes an epitope in the membrane-proximal external region of the HIV envelope protein gp41. Previous attempts to elicit 4E10 by vaccination with envelope-derived or reverse-engineered immunogens have failed. It was presumed that the ontogeny of 4E10-equivalent responses was blocked by inherent autoreactivity and exceptional polyreactivity. We generated 4E10 heavy-chain knock-in mice, which displayed significant B cell dysregulation, consistent with recognition of autoantigen/s by 4E10 and the presumption that tolerance mechanisms may hinder the elicitation of 4E10 or 4E10-equivalent responses. Previously proposed candidate 4E10 autoantigens include the mitochondrial lipid cardiolipin and a nuclear splicing factor, 3B3. However, using carefully-controlled assays, 4E10 bound only weakly to cardiolipin-containing liposomes, but also bound negatively-charged, non-cardiolipin-containing liposomes comparably poorly. 4E10/liposome binding was predominantly mediated by electrostatic interactions rather than presumed hydrophobic interactions. The crystal structure of 4E10 free of bound ligands showed a dramatic restructuring of the combining site, occluding the HIV epitope binding site and revealing profound flexibility, but creating an electropositive pocket consistent with non-specific binding of phospholipid headgroups. These results strongly suggested that antigens other than cardiolipin mediate 4E10 autoreactivity. Using a synthetic peptide library spanning the human proteome, we determined that 4E10 displays limited and focused, but unexceptional, polyspecificity. We also identified a novel autoepitope shared by three ER-resident inositol trisphosphate receptors, validated through binding studies and immunohistochemistry. Tissue staining with 4E10 demonstrated reactivity consistent with the type 1 inositol trisphosphate receptor as the most likely candidate autoantigen, but is inconsistent with splicing factor 3B3. These results demonstrate that 4E10 recognition of liposomes competes with MPER recognition and that HIV antigen and autoepitope recognition may be distinct enough to permit eliciting 4E10-like antibodies, evading autoimmunity through directed engineering. However, 4E10 combining site flexibility, exceptional for a highly-matured antibody, may preclude eliciting 4E10 by conventional immunization strategies

Some Findings Concerning Requirements in Agile Methodologies

gile methods have appeared as an attractive alternative to conventional methodologies. These methods try to reduce the time to market and, indirectly, the cost of the product through flexible development and deep customer involvement. The processes related to requirements have been extensively studied in literature, in most cases in the frame of conventional methods. However, conclusions of conventional methodologies could not be necessarily valid for Agile; in some issues, conventional and Agile processes are radically different. As recent surveys report, inadequate project requirements is one of the most conflictive issues in agile approaches and better understanding about this is needed. This paper describes some findings concerning requirements activities in a project developed under an agile methodology. The project intended to evolve an existing product and, therefore, some background information was available. The major difficulties encountered were related to non-functional needs and management of requirements dependencies

Ontogeny of Recognition Specificity and Functionality for the Broadly Neutralizing Anti-HIV Antibody 4E10

The process of antibody ontogeny typically improves affinity, on-rate, and thermostability, narrows polyspecificity, and rigidifies the combining site to the conformer optimal for binding from the broader ensemble accessible to the precursor. However, many broadly-neutralizing anti-HIV antibodies incorporate unusual structural elements and recognition specificities or properties that often lead to autoreactivity. The ontogeny of 4E10, an autoreactive antibody with unexpected combining site flexibility, was delineated through structural and biophysical comparisons of the mature antibody with multiple potential precursors. 4E10 gained affinity primarily by off-rate enhancement through a small number of mutations to a highly conserved recognition surface. Controverting the conventional paradigm, the combining site gained flexibility and autoreactivity during ontogeny, while losing thermostability, though polyspecificity was unaffected. Details of the recognition mechanism, including inferred global effects due to 4E10 binding, suggest that neutralization by 4E10 may involve mechanisms beyond simply binding, also requiring the ability of the antibody to induce conformational changes distant from its binding site. 4E10 is, therefore, unlikely to be re-elicited by conventional vaccination strategies

Cerebral organoids derived from Sandhoff disease-induced pluripotent stem cells exhibit impaired neurodifferentiation

Sandhoff disease, one of the GM2 gangliosidoses, is a lysosomal storage disorder characterized by the absence of beta-hexosaminidase A and B activity and the concomitant lysosomal accumulation of its substrate, GM2 ganglioside. It features catastrophic neurodegeneration and death in early childhood. How the lysosomal accumulation of ganglioside might affect the early development of the nervous system is not understood. Recently, cerebral organoids derived from induced pluripotent stem (iPS) cells have illuminated early developmental events altered by disease processes. To develop an early neurodevelopmental model of Sandhoff disease, we first generated iPS cells from the fibroblasts of an infantile Sandhoff disease patient, then corrected one of the mutant HEXB alleles in those iPS cells using CRISPR/Cas9 genome-editing technology, thereby creating isogenic controls. Next, we used the parental Sandhoff disease iPS cells and isogenic HEXB-corrected iPS cell clones to generate cerebral organoids that modeled the first trimester of neurodevelopment. The Sandhoff disease organoids, but not the HEXB-corrected organoids, accumulated GM2 ganglioside and exhibited increased size and cellular proliferation compared with the HEXB-corrected organoids. Whole-transcriptome analysis demonstrated that development was impaired in the Sandhoff disease organoids, suggesting that alterations in neuronal differentiation may occur during early development in the GM2 gangliosidoses