Current Trends in Software Project Management

Abstract

Abstract. Complexity of software project management has been increasing rapidly in recent years. Project management strategies are evolving in order to address the complexity problems. A persistent struggle is to find an adequate balance between conflicting factors such as providing freedom and flexibility to software engineers in order to solve complex problems in a creative way while managing risks associated with freedom and flexibility. Risk based strategies for software project management appear to be promising. Potential risks are identified, analyzed, assessed and monitored. Appropriate steps are taken for managing imminent risks in a timely manner. This study suggests that communication risk plays a special role in software projects, because it interacts with other risks in startling ways. Interacting risks need to be studied at several levels with special attention to communication risk, because it could be considered as a super-risk. Current trends in software project management include analysis of all categories of risks such as technical risks, budget risks, scheduling risks, legal risks, ethical risks, operational risks, security risks, communication risks, project planning risks, and personnel risks that require timely intervention without restricting the creative power of executable software knowledge development.

Toward ontology‐based risk management framework for software projects: An empirical study

“…The aim of the study is to have quick access to information in recorded data in documents and spreadsheets having to do with scope, time, and cost management in software projects. Another study 34 Comparing this research work with some selected related works, we discovered that Rene Robin and Uma used ontology to develop their knowledge repository. The risk classes and subclasses are categorized and modeled using technical development process.…”

“…Likewise, Dey et al 34 identified risks but did not use spiral SDLC model. The research carried out by Sariglannidis and Chatzoglou 37 analyzes the effect of project risks and the extent of the effect of residual performance risk on software project performance for software experts.…”

“…Software risks identified in this work are majorly from the literature review and a few from experts during the interview. 34 In a nutshell, HBRS assists in the prioritization of risks, which invariably helps in providing an appropriate method of risk mitigation. This phase is important in ontology for creating classes, subclasses, and the risk factors with the relationship that exist among them.…”

“…The aim of the study is to have quick access to information in recorded data in documents and spreadsheets having to do with scope, time, and cost management in software projects. Another study 34 about current trends in software project management proposed communication risk as a superrisk in the development of software projects. They emphasized the communication risks related to another category of risks in a surprising way and that the software project is a complex undertaken, which involves the cognitive nature of its development.…”

“…Bastos 33 used ontologies to develop their knowledge repository for recorded data for reusability in order to enhance the development of software projects. Likewise, Dey et al 34 identified risks but did not use spiral SDLC model. The research carried out by Sariglannidis and Chatzoglou 37 analyzes the effect of project risks and the extent of the effect of residual performance risk on software project performance for software experts.…”