Detecting Coordination Problems in Collaborative Software Development Environments

Software development is rarely an individual effort and generally involves teams of developers collaborating to generate good reliable code. Among the software code there exist technical dependencies that arise from software components using services from other components. The different ways of assigning the design, development, and testing of these software modules to people can cause various coordination problems among them. We claim\ud that the collaboration of the developers, designers and testers must be related to and governed by the technical task structure. These collaboration practices are handled in what we call Socio-Technical Patterns.\ud The TESNA project (Technical Social Network Analysis) we report on in this paper addresses this issue. We propose a method and a tool that a project manager can use in order to detect the socio-technical coordination problems. We test the method and tool in a case study of a small and innovative software product company

TESNA: A Tool for Detecting Coordination Problems

Detecting problems in coordination can prove to be very difficult. This is especially true in large globally distributed environments where the Software Development can quickly go out of the Project Manager’s control. In this paper we outline a methodology to analyse the socio-technical coordination structures. We also show how this can be made easier with the help of a tool called TESNA that we have developed

The Design and Implementation of a bespoke Enterprise Resource Planning System (ERP) for an acoustical engineering company

This paper will describe the tasks completed so far as part of a Knowledge Transfer Partnership between the University of Hertfordshire and Acoustical Control Engineers (ACE) a ‘small and medium sized enterprise’ (SME) based in Cambridgeshire, UK. ACE’s 25 personnel design, manufacture and install noise and vibration control systems to solve a wide range of acoustic problems. The projects undertaken include acoustic enclosures for supermarket refrigeration plant and for generators used in many situations, together with other more diverse applications such as controlling noise in the workplace and even on a luxury boat. Before the current KTP project the company used some partially computerised systems consisting of spreadsheets to perform acoustic analyses, pricing and project management functions supplemented with a paper based system to ‘fill the gaps’. Enterprise Resource Planning (ERP) systems provide an integrated database for all parts of the organisation allowing decisions to be based on a complete understanding of the organisation’s information, avoiding the problems due to duplication of data and ensuring that the consequences of decisions in one part of the organisation are reflected in the planning and control systems of the rest of the organisation. ERP systems became popular from the 1990’s mainly in relatively large organisations due to the complexity and cost of these systems. This project is unusual in that rather than adapting an off-the-shelf ERP solution to ACE’s very specific and specialised requirements we are taking an ERP development approach in an SME whose legacy systems are made up of spreadsheet and paper based systems. For the software development an Agile approach has been used. Agile involves software development methods based on iterative and incremental development. The initial attempt was to start developing the ERP from an Open Source ERP Source Code; however this effort was futile as a result of the bespoke nature of ACE’s business and product lines. Mapping ACE’s data model to the database which any existing ERP system could be adapted to, proved to be a very difficult problem. Therefore, developing the ERP from first principles was inevitable. Several of the ERP modules have been developed, user training has taken place and the core modules have been signed off. The project is due to complete in September 2014 and by this time we will have further information on how the ERP system has increased the competitiveness of the company, as well as experience of introducing an ERP into an SME. However, as would be expected the work undertaken developing the system so far has had several significant effects on ACE and acted as a catalyst for change in various parts of ACE’s business.Non peer reviewe

A Knowledge Transfer Partnership - the development of a Bespoke Enterprise Resource Planning System in the UK

Abstract. A Knowledge Transfer Partnerships (KTP) is a UK-wide programme designed to enable businesses to improve their competitiveness, productivity and performance. A KTP achieves this through the forming of a Partnership between a business and an academic institution. The aim is to enable businesses to access skills and expertise from academics and embed this knowledge in their businesses in order to develop the business. The knowledge sought is embedded into the business through a project, or projects, undertaken by a recently qualified person (known as the Associate). Part funding is provided by the government towards the Associate’s salary and towards the release of an Academic supervisor who works a half a day a week at the company. KTPs can vary in length from 6 months to three years, depending on the needs of the business and the desired outcomes. Therefore a KTP enables new capability to be embedded into the business and has benefited and continues to benefit a wide range of businesses across many sectors in the UK, including micro sized, small and large businesses across many sectors. This paper describes a Knowledge Transfer Partnership project between the University of Hertfordshire and a small and medium sized enterprise (SME) based in Cambridgeshire, UK.Final Accepted Versio

Identification of Critical Factors and Their Interrelationships to Design Agile Supply Chain : Special Focus to Oil and Gas Industries

Purpose – This research attempted to identify the most critical factors and their inter-relationships to ensure designing agile supply chain, especially in oil and gas industry. This factors identification process is performed through developing a conceptual framework and the use of Interpretive Structural Modelling (ISM) tool. Design/methodology/approach – This study is conducted through an extensive literature review and questionnaires survey to identify and refine the critical factors that ensure the agile supply chain in oil and gas industry. In addition, several brainstorming sessions with the experts in the field of oil and gas industries were organized with the objective to interpret the contextual inter-relationships between the identified factors. The outcomes from the literature reviews, interview questions and experts’ opinions were used to develop a diagraph and MICMAC analysis to know the drivers of agility in supply chain. Findings –From this study, 34 enablers and 12 factors were identified, which are responsible to ensure agile supply chain in oil and gas industry. Out of these identified factors, top management commitment, strategic alignment, competency of management and integration of information and systems technology are found to be the critical drivers of supply chain agility. On the other hand, government regulations, transportation and logistics flexibility and production planning and control falls under the category of dependent factors. Originality/value – The identified factors and their interrelationships can be a valuable aid to ensure and measure the agility in supply chain, especially in oil and gas industry. These identified factors and their defined consequences will help managers and concerned authorities in oil and gas industry to take better decision to improve the agility level of their supply chain.©2020 Springer Nature. This is a post-peer-review, pre-copyedit version of an article published in Global Journal of Flexible Systems Management. The final authenticated version is available online at: http://dx.doi.org/10.1007/s40171-020-00247-5fi=vertaisarvioitu|en=peerReviewed

Negotiation Support and Risk Reduction in Collaborative Networks

Part 2: Collaborative Enterprise NetworksInternational audienceIn face of the current economic turbulence, companies face new challenges. In order to respond to new business opportunities, it is crucial that companies attain strategic alliances so that they can obtain or maintain market competiveness. The formation of alliances and partnerships for collaborative problem solving is of extreme importance, being therefore essential to understand their structures and requirements. To overcome a number of difficulties that may appear in the formation of such alliances, it is necessary to properly model the elements that constitute the alliance agreements through a suitable negotiation support environment that besides the basic functionalities of data storage and alerts can also conduct the entire negotiation process making it traceable. In this context, this paper presents the main requirements of an electronic negotiation support environment in a collaborative network, identifies the main risk sources and drivers in collaborations, and analyses how a negotiation support system can help in reducing the potential risk in collaboration

A taxonomy of dependencies in agile software development

Dependencies in a software project can contribute to unsatisfactory progress if they constrain or block the flow of work. Various studies highlight the importance of dependencies in the organisation of work; however dependencies in agile software development projects have not previously been a research focus. Drawing on three case studies of agile software projects, and the IS literature, this paper develops an initial taxonomy of agile software project dependencies. Three distinct categories of dependency are found: task, resource, and knowledge dependencies. This paper contributes to theory by providing a taxonomy of dependency types occurring in the area of agile software development. Practitioners can use this taxonomy as sensitising device to ensure they consider dependencies they might face that could hinder their projects, enabling them to take appropriate and timely mitigating action.<br /

NEC themes: a conceptual analysis and applied principles

This paper deals with essential principles of Interoperability, Agility, Collaboration and Knowledge applied in the context of Network Enabled Capability Through Innovative Systems Engineering (NECTISE). Using empirical investigations these concepts have been identified as NEC-readiness themes and they contribute significantly to the realisation of NEC. Based on a systemic analysis and application of theoretical principles, the approach described in this paper contributes towards the demonstration of NEC as well as the identification of a limited set of critical features for capability planning and systems design. Some research questions are derived and discussed and a gap analysis strategy is proposed. These themes also defined as critical features have been investigated in a variety of contexts The main contributions of this paper are related to the mapping the themes to the military capability model and formalisation of the relationships. The purpose of such an exercise is to exploit learning from other (mainly civil) domains in the military context, with regard to the readiness themes which overlap with a limited set of critical features for design within a NEC context