Risk management in software projects through Knowledge Management techniques: Cases in Brazilian Incubated Technology-Based Firms

Neves, Sandra Miranda; Silva, Carlos Eduardo Sanches da; Salomon, Valério Antônio Pamplona; Silva, Aneirson Francisco da; Sotomonte, Bárbara Elizabeth Pereira

doi:10.1016/j.ijproman.2013.02.007

Cited by 53 publications

(32 citation statements)

References 38 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…On the same direction of the proposed approach, Ruhe and Greer [6] introduce an iterative model dealing with software risks, in which a set of various releases m is recommended. However, in a way different from the proposed approach, this proposal deals with risks as a constraint, defining a limit level that should not be exceeded, as indicated in Equation 25. Thus, unlike the approach proposed herein, risks in this proposal do not impact directly on requirements costs or clients' satisfaction.…”

Section: Related Workmentioning

confidence: 99%

“…Again, note that, for each identified risk, the set of associated mitigation techniques represents in the proposed approach the term , , which denotes the traceability between the risk and the mitigation technique , as defined in Equation 14. Although the adopted dataset does not contain risks, a survey that include such information was used as a guideline [25] in order to estimate synthetic data. Thereafter, for all identified mitigation techniques, as illustrated in Table 4, it is necessary to provide their associated costs, together with classifications as preventive or corrective techniques.…”

Section: A Pilot Use Casementioning

confidence: 99%

See 1 more Smart Citation

A Risk-Based Approach for Selecting Software Requirements

Amaral

Elias

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

In incremental development approaches, there is a great interest in delivering system releases on-time and on-budget, raising the satisfaction level of the stakeholders involved in the development process. Thus, the software requirements selection process has a key role in identifying a good-enough or even an optimal subset of candidate requirements, which can balance trade-offs among critical aspects, such as project budget, requirements costs, customers' preferences and their importance. Despite relevant contributions, current proposals do not address software risks involved in the development process, which represents another key aspect that can deeply impact on project cost and stakeholders' satisfaction. In such a direction, this paper proposes a risk-based approach for selecting software requirements, in which a risk analysis is incorporated for estimating the impact of risks in the cost of the next release requirements and stakeholders' satisfaction. Evaluation results based on a pilot use case reveal the potential practical applicability of the proposed approach. CCS Concepts• Software and its engineering➝Requirements analysis • Software and its engineering➝Risk management.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: A Pilot Use Casementioning

confidence: 99%

A Risk-Based Approach for Selecting Software Requirements

Amaral

Elias

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

show abstract

“…Pástor, Šipikal and Rehák (2013) found evidence of knowledge creation through innovation and knowledge acquisition from external sources in Slovakian organisations. Neves et al (2014) investigated the role of KM in mitigating risk in micro and small software organisations in Brazil. Their study found that combination -as explained by Nonaka and Takeuchi (1995) -is mostly used to mitigate risk in software development teams.…”

Section: Knowledge Management Practices In Software Organisationsmentioning

confidence: 99%

“…In developed countries such as Germany, Australia and Irelandto mention but a few -studies by Aurum, Daneshgar and Ward (2008), Heavin and Adam (2012) and Betz, Oberweis and Stephan (2014) have been conducted to investigate KM practices in software development organisations. Developing countries in the Brazil, Russia, India, China, SA (BRICS) block such as Brazil, China and India have investigated this issue too (Jiang et al 2009;Neves et al 2014;Sharma, Singh & Goyal 2012). This does not seem to be the case in SA, yet she is an African IT giant.…”

Section: Introductionmentioning

confidence: 99%

Knowledge management in small software development organisations: A South African perspective

Shongwe

2017

S. Afr. j. inf. manag.

View full text Add to dashboard Cite

Background: Software organisations have been experiencing software development failures since the beginning of software development. Globally, latest Standish Group CHAOS reports indicate that only 29% of projects are successful. In South Africa (SA), the ITWeb report (2013) indicates that only 11% of all projects are successful. Intervention strategies such as software process improvement (SPI) frameworks and new software development methodologies such as agile methods have been introduced to address this issue. These intervention strategies do not seem to be effective because software development projects continue to fail. To address this issue, software organisations are turning to knowledge management (KM). This is because software development is a knowledge-intensive task.Objectives: The study aimed to investigate KM practices in small, medium and micro (SMMEs) software development organisations in SA and to determine if KM has benefited the organisations.Method: Fifteen software development project managers from 15 software development SMMEs were interviewed. Content analysis was used to analyse the data.Results: The study found six KM practices in the organisations: knowledge acquisition, creation, storage, sharing, organisation and application. The study found that KM has benefited organisations by making them effective, efficient and productive.Conclusions: The study concluded that software development organisation have adopted KM, although informally, and that KM practices have improved organisational routines and processes.

show abstract

“…Neves et al (2014) verificaram as técnicas da gestão do conhecimento na análise dos riscos no desenvolvimento de software em incubadoras de empresa, sendo que o principal risco para os gestores e desenvolvedores são escopo e metas indefinidas. Para Islam et al (2014), a fase inicial do gerenciamento de riscos auxilia nos problemas que possam existir em um projeto, e isso contribui para o sucesso geral do projeto.…”

Section: Definição De Riscounclassified

Gerenciamento de Risco Aplicado ao Desenvolvimento de Software

Macedo

Salgado

2015

S&G

View full text Add to dashboard Cite

O risco presente na condução do desenvolvimento de software é um assunto que sempre foi uma preocupação para a engenharia de software. Muito tem sido feito para que os projetos sejam entregues de acordo com o cronograma, mas incertezas sempre existirão no decorrer do tempo. Isso mostra que a área de gerenciamento de risco tem uma importância significativa no projeto de desenvolvimento de software. O gerenciamento de risco colabora com a redução e mitigação dos riscos do projeto por meio de sua identificação e análise para que seja tratado e controlado. Além disso, se o gerenciamento de riscos for aplicado adequadamente, pode resultar na melhoria do produto e no aumento da produtividade do processo de desenvolvimento de software.Dessa forma, esta pesquisa tem por objetivo analisar a incorporação do gerenciamento de riscos no processo de desenvolvimento de software no Laboratório de Pesquisa e Desenvolvimento da Universidade Federal de Alfenas (UNIFAL-MG). As etapas de análise qualitativa de riscos e o planejamento de medidas frente aos riscos fornecem uma maior precisão quanto aos prazos e a identificação das atividades críticas que podem surgir durante o desenvolvimento de um software nessa empresa.Palavras-chave: Engenharia de software; desenvolvimento de software; gerenciamento de riscos. ResumoThe risk present in driving the software development is a subject that always been a concern to the Software Engineering. Much has been done to ensure that projects are delivered according to the schedule, but there will always be uncertainties over the time. This shows that the area of risk management has a significant importance in the project of software development. Risk management contributes to the reduction and mitigation of project risks through its identification and analysis to be treated and controlled. Furthermore, if risk management is applied properly can result in product improvement and increasing the productivity of the software development process. Thus, this research aims to analyze the incorporation of risk management in the process of software development at the Laboratory of Research and Development, Federal University of Alfenas (UNIFAL-MG). The steps of qualitative risk analysis and the planning measures forward the risks provide greater accuracy concerning deadlines and identification of critical issues that may arise during the development of one software in this company.Keywords: Software engineering, software development, risk management. Abstract INTRODUÇÃOSegundo Martins (2010), pode-se definir projeto como um trabalho que visa a criação de um produto ou a execução de um serviço que é do tipo específico, temporário em que há certo grau de incerteza em sua realização cujas atividades precisam ser planejadas, programadas e, quando executadas, necessitam ser controladas. Essa definição vai ao encontro da definição de projeto preconizada pelo o PMI (2004).Um projeto deve ter um ciclo de vida definido composto por um início, intermediário e término. Os custos e a quantidade de recursos alocados ...

show abstract

Risk management in software projects through Knowledge Management techniques: Cases in Brazilian Incubated Technology-Based Firms

Cited by 53 publications

References 38 publications

A Risk-Based Approach for Selecting Software Requirements

A Risk-Based Approach for Selecting Software Requirements

Knowledge management in small software development organisations: A South African perspective

Gerenciamento de Risco Aplicado ao Desenvolvimento de Software

Contact Info

Product

Resources

About