A Lean Enterprise Architecture Approach as an Enabler for Organizational Agility : Case: Metso Outotec

In the era where delivery speed is perceived more important than IT landscape integration, consistency and long-term planning, different architectural approaches have become important considerations of information systems management. Moreover, recent studies have shown that the need for a holistic EA is often overlooked, when organizations try to apply agile development models, which may lead to several problems, such as technical debt, redundant rework, inconsistent communication, decentralized and siloed architecture design, unsustainable architecture, and inconsistence in coding style. Hence, with the growing deployment of scaling agile methods there is a need for purpose-fit approaches to integrate EA frameworks to enable organization agility while maintaining long-term vision. This study aims to explore how EA activities are put into practices in a company deploying large-scale agile development methods – namely EA deliverables, EA benefits, EA concerns and EA enablers. In total, 13 semi-structured interviews were conducted from a case company, and an analysis was done using the Gioia method. As a result, EA deliverables (business objective deliverables, intentional architecture deliverables, and emergent design deliverables), EA benefits (organizational agility and organizational robustness), EA concerns (immaturity, disengagement, urgency, and resistance and anti-patterns), and EA enablers (communication and collaboration, Lean EA, and EA culture) were identified. The enterprise architecture practices used by the case company were in line with the guidelines and best practices recommended by the literature and industry experts. Moreover, a literature review provided some theoretical constructs and suggestions, namely the Lean EA development (LEAD) method and the design principles of architectural thinking for supporting organizational agility, which can be recommended to be applied by the case company or any other organization scaling agile

DevOps for Digital Leaders

DevOps; continuous delivery; software lifecycle; concurrent parallel testing; service management; ITIL; GRC; PaaS; containerization; API management; lean principles; technical debt; end-to-end automation; automatio

Web Engineering Security (WES) Methodology

The impact of the World Wide Web on basic operational economical components in global information-rich civilizations is significant. The repercussions force organizations to provide justification for security from a business-case perspective and to focus on security from a Web application development environment standpoint. The need for clarity promoted an investigation through the acquisition of empirical evidence from a high level Web survey and a more detailed industry survey to analyze security in the Web application development environment ultimately contributing to the proposal of the Essential Elements (EE) and the Security Criteria for Web Application Development (SCWAD). The synthesis of information provided was used to develop the Web Engineering Security (WES) methodology. WES is a proactive, flexible, process neutral security methodology with customizable components that is based on empirical evidence and used to explicitly integrate security throughout an organization’s chosen application development process

Governança ágil em TIC: rompendo paradigmas

This paper presents the basis of the Agile Governance in Information and Communication Technology (ICT), which is based on Agile Software Engineering Methodologies principles and values. Its development was done through a systematic review process, supported by Bibliometrics and Scientometrics methods and techniques, where the Critical Success Factors (CSF) of ICT Governance projects and the principles of the Agile Manifesto were analyzed. Next, through an inductive approach, focused on the convergence between the concepts involved, it was analyzed how agile principles could help to minimize the gap between ICT and business. Evidences of their occurrence were taken through a Conceptual Survey Research. As a result, the foundations and concepts of Agile Governance in ICT were defined and, finally, the development of a reference model was proposed as a future work.Este artigo apresenta as bases do conceito de Governança Ágil em TIC - Tecnologia da Informação e Comunicação - , baseado nos princípios e valores das Metodologias Ágeis da Engenharia de Software. O desenvolvimento deste trabalho se deu através de um processo de Revisão Sistemática, apoiado em técnicas e métodos Bibliométricos e Cienciométricos, no qual foram analisados os Fatores Críticos de Sucesso (FCS) de projetos de Governança em TIC e os princípios das Metodologias Ágeis. Em seguida, através de uma abordagem indutiva, com foco na convergência entre os conceitos envolvidos, analisou-se como os princípios ágeis poderiam contribuir para minimizar o hiato existente entre a TIC e o negócio. Evidências da coerência da proposta foram reforçadas através de uma Pesquisa de Sondagem Conceitual. Como resultado, foram definidas as bases em que se fundamentam o conceito de Governança Ágil em TIC e sugerido como trabalho futuro a definição de um modelo de referência para este conceito

DevOps for Digital Leaders

DevOps; continuous delivery; software lifecycle; concurrent parallel testing; service management; ITIL; GRC; PaaS; containerization; API management; lean principles; technical debt; end-to-end automation; automatio

Agile Processes in Software Engineering and Extreme Programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, Proceedings

agile software development; lean development; scrum; project management; software developmen

Best Practices for Implementing Agile Methods: A Guide for Department of Defense Software Developers

Traditional plan-driven software development has been widely used in the government because it\u27s considered to be less risky, more consistent, and structured. But there has been a shift from this approach to Agile methods which are more flexible, resulting in fast releases by working in an incremental fashion to adapt to the reality of the changing or unclear requirements. This report describes the Agile software development philosophy, methods, and best practices in launching software design projects using the Agile approach. It is targeted to Defense Department software developers because they face broad challenges in creating enterprise-wide information systems, where Agile methods could be used most effectively. Though not a panacea, agile methods offer a solution to an important class of problems faced by organizations today. Technology and E-Government

An agile based integrated framework for software development.

Doctor of Philosophy in Management. University of KwaZulu-Natal. Durban, 2018.Software development practice has been guided by practitioners and academics along an evolutionary path that extends from a Waterfall approach, characterised as highly prescriptive, to an approach that is agile, embracing the dynamic context in which software is developed. Agile Methodology is informed by a set of generic principles and agile methods that are customised by practitioners to meet the requirements of the environment in which it is used. Insight into the customisation of agile methods is pivotal to uphold the evolutionary trajectory of software development methodology. The study adopted a ‘socio-technical’ orientation to enhance the implementation of Agile Methodology. The social component of the study was aligned to the role played by organisational culture in the adoption of software development methodology. The amorphous concept of organisational culture has been operationalised by implementing the Competing Values Framework to develop a model that aligns organisational culture to an optimal methodology for software development. The technical component of the study has a software engineering focus. The study leveraged experiential knowledge of software development by South African software practitioners to develop a customised version of a prominent agile software development method. The model has been developed so that it is compatible with a variant of organisational culture that is aligned with agile methodology. The study implemented a sequential research design strategy consisting of two phases. The first phase was qualitative consisting of a phenomenological approach to develop the study’s main models. The second phase was quantitative, underpinned by technology acceptance theory, consisting of a survey based approach to determine South African software practitioners’ acceptance of the agile-oriented technical model that was developed in the study. The results from the survey indicated an 80% acceptance of the model proposed in study. Structural Equation Modelling was used to demonstrate that the inclusion of organisational culture as an independent construct improved the predictive capacity of technology acceptance theory in the context of software development methodology adoption. The study’s overall theoretical contribution was to highlight the significance of organisational culture in the implementation of agile methodology and to extend the evolutionary path of software development methodology by proposing an agile oriented model that scales the software process to an organisational infrastructure level