A study of the Scrum Master’s role

Scrum is an increasingly common approach to software development adopted by organizations around the world. However, as organizations transition from traditional plan-driven development to agile development with Scrum, the question arises as to which Scrum role (Product Owner, Scrum Master, or Scrum Team Member) corresponds to a Project Manager, or conversely which Scrum role should the Project Managers adopt? In an attempt to answer this question, we adopted a mixed-method research approach comprising a systematic literature review and embedded case study of a commercial software development team. Our research has identified activities that comprise the Scrum Master role, and which additional roles are actually performed by Scrum Masters in practice. We found nine activities that are performed by Scrum Masters. In addition, we found that Scrum Masters also perform other roles, most importantly as Project Managers. This latter situation results in tension and conflict of interest that could have a negative impact on the performance of the team as a whole. These results point to the need to re-assess the role of Project Managers in organizations that adopt Scrum as a development approach. We hypothesize that it might be better for Project Managers to become Product Owners, as aspects of this latter role are more consistent with the traditional responsibilities of a Project Manager

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

Enhancing students’ motivation to learn software engineering programming techniques: a collaborative and social interaction approach

To motivate students to study advanced programming techniques, including the use of architectural styles such as the model–view–controller pattern, we have con-ducted action research upon a project based-learning approach. In addition to collabo-ration, the approach includes students’ searching and analysis of scientific documents and their involvement in communities of practice outside academia. In this paper, we report the findings of second action research cycle, which took place throughout the fourth semester of a six-semester program. As with the previous cycle during the pre-vious academic year, students did not satisfactorily achieve expected learning out-comes. More groups completed the assigned activities, but results continue to reflect poor engagement in the communities of practice and very low performance in other learning tasks. From the collected data we have identified new approaches and recom-mendations for subsequent research.Fundação para a Ciência e Tecnologia (FCT), Portugal, for Ph.D. Grants SFRH/BD/91309/2012 and SFRH/BD/87815/201

Clinical profiles of patients colonized or infected with extended-spectrum beta-lactamase producing Enterobacteriaceae isolates: a 20 month retrospective study at a Belgian University Hospital

<p>Abstract</p> <p>Background</p> <p>Description of the clinical pictures of patients colonized or infected by ESBL-producing <it>Enterobacteriaceae </it>isolates and admitted to hospital are rather scarce in Europe. However, a better delineation of the clinical patterns associated with the carriage of ESBL-producing isolates may allow healthcare providers to identify more rapidly at risk patients. This matter is of particular concern because of the growing proportion of ESBL-producing <it>Enterobacteriaceae </it>species isolates worldwide.</p> <p>Methods</p> <p>We undertook a descriptive analysis of 114 consecutive patients in whom ESBL-producing <it>Enterobacteriaceae </it>isolates were collected from clinical specimens over a 20-month period. Clinical data were obtained through retrospective analysis of medical record charts. Microbiological cultures were carried out by standard laboratory methods.</p> <p>Results</p> <p>The proportion of ESBL-producing <it>Enterobacteriaceae </it>strains after exclusion of duplicate isolates was 4.5% and the incidence rate was 4.3 cases/1000 patients admitted. Healthcare-associated acquisition was important (n = 104) while community-acquisition was less frequently found (n = 10). Among the former group, two-thirds of the patients were aged over 65 years and 24% of these were living in nursing homes. Sixty-eight (65%) of the patients with healthcare-associated ESBL, were considered clinically infected. In this group, the number and severity of co-morbidities was high, particularly including diabetes mellitus and chronic renal insufficiency. Other known risk factors for ESBL colonization or infection such as prior antibiotic exposure, urinary catheter or previous hospitalisation were also often found. The four main diagnostic categories were: urinary tract infections, lower respiratory tract infections, septicaemia and intra-abdominal infections. For hospitalized patients, the median hospital length of stay was 23 days and the average mortality rate during hospitalization was 13% (Confidence Interval 95%: 7-19). <it>Escherichia coli</it>, by far, accounted as the most common ESBL-producing <it>Enterobacteriaceae </it>species (77/114; [68%]) while CTX-M-1 group was by far the most prevalent ESBL enzyme (n = 56).</p> <p>Conclusion</p> <p>In this retrospective study, the clinical profiles of patients carrying healthcare-associated ESBL-producing <it>Enterobacteriacae </it>is characterized by a high prevalence rate of several major co-morbidities and potential known risk factors. Both, the length of hospital stay and overall hospital mortality rates were particularly high. A prospective case-control matched study should be designed and performed in order to control for possible inclusion bias.</p

Efficacy of Infection Control Interventions in Reducing the Spread of Multidrug-Resistant Organisms in the Hospital Setting

Multidrug-resistant organisms (MDRO) continue to spread in hospitals globally, but the population-level impact of recommended preventive strategies and the relative benefit of individual strategies targeting all MDRO in the hospital setting are unclear. To explore the dynamics of MDRO transmission in the hospital, we develop a model extending data from clinical individual-level studies to quantify the impact of hand hygiene, contact precautions, reducing antimicrobial exposure and screening surveillance cultures in decreasing the prevalence of MDRO colonization and infection. The effect of an ongoing increase in the influx of patients colonized with MDRO into the hospital setting is also quantified. We find that most recommended strategies have substantial effect in decreasing the prevalence of MDRO over time. However, screening for asymptomatic MDRO colonization among patients who are not receiving antimicrobials is of minimal value in reducing the spread of MDRO

Project management between will and representation

This article challenges some deep-rooted assumptions of project management. Inspired by the work of the German philosopher, Arthur Schopenhauer, it calls for looking at projects through two complementary lenses: one that accounts for cognitive and representational aspects and one that accounts for material and volitional aspects. Understanding the many ways in which these aspects transpire and interact in projects sheds new light on project organizations, as imperfect and fragile representations that chase a shifting nexus of intractable human, social, technical, and material processes. This, in turn, can bring about a new grasp of notions such as value,\ud knowledge, complexity, and risk

Cargo Cults in Information Systems Development: a Definition and an Analytical Framework

Organizations today adopt agile information systems development methods (ISDM), but many do not succeed with the adoption process and in achieving desired results. Systems developers sometimes fail in efficient use of ISDM, often due to a lack of understanding the fundamental intentions of the chosen method. In many cases organizations simply imitate the behavior of others without really understanding why. This conceptual paper defines this phenomenon as an ISDM cargo cult behavior and proposes an analytical framework to identify such situations. The concept of cargo cults originally comes from the field of social anthropology and has been used to explain irrational, ritualistic imitation of certain behavior. By defining and introducing the concept in the field of information systems development we provide a diagnostic tool to better understand one of the reasons why ISDM adoption sometimes fail