Future software organizations – agile goals and roles

Peer reviewe

AGILE PORTFOLIO MANAGEMENT: DESIGN GOALS AND PRINCIPLES

Digital transformation and the resulting volatile and unpredictable business environments challenge traditional enterprises to continuously fulfill and surpass customers’ expectations. They need to become agile in its organization by proactively sensing the unpredictable change and responding accordingly with speed and dexterity. While many organizations are quite advanced in realizing adaptivity at the operational level, strategic agility in general and in portfolio management in particular as linking op-erations and strategy for satisfying the customer needs is in its nascence. To identify the baseline for portfolio management for achieving agility, we derive four design goals for an effective agile portfolio management system, six design principles on how to achieve these goals and show an exemplary setup with design features. Our results are based on a research study with empirical insights from six com-panies and theoretical input from thirteen existing case studies and eight frameworks for scaling agility to the portfolio level. By deriving design principles for an agile portfolio management system, our work closes a gap in existing research, which focuses on principles for adaptive IT portfolio management processes instead of proactive enterprise systems, insights on individual portfolio practices or non-generalizable blueprints for an agile organizational setup without showing alternative approaches

Guest Editorial: Agile beyond software - In search of flexibility in a wide range of innovation projects and industries

The nine papers in this special section focus on new developments in agile software and reports on applications for its use. A key aspect for the extensive use of agile software is that it supports developers with coping with the growing uncertainty and turbulence in technological and market environments. Feedback and change are at the core of Agile for a dynamic, evolving, and organic, rather than static, predefined, and mechanistic development process advocated by waterfall management. To create timely, high-quality, cost-efficient, and innovative solutions, Agile developers organized in small, colocated, autonomous teams, build and test software in rapid iterative cycles, actively involving users to gather feedback, updating the project scope, and plan “on-the-fly,” using face-to-face communication as opposed to documentation. These papers contribute to the state-of-the-art of agile research by offering a rich, up-todate account of the dynamics occurring when expanding Agile into “not-just-software” contexts of the key challenges and perils related to the scaling and of the possible solutions to them

Model-driven Test Engineering: A Practical Analysis in the AQUA-WS Project

The effective application of test phases has been one of the most relevant, critical and cost phases in the life cycle of software projects in the last years. During the test phase, the test team has to assure the quality of the system and the concordance with the initial requirements of the system. The model driven paradigm is offering suitable results in some areas and the test phase could be one of them. This paper presents how the application of this paradigm can help to improve this aspect in the functional test generation and it analyses the experience in a real project developed under this approach.Ministerio de Ciencia e Innovación TIN2010-20057-C03-02Ministerio de Ciencia e Innovación TIN 2010-12312-EJunta de Andalucía TIC-578

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

Improving Digital-Enabled Strategic Agility with Enterprise Strategy SaaS Platform Affordances: A Manufacturing Perspective

Strategic Agility allows organizations to rapidly respond to market movements and integrate these opportunities into their organization. Open Strategy, utilizing frameworks such as Objectives and Key Results, increases Strategic Agility by enhancing transparency and inclusiveness in strategy development and execution. However, leaders lack effective digital tools to rapidly align organizations at scale and track progress, especially when creating Strategic Agility. To address this, Enterprise Strategy SaaS Platforms (Strategy SaaS), a new breed of strategy software, is being developed to facilitate Digital-Enabled Strategic Agility (DESA). This research explores the enablers of Strategy SaaS adoption and its impact on DESA through two manufacturing cases using Integrated Affordance Theory. Results indicate Strategy SaaS enables organizations to sense, decide, coordinate, and act on their Open Strategy initiatives more effectively. However, it also requires additional enablers due to the business-led nature of implementation. The research contributes a tangible action plan for leaders to increase DESA

Finnish Enterprise Agile Transformations : A Survey Study

Peer reviewe

Putting Teeth into Open Architectures: Infrastructure for Reducing the Need for Retesting

Proceedings Paper (for Acquisition Research Program)The Navy is currently implementing the open-architecture framework for developing joint interoperable systems that adapt and exploit open-system design principles and architectures. This raises concerns about how to practically achieve dependability in software-intensive systems with many possible configurations when: 1) the actual configuration of the system is subject to frequent and possibly rapid change, and 2) the environment of typical reusable subsystems is variable and unpredictable. Our preliminary investigations indicate that current methods for achieving dependability in open architectures are insufficient. Conventional methods for testing are suited for stovepipe systems and depend strongly on the assumptions that the environment of a typical system is fixed and known in detail to the quality-assurance team at test and evaluation time. This paper outlines new approaches to quality assurance and testing that are better suited for providing affordable reliability in open architectures, and explains some of the additional technical features that an Open Architecture must have in order to become a Dependable Open Architecture.Naval Postgraduate School Acquisition Research ProgramApproved for public release; distribution is unlimited