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

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

Scaling agile on large enterprise level – systematic bundling and application of state of the art approaches for lasting agile transitions

International audienceOrganizations are looking for ways of establishing agile and lean process for delivery. Many approaches exist in the form of frameworks, methods and tools to setup an individual composition for a best fit. The challenge is that large organizations are heterogeneous and diverse, and hence there is no "one size fits all" approach. To facilitate a systematic implementation of agile and lean, this article proposes a transition kit based on abstraction. This kit scouts and bundles state of the art methods and tools from the agile and lean community to align them with governance and compliance aspects of the specific enterprise. Coaching of the application of the transition kit ensures an adequate instantiation. The instantiation handles business domain specific aspects and standards. A coaching governance ensures continuous improvement. An example of the systematic application of the transition approach as well as its scaling is demonstrated through its application in the Volkswagen Group IT

Relationship of Transformational Leadership and Organizational Change During Enterprise Agile and DevOps Initiatives In Financial Service Firms

The rate of organizations adopting Agile and DevOps methodologies has grown in recent years, with researchers observing the impact of leadership styles and methodology adoption, presenting challenges with sustaining and scaling change initiatives. Where organizations within the marketplace today reveal the significance of leadership in influencing change, while findings signal deficiencies with having leaders who are ready. The purpose of this quantitative correlational research examines the increased probability of failure organizations face when engaging in enterprise Agile and DevOps transformational change initiatives. Through investigating the relationship between transformational leadership behaviors, readiness for change, and organizational citizenship behavior exhibited by management and employees engaging in Agile and DevOps initiatives within regional financial services companies with a presence in the South Eastern United States. The resulting study surveyed 390 anonymous participants with varying backgrounds and organizational roles based upon predetermined quota constraints aligning with the Bureau of Labor Statistics, U.S. Census, and FDIC data. Utilizing three principal instruments to measure transformational leadership, change readiness, and organizational citizenship behavior; conducting statistical analysis for construct reliability, descriptive properties, and hypothesis testing, concluding the existence of influential correlation of change readiness and organizational citizenship behaviors having a relationship with transformational leadership. The research findings identify the association of organizational readiness and employee social citizenship responsibility with applicability to transformational leadership, bringing light to the significance of grooming and sustaining leaders at all levels of the organization

Are Product Owners communicators? A multi-method research approach to provide a more comprehensive picture of Product Owners in practice

Product Owners have an important role in the agile and hybrid software development process. While this role is supposed to maximize the value of a product, there seem to be several scattered results on how they achieve this, as well as what actually constitutes this role in practice. To consolidate current research results and to further analyze the key attribute of Product Owners, we conducted a multi-method research approach spanning a systematic mapping study and a consecutive case study in a hybrid development environment. The results of the mapping study states that Product Owners are communicators. We further investigated on this and used the shadowing technique to observe three Product Owners' communication activities. The results support that statement, as the gained data reveal that Product Owners spend 65% of their time in meetings. But rather than just providing the team with the necessary requirements for the product under development, Product Owners need this time to synchronize and align their work, streamline the agile process of large-scale Scrum, discuss team-based topics, and to solve upcoming issues addressed by the team. These results contribute to draw a more comprehensive picture of the important but yet complex role of Product Owners in practice. © 2020 John Wiley & Sons, Ltd

Toward a Metric Catalog for Large-Scale Agile Development

Nowadays, organizations use agile software development to remain competitive in their frequently changing business environment. Inspired by the success of agile methods on a small scale, organizations have started to apply them in larger contexts. However, the limited scalability of agile methods is a problem. Metrics can be a success factor for achieving agility at scale, thus adopting them is promising. Most scaling agile frameworks provide few recommendations regarding metrics. Likewise, research on metrics in large-scale agile development lacks concrete guidance for metrics or their organization-specific adoption. To fill this gap, we propose two artifacts. We present the design of a minimalistic metric management fact sheet (MMFS) for large-scale agile development to support practitioners in using metrics in their organization-specific development environment. Furthermore, the MMFS is the basis for our metric catalog documenting 196 metrics identified in an expert study to provide a comprehensive metric set for scaling agile environments