4,309 research outputs found
Boundary Objects and their Use in Agile Systems Engineering
Agile methods are increasingly introduced in automotive companies in the
attempt to become more efficient and flexible in the system development. The
adoption of agile practices influences communication between stakeholders, but
also makes companies rethink the management of artifacts and documentation like
requirements, safety compliance documents, and architecture models.
Practitioners aim to reduce irrelevant documentation, but face a lack of
guidance to determine what artifacts are needed and how they should be managed.
This paper presents artifacts, challenges, guidelines, and practices for the
continuous management of systems engineering artifacts in automotive based on a
theoretical and empirical understanding of the topic. In collaboration with 53
practitioners from six automotive companies, we conducted a design-science
study involving interviews, a questionnaire, focus groups, and practical data
analysis of a systems engineering tool. The guidelines suggest the distinction
between artifacts that are shared among different actors in a company (boundary
objects) and those that are used within a team (locally relevant artifacts). We
propose an analysis approach to identify boundary objects and three practices
to manage systems engineering artifacts in industry
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
Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program
Software development projects have undergone remarkable changes with the
arrival of agile development methods. While intended for small, self-managing
teams, these methods are increasingly used also for large development programs.
A major challenge in programs is to coordinate the work of many teams, due to
high uncertainty in tasks, a high degree of interdependence between tasks and
because of the large number of people involved. This revelatory case study
focuses on how knowledge work is coordinated in large-scale agile development
programs by providing a rich description of the coordination practices used and
how these practices change over time in a four year development program with 12
development teams. The main findings highlight the role of coordination modes
based on feedback, the use of a number of mechanisms far beyond what is
described in practitioner advice, and finally how coordination practices change
over time. The findings are important to improve the outcome of large
knowledge-based development programs by tailoring coordination practices to
needs and ensuring adjustment over time.Comment: To appear in Project Management Journa
An agile information flow consolidator for delivery of quality software projects: technological perspective from a South African start-up
In today’s knowledge-based economy, modern organisations understand the importance of technology in their quest to be considered global leaders. South African markets like others worldwide are regularly flooded with the latest technology trends which can complicate the acquisition, use, management and maintenance of software. To achieve a competitive edge, companies tend to leverage agile methods with the best possible combination of innovative supporting tools as a key differentiator. Software technology firms are in this light faced with determining how to leverage technology and efficient development processes for them to consistently deliver quality software projects and solutions to their customer base.
Previous studies have discussed the importance of software development processes from a project management perspective. African academia has immensely contributed in terms of software development and project management research which has focused on modern frameworks, methodologies as well as project management techniques. While the current research continues with this tradition by presenting the pertinence of modern agile methodologies, it additionally further describes modern agile development processes tailored in a sub-Saharan context. The study also aims novelty by showing how innovative sometimes disruptive technology tools can contribute to producing African software solutions to African problems. To this end, the thesis contains an experimental case study where a web portal is prototyped to assist firms with the management of agile project management and engineering related activities.
Literature review, semi-structure interviews as well as direct observations from the industry use case are used as data sources. Underpinned by an Activity Theory analytical framework, the qualitative data is analysed by leveraging content and thematic oriented techniques.
This study aims to contribute to software engineering as well as the information systems body of knowledge in general. The research hence ambitions to propose a practical framework to promote the delivery of quality software projects and products.
For this thesis, such a framework was designed around an information system which helps organizations better manage agile project management and engineering related activities.Information SciencePh. D. (Information Systems
An Empirical Investigation of Pull Requests in Partially Distributed BizDevOps Teams
In globally distributed projects, virtual teams are often partially
dispersed. One common setup occurs when several members from one company work
with a large outsourcing vendor based in another country. Further, the
introduction of the popular BizDevOps concept has increased the necessity to
cooperate across departments and reduce the age-old disconnection between the
business strategy and technical development. Establishing a good collaboration
in partially distributed BizDevOps teams requires extensive collaboration and
communication techniques. Nowadays, a common approach is to rely on
collaboration through pull requests and frequent communication on Slack. To
investigate barriers for pull requests in distributed teams, we examined an
organization located in Scandinavia where cross-functional BizDevOps teams
collaborated with off-site team members in India. Data were collected by
conducting 14 interviews, observing 23 entire days with the team, and observing
37 meetings. We found that the pull-request approach worked very well locally
but not across sites. We found barriers such as domain complexity, different
agile processes (timeboxed vs. flow-based development), and employee turnover.
Using an intellectual capital lens on our findings, we discuss barriers and
positive and negative effects on the success of the pull-request approach
Learning in an Agile Setting: A Multilevel Study on the Evolution of Organizational Routines
Recognizing a serious lack of research on routinized individual actions and organizational adaptation in the stability-change paradox, we intend to provide an in-depth explanation of the way in which agile methods affect organizational learning in self-managed, team-based organizations, taking a multi-level evolutionary approach. We explore learning in agile organizations by breaking the analysis of organizational routines down into different levels \u2013 individual, team and organization \u2013 and describing the process of variation, selection and retention of routines at each level. Leveraging on multiple case studies, we discuss how team members learn and gain knowledge, from both direct and indirect experience, and analyze how teams develop conceptual frameworks and interpret those experiences. Finally, we discuss how organizational memory develops and how teams in agile organizations adapt simultaneously within an ecological structure that also comprises the changing environment. Our findings reveal substantial flaws in the capacity of agile methods to foster organizational learning
A discussion on the Role of People in Global Software Development.
Literature is producing a considerable amount of papers which focus on the risks, challenges and solutions of global software development (GSD). However, the influence of human factors on the success of GSD projects requires further study. The aim of our paper is twofold. First, to identify the challenges related to the human factors in GSD and, second, to propose the solution(s), which could help in solving or reducing the overall impact of these challenges. The main conclusions of this research can be valuable to organizations that are willing to achieve the quality objectives regarding GSD projects
- …