Software systems engineering: a journey to contemporary agile and beyond, do people matter?

publishedVersio

Software systems engineering: a journey to contemporary agile and beyond, do people matter?

It is fascinating to view the evolution of software systems engineering over the decades. At the first glance, it could be perceived that the various approaches and processes are different. Are they indeed different? This paper will briefly discuss such a journey relating to findings from an empirical study in some organisations in the UK. Some of the issues described in the literature and by practitioners are common across different software system engineering approaches over the time. It can be argued that human-element of software development plays an integral part in the success of software systems development endeavour. After all, software engineering is a human-centric craft. In order to understand such issues, we crossed the discipline to other disciplines in order to adapt theories and principles that will help to better understand and tackle such matter. Other disciplines have well established human related theories and principles that can be useful. From Japanese management philosophies, we have adapted Lean and knowledge management theories. From psychology, we have adapted Emotional Intelligence (EI). With such an interdisciplinary view, some of the issues can be addressed adequately. Which bring the question: is it really the process or the people? The second author will reflect on his experience attending the first SQM conference 25 years ago. The reflection will discuss the evolution of software systems engineering, and what was changed since then, if at all changed

Determining information systems contribution to manufacturing agility for SME's in dynamic business environments

This thesis was submitted for the degree of Doctor of Philosophy and awarded by Brunel University.Since the concept of agile manufacturing was coined in the early nineties, the study of the contribution of information systems to agility has lacked a thorough analysis. Information systems have been labelled in the academic literature as critical, key and important in achieving and supporting agility. On the other hand, there is a large number of documented cases where IS have failed to deliver expected benefits. The aim of this study has been to determine the contribution of information systems to manufacturing agility. This study required the development of a research survey with the purpose of testing seven IT/IS proficiency characteristics of agility, three characteristics of a dynamic business environment and the type of IS applications used in manufacturing organisations. The analysis of the survey suggested that the business environment does not exert great influence on the IT/IS proficiency characteristics; also no association was found with the use of a specific type of manufacturing IS and the IT/IS proficiency characteristics. The results of the analysis of the survey were further expanded in a multiple case-study. Profitable SMEs with some agile processes in place participated in a multiple case-study that covered the agility of manufacturing and other business process, business and IT strategies, and skills and expertise of employees affecting the realisation of benefits of IS. The study revealed that information systems are neither the most important, the most overwhelming, the most difficult part of the equation to achieve agility nor are they principal enablers of manufacturing. Identified principal enablers of agile manufacturing include providing training to employees, right attitude of workforce towards change, having a flexible manufacturing base and people's knowledge and skills. Moreover, the use of low performing information systems was not an impediment to moving towards agility. The results of the multiple case-study tend to indicate that information systems play a more significant role in enhancing agility once principal enablers have been implemented. Certainly, IS may be required to support manufacturing agility but that information systems are not sufficient to achieve it. The study revealed that skills and expertise of people were used as means to overcome the problems and shortcomings generated by low performing IS. A new taxonomy of enablers of agility has been defined, identifying IS as second-order enablers of agility. Also, a proposed new framework has considered the adoption of an IT strategy to influencing a business strategy as a mean of enhancing the agility of business processes already achieved through the implementation of principal enablers

Exploring the supply chain agility attributes in fast moving consumer goods industry: A case study in the Middle East

During the 1990s, supply chain management and agility have both received great attention. This is due to the fact that the business market place is characterized by being highly dynamic and complex. This paper aims to explore the need and the attributes of supply chain agility in FMCG business industry working in the Middle East markets. A case study of a multinational company working in the Middle East was chosen, where it faces the challenges of its business environment and its rapid changes in its markets. The findings show the case study supply chain working within such type of industry needs to be agile and that the attributes required for achieving agility within FMCGs supply chain includes: responsiveness; Customer service; flexibility; innovation; speed; quality; efficiency; and responsible people thinking

Revealing the Vicious Circle of Disengaged User Acceptance: A SaaS Provider's Perspective

User acceptance tests (UAT) are an integral part of many different software engineering methodologies. In this paper, we examine the influence of UATs on the relationship between users and Software-as-a-Service (SaaS) applications, which are continuously delivered rather than rolled out during a one-off signoff process. Based on an exploratory qualitative field study at a multinational SaaS provider in Denmark, we show that UATs often address the wrong problem in that positive user acceptance may actually indicate a negative user experience. Hence, SaaS providers should be careful not to rest on what we term disengaged user acceptance. Instead, we outline an approach that purposefully queries users for ambivalent emotions that evoke constructive criticism, in order to facilitate a discourse that favors the continuous innovation of a SaaS system. We discuss theoretical and practical implications of our approach for the study of user engagement in testing SaaS applications

A hybrid approach to achieve organizational agility: An empirical study of a food company

Purpose: In today’s intense global competition, agility is advocated as a fundamental characteristic for business survival and competitiveness. The purpose of this paper is to propose a practical methodology to achieve and enhance organizational agility based on strategic objectives. Design/methodology/approach: In the first step, a set of key performance indicators (KPIs) of the organization being studied are recognized and classified under the perspectives of balanced scorecard (BSC). Critical success factors are then identified by ranking the KPIs according to their importance in achieving organizational strategic objectives using the Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS). In the second step, three houses of quality (HOQs) are constructed sequentially to identify and rank the main agile attributes, agile enablers, and improvement paths. In addition, in order to translate linguistics judgments of practitioners into numerical values in building HOQs, fuzzy logic is employed. Findings: The capability of the proposed methodology is demonstrated by applying it to a case of a multi-national food company in Iran. Through the application, the company could find the most suitable improvement paths to improve its organizational agility. Research limitations/implications: A limited number of KPIs were chosen due to computational and visual constraints related to HOQs. Another limitation, similar to other agility studies, which facilitate decision making among agility metrics, was that the metrics were more industry-specific and less inclusive. Practical implications: A strong practical advantage for the application of the methodology over directly choosing agility metrics without linking them is that through the methodology, the right metrics were selected that match organization’s core values and marketing objectives. While metrics may ostensibly seem unrelated or inappropriate, they actually contributed to the right areas where there were gaps between the current and desired level of agility. It would otherwise be impossible to choose the right metrics without a structured methodology. Originality/value: This paper proposes a novel methodology for achieving organizational agility. By utilizing and linking several tools such as BSC, fuzzy TOPSIS, and quality function deployment (QFD), the proposed approach enables organizations to identify the most appropriate agile attributes, agile enablers, and subsequently agile improvement paths

Comparative Study on Agile software development methodologies

Today-s business environment is very much dynamic, and organisations are constantly changing their software requirements to adjust with new environment. They also demand for fast delivery of software products as well as for accepting changing requirements. In this aspect, traditional plan-driven developments fail to meet up these requirements. Though traditional software development methodologies, such as life cycle-based structured and object oriented approaches, continue to dominate the systems development few decades and much research has done in traditional methodologies, Agile software development brings its own set of novel challenges that must be addressed to satisfy the customer through early and continuous delivery of the valuable software. It is a set of software development methods based on iterative and incremental development process, where requirements and development evolve through collaboration between self-organizing, cross-functional teams that allows rapid delivery of high quality software to meet customer needs and also accommodate changes in the requirements. In this paper, we significantly identify and describe the major factors, that Agile development approach improves software development process to meet the rapid changing business environments. We also provide a brief comparison of agile development methodologies with traditional systems development methodologies, and discuss current state of adopting agile methodologies. We speculate that from the need to satisfy the customer through early and continuous delivery of the valuable software, Agile software development is emerged as an alternative to traditional plan-based software development methods. The purpose of this paper, is to provide an in-depth understanding, the major benefits of agile development approach to software development industry, as well as provide a comparison study report of ASDM over TSDM.Comment: 25 pages, 25 images, 86 references used, with authors biographie

Agile Testing: Improving the Process : Case Descom

The thesis was assigned by Descom, a marketing and technology company based in Jyväskylä. The aim of the thesis was to research the current state of testing inside the organization, and to improve on the existing processes and practices. The thesis was carried out as a design research (applied action research), because the focus was improving already existing processes inside a company. The theory base contains a wide range of subjects from agile development models, the testing process, and process improvement models to agile testing. Without a solid base of multiple aspects it would have been impossible to understand how the testing works as a process and how it could have been improved. As Descom uses agile development it was necessary to follow the same principles throughout the writing of the thesis and on results. As a result information was provided for the company about the current state of testing procedures at Descom and how to improve the testing and processes in the future. The documentation already existing for testing such as the test plan and test report were updated. New documents such as a process improvement plan based on Critical Testing Processes, test strategy and testing policy were also created. Figures of the testing process, and the processes for all test types in use were created to be used as a visual aid for understanding the testing as whole at Descom.Opinnäytetyön toimeksianto tuli Descomilta, joka on Jyväskylästä lähtöisin oleva markkinointi ja teknologia yritys. Työn tavoitteena oli tutkia testauksen tilaa organisaatiossa ja kehittää olemassa olevia prosesseja ja käytäntöjä. Tutkimusmenetelmäksi valikoitui kehittämistutkimus, koska painotus oli olemassa olevien prosessien kehityksessä yrityksen sisällä. Teoriapohjassa käsiteltiin monia aiheita ketterästä sovelluskehityksestä, testausprosessista ja prosessi kehityksestä aina ketterään testaukseen asti. Ilman kattavaa pohjaa monille osa-alueille, olisi ollut mahdotonta ymmärtää miten testaus toimii prosessina ja miten sitä pystyy kehittämään. Descom toimii ketterän sovelluskehityksen mukaisesti projekteissaan, joten oli tärkeää seurata samoja ketteriä periaatteita läpi opinnäytetyön kirjoittamisen ja tuloksissa. Tuloksena saatiin tietoa yritykselle, siitä miten testaus on toiminut Descomilla ja kuinka testausta ja prosesseja tulisi kehittää tulevaisuudessa. Myös aiemmin olemassa olleet testausdokumentit päivitettiin. Uusina dokumentteina laadittiin suunnitelma prosessikehitykseen, joka perustui Critical Testing Processes –malliin, testausstrategia ja testauspolitiikka. Prosessikuvaus tehtiin kaavioita käyttäen, joilla kuvattiin prosessi kokonaisuutena sekä käytettävät testaustasot