A STUDY ON SOFTWARE DEVELOPMENT PROJECT RISK, RISK MANAGEMENT, PROJECT OUTCOMES AND THEIR INTER-RELATIONSHIP

This research was undertaken with an objective of studying software development project risk, risk management, project outcomes and their inter-relationship in the Indian context. Validated instruments were used to measure risk, risk management and project outcome in software development projects undertaken in India. A second order factor model was developed for risk with five first order factors. Risk management was also identified as a second order construct with four first order factors. These structures were validated using confirmatory factor analysis. Variation in risk across categories of select organization / project characteristics was studied through a series of one way ANOVA tests. Regression model was developed for each of the risk factors by linking it to risk management factors and project /organization characteristics. Similarly regression models were developed for the project outcome measures linking them to risk factors. Integrated models linking risk factors, risk management factors and project outcome measures were tested through structural equation modeling. Quality of the software developed was seen to have a positive relationship with risk management and negative relationship with risk. The other outcome variables, namely time overrun and cost over run, had strong positive relationship with risk. Risk management did not have direct effect on overrun variables. Risk was seen to be acting as an intervening variable between risk management and overrun variables.

An analysis of the management of a public sector project: a systems-based case study

The management of a public sector project is analysed using a model developed from systems theory. Linear responsibility analysis is used to identify the primary and key decision structure of the project and to generate quantitative data regarding differentiation and integration of the operating system, the managing system and the client/project team. The environmental context of the project is identified. Conclusions are drawn regarding the project organization structure's ability to cope with the prevailing environmental conditions. It is found that the complexity of the managing system imposed on the project was unable to achieve this and created serious deficiencies in the outcome of the project.

Change management in practice: an ethnographic study of changes to contract requirements on a hospital project

Changes to client requirements are inevitable during construction. Industry discourse is concerned with minimizing and controlling changes. However, accounts of practices involved in making changes are rare. In response to calls for more research into working practices, an ethnographic study of a live hospital project was undertaken to explore how changes are made. A vignette of a meeting exploring the investigation of changes illustrates the issues. This represents an example from the ethnographic fieldwork, which produced many observations. There was a strong emphasis on using change management procedures contained within the contract to investigate changes, even when it was known that the change was not required. For the practitioners, this was a way of demonstrating best practice, transparent and accountable decision-making regarding changes. Hence, concerns for following procedures sometimes overshadowed considerations about whether or not a change was required to improve the functionality of the building. However, the procedures acted as boundary objects between the communities of practice involved on the project by coordinating the work of managing changes. Insights suggest how contract procedures facilitate and impede the making of changes, which can inform policy guidance and contract drafting.

Quality management for vital forest tree seedlings : Final report, Project no: P33854-1

The work concerns development of a prototype molecular tests to identify vitality status of conifer seedlings. The work is done by NSure, Holland, Dalarna University and SUAS. In case for spruce, a successful validation experiment has been performed to validate the identified frost tolerance and vitality genes. Multiple indicators were identified that can be used to either reinforce the existing ColdnSure test, but also for development of a vitality test. The identified frost tolerance and vitality genes for pine still need to be validated. NSure together with Dalarna University aim to perform a validation next season. Multiple LN indicators were identified in spruce that can be used to determine the effectiveness of a LN treatment, but they are not yet validated. In spruce and pine hardly any scientific research is performed to study the effect of a LN treatment, particularly not at molecular level. Therefore NSure together with Dalarna Research Station want to apply for a project. Within this project, we would be able to develop the tests further.

PRiMA : project risk management approach

Esta tese propõe uma abordagem sistemática para gerenciar riscos em projetos de software, por meio da adaptação de processos. O objetivo da abordagem é permitir a elaboração de um processo específico para um dado projeto, visando minimizar a exposição do projeto aos riscos, identificados de acordo com o contexto do projeto. As atividades, possíveis de serem executadas em processos de projetos de uma organização, são estruturadas em um framework de processo (PRiMA-F), que inclui também os padrões de processo e organizacionais usados para descrever ações preventivas e corretivas aos riscos. A estruturação do framework básico, construído pela organização, poderá permitir distintas instanciações, como por exemplo, processos de acordo com o paradigma ágil ou planejado, ou em conformidade com normas de qualidade, como CMM e outras; além dos padrões organizacionais e de processo para gestão de riscos de projeto. PRiMA-F define o escopo maior do processo de software da organização e este é adaptado de acordo com os riscos identificados para o projeto e suas necessidades específicas, dando origem ao processo a ser usado no projeto. adaptação. Os guias descrevem como adaptar elementos de processo de acordo com o tamanho e o formalismo do projeto. Configurações de processo são modelos prédefinidos, visando atender projetos típicos ou modelos de qualidade. Prima-F pode ser estendida para novos riscos, padrões e processos, de acordo com as necessidades da organização. Utilizando o paradigma Goal/Question/Metric, no framework de processo (PRiMAF), são definidas métricas do processo de software, associadas aos riscos, para serem usadas para acompanhar o progresso dos fatores de risco, possibilitando ao gerente de projeto tomar ações corretivas, quando necessário e no momento adequado. As ações corretivas são descritas usando padrões organizacionais e de processo. Uma ferramenta de apoio à sistemática proposta (PRiMA-Tool) foi desenvolvida. Estudos de caso foram elaborados para validar a sistemática proposta