Search

The competition in the software market demands that the time required for any software product to reach the market be reduced if the product is to survive competition from other developers. The pursuit of this goal has led to the adoption of agile software development methodologies. While other agile methodologies provide guidelines as to the software engineering (SE) practices to be used during the development lifecycle, Scrum does not. The purpose of this study is twofold: first, to identify the usage and level of importance of software engineering practices in the Scrum development environment; and second, to investigate how Scrum teams adopt an appropriate set of SE techniques and whether a hybrid Scrum/Extreme Programming (XP) methodology is an appropriate approach to take. This research was conducted by examining sample data from five organizations using the Scrum methodology. The sample included a range of industries including communications and embedded systems, financial asset management, software development houses and consulting firms in South Africa. The study employed a mixed method approach. A key finding was that, regardless of the fact that Scrum does not explicitly recommend engineering practices, there was extensive use of these practices by all of the participating organizations. The study also found that the lack of software engineering practices in Scrum does not constitute a barrier to a successful adoption of Scrum, provided the 'inspect and adapt' principle inherent in Scrum is properly followed. The study discusses the findings, explains the implications and suggests future research. [ABSTRACT FROM AUTHOR]

The Agile approach and tools are popular for the management of Enterprise Application Software (EAS) development. This article focuses on the issue of inconsistency between strategic business objectives and the functionality of the software developed. Agile management tools lack the functionality of EAS project activities coordination. This article aims to rethink Agile project management using the causal modelling approach. A causal model of Agile project management using a management transaction (MT) concept was developed. The notion of the space of processes was used to identify the MTs location along the axes of aggregation, generalization, and time and to formalize their interaction specifications. Taxonomy of the coordination meta-types and types was developed using the identifiers of the MTs. The modified Agile activities hierarchy was developed, and vertical and horizontal causal interactions between Agile activities were identified. This modified Agile management model helps to consistently track the integrity of EAS project content. Complexity indicators were introduced to evaluate the EAS project complexity and their average and normalized values are presented. Additional attributes in the Agile management tool Jira are proposed. Monitoring mismatch between strategic business objectives and development activities content helps to improve the success of EAS projects delivery. [ABSTRACT FROM AUTHOR]

The social revolution of the Web 2.0 is changing learning and management processes: In the field of learning, concepts like e-learning 2.0 and connectivism have emerged. Within the field of management theory, approaches like Agile Management have been developed. E-learning 2.0, Connectivism and concepts like Agile Management are based on a dialogical communication, which is a feature of the Digital Age. But at the same time these concepts share neoliberal implications. To provide a foundation for this thesis, the article provides, besides an introduction (1), a definition of the term Digital Age (2). Afterwards e-learning 2.0 and Connectivism (3) and Agile Management (4) are introduced as dialogical forms of digital based communication which emerged within the Digital Age. With reference to the neoliberal concepts of the subject it's possible to identify the underlying neoliberal structures of E-Learning 2.0, Connectivism and Agile Management (5). The dialogical and emancipative aspects of these approaches turn in to a repressive social dynamic which require a neoliberal self-optimization of the subject. This aspect is discussed within the conclusion (6). [ABSTRACT FROM AUTHOR]

In this introduction to the special theme: Project Management in e-Science: Challenges and Opportunities, we argue that the role of project management and different forms of leadership and facilitation can influence significantly the nature of cooperation and its outcomes and deserves further research attention. The quality of social interactions such as communication, cooperation, and coordination, have emerged as key factors in developing and deploying e-science infrastructures and applications supporting large-scale and distributed collaborative scientific research. If software is seen to embody the relational web within which it evolves, and if the processes of software design, development and deployment are seen as ongoing transformations of this dynamic web of relationships between technology, people and environment, the role of managers becomes crucial: it is their responsibility to balance and facilitate the dynamics of these relationships. [ABSTRACT FROM AUTHOR]