Using grounded theory to understand software process improvement: A study of Irish software product companies

Software Process Improvement (SPI) aims to understand the software process as it is used within an organisation and thus drive the implementation of changes to that process to achieve specific goals such as increasing development speed, achieving higher product quality or reducing costs. Accordingly, SPI researchers must be equipped with the methodologies and tools to enable them to look within organisations and understand the state of practice with respect to software process and process improvement initiatives, in addition to investigating the relevant literature. Having examined a number of potentially suitable research methodologies, we have chosen Grounded Theory as a suitable approach to determine what was happening in actual practice in relation to software process and SPI, using the indigenous Irish software product industry as a test-bed. The outcome of this study is a theory, grounded in the field data, that explains when and why SPI is undertaken by the software industry. The objective of this paper is to describe both the selection and usage of grounded theory in this study and evaluate its effectiveness as a research methodology for software process researchers. Accordingly, this paper will focus on the selection and usage of grounded theory, rather than results of the SPI study itself

Integration of Cost andWork Breakdown Structures in the Management of Construction Projects

Scope management allows project managers to react when a project underperforms regarding schedule, budget, and/or quality at the execution stage. Scope management can also minimize project changes and budget omissions, as well as improve the accuracy of project cost estimates and risk responses. For scope management to be effective, though, it needs to rely on a robust work breakdown structure (WBS). A robust WBS hierarchically and faithfully reflects all project tasks and work packages so that projects are easier to manage. If done properly, the WBS also allows meeting the project objectives while delivering the project on time, on budget, and with the required quality. This paper analyzes whether the integration of a cost breakdown structure (CBS) can lead to the generation of more robust WBSs in construction projects. Over the last years, some international organizations have standardized and harmonized different cost classification systems (e.g., ISO 12006-2, ISO 81346-12, OmniClass, CoClass, UniClass). These cost databases have also been introduced into building information modeling (BIM) frameworks. We hypothesize that in BIM environments, if these CBSs are used to generate the project WBS, several advantages are gained such as sharper project definition. This enhanced project definition reduces project contradictions at both planning and execution stages, anticipates potential schedule and budget deviations, improves resource allocation, and overall it allows a better response to potential project risks. The hypothesis that the use of CBSs can generate more robust WBSs is tested by the response analysis of a questionnaire survey distributed among construction practitioners and project managers. By means of structural equation modeling (SEM), the correlation (agreement) and perception differences between two 250-respondent subsamples (technical project staff vs. project management staff) are also discussed. Results of this research support the use of CBSs by construction professionals as a basis to generate WBSs for enhanced project management (PM)

Technical debt and waste in non-functional requirements documentation:an exploratory study

Background: To adequately attend to non-functional requirements (NFRs), they must be documented; otherwise, developers would not know about their existence. However, the documentation of NFRs may be subject to Technical Debt and Waste, as any other software artefact. Aims: The goal is to explore indicators of potential Technical Debt and Waste in NFRs documentation. Method: Based on a subset of data acquired from the most recent NaPiRE (Naming the Pain in Requirements Engineering) survey, we calculate, for a standard set of NFR types, how often respondents state they document a specific type of NFR when they also state that it is important. This allows us to quantify the occurrence of potential Technical Debt and Waste. Results: Based on 398 survey responses, four NFR types (Maintainability, Reliability, Usability, and Performance) are labelled as important but they are not documented by more than 22% of the respondents. We interpret that these NFR types have a higher risk of Technical Debt than other NFR types. Regarding Waste, 15% of the respondents state they document NFRs related to Security and they do not consider it important. Conclusions: There is a clear indication that there is a risk of Technical Debt for a fixed set of NFRs since there is a lack of documentation of important NFRs. The potential risk of incurring Waste is also present but to a lesser extent

An empirical study on the implementation and evaluation of a goal-driven software development risk management model

Context: Building a quality software product in the shortest possible time to satisfy the global market demand gives an enterprise a competitive advantage. However, uncertainties and risks exist at every stage of a software development project. These can have an extremely high influence on the success of the final software product. Early risk management practice is effective to manage such risks and contributes effectively towards the project success. Objective:Despite risk management approaches, a detailed guideline that explains where to integrate risk management activities into the project is still missing. Little effort has been directed towards the evaluation of the overall impact of a risk management method. We present a Goal-driven Software Development Risk Management Model (GSRM) and its explicit integration into the requirements engineering phase and an empirical investigation result of applying GSRM into a project. Method:We combined case study method with action research. This allows to guide the development team for managing risks and to attain goals as well as to identify ways to improve the proposed methodology. The data is from multiple sources and analysed both qualitative and quantitative way. Results: When risk factors are beyond the control of the project manager and project environment then it is difficult to control these risks. Project scope affects all dimensions of risk. GSRM is a reasonable risk management method that can be employed in an industrial context. The study results compare with other existing study results, to generalize findings and to identify contextual factors. Conclusion: A formal early stage risk management practice provides early warning related to the problems that exists in the project and contributes to the overall project success. It is not necessary to always consider budget and schedule constraints top priority. There exist issues such as requirements, change management, and user satisfaction influence these constraints

Ability-based view in action: a software corporation study

This research investigates antecedents, developments and consequences of dynamic capabilities in an organization. It contributes by searching theoretical and empirical answers to the questions: (a) What are the antecedents which can provide an organization with dynamic and ordinary capabilities?; (b) How do these antecedents contribute to create capabilities in an organization?; (c) How do they affect an organization's competitive advantage?; (d) Can we assess and measure the antecedents and consequences to an organization? From a first (theoretical) perspective, this paper searches answers to the first, second and third questions by reviewing concepts of an ability-based view of organizations that involves the abilities of cognition, intelligence, autonomy, learning and knowledge management, and which contributes to explain the dynamic behavior of the firm in the pursuit of competitive advantage. From a second (empirical) perspective, this paper reinforces and delivers findings to the second, third and fourth questions by presenting a case study that evidences the ability-based view in action in a software corporation, where it contributes by investigating: (a) the development of organizational capabilities; (b) the effects of the new capabilities on the organization; and (c) the assessment and measurement of the abilities and consequences

The building information modelling trajectory in facilities management: A review

There is a paucity of literature that examines building information modelling (BIM) for asset management within the architecture, engineering, construction and owner-operated (AECO) sector. This paper therefore presents a thorough review of published literature on the latest research and standards development that impact upon BIM and its application in facilities management (FM) during the operations and maintenance (O&M) phase of building usage. The purpose is to generate new ideas and provide polemic clarity geared to intellectually challenge readers from across a range of academic and industrial disciplines. The findings reveal that significant challenges facing the FM sector include the need for: greater consideration of long-term strategic aspirations; amelioration of data integration/interoperability issues; augmented knowledge management; enhanced performance measurement; and enriched training and competence development for facilities managers to better deal with the amorphous range of services covered by FM. Future work is also proposed in several key areas and includes: case studies to observe and report upon current practice and development; and supplementary research related to concepts of knowledge capture in relation to FM and the growing use of BIM for asset management