5 A knowledge-based risk management approach for Scrum software development projects

2021 ◽  
pp. 97-116
Author(s):  
Mirko Perkusich ◽  
Ademar Sousa Neto ◽  
Joao Nunes ◽  
Kyller Gorgônio ◽  
Hyggo Almeida ◽  
...  
2021 ◽  
pp. 1063293X2110152
Author(s):  
Qing Yang ◽  
Yingxin Bi ◽  
Qinru Wang ◽  
Tao Yao

Software development projects have undergone remarkable changes with the arrival of agile development approaches. Many firms are facing a need to use these approaches to manage entities consisting of multiple projects (i.e. programs) simultaneously and efficiently. New technologies such as big data provide a huge power and rich demand for the IT application system of the commercial bank which has the characteristics of multiple sub-projects, strong inter-project correlation, and numerous project participating teams. Hence, taking the IT program management of a bank in China as a case, we explore the methods to solve the problems in multi-project concurrent development practice through integrating the ideas of program and batch management. First, to coordinate the multi-project development process, this paper presents the batch-based agile program management approach that synthesizes concurrent engineering with agile methods. And we compare the application of batch management between software development projects and manufacturing process. Further, we analyze the concurrent multi-project development practice in the batch-based agile program management, including the overlapping between stages, individual project’s activities, and multiple projects based on common resources and environment to stimulate the knowledge transfer. Third, to facilitate the communication and coordination of batch-based program management, we present the double-level responsibility organizational structure of batch management.


2021 ◽  
Vol 43 (4) ◽  
pp. 113-124
Author(s):  
D.V. Saveliev ◽  

The article defines the concept of threat model. Described a list of current security guidelines for the development and administration of web systems. Formed the list of cybersecurity threats, the consequences of their implementation are determined. Described the process of forming a model of cybersecurity threats of web systems. Defined the list of threats based on the recommendations and experience of authoritative organizations in the world and Ukraine. Defined the concepts of risk, risk index and risk status for the security of web systems. Defined the main principles of risk management in software development projects.


Author(s):  
Mohammad Baydoun

This case aims to analyze risk management practices of Millennium Development International (MDI) and suggest enhancements based on a theoretical framework derived from the literature while considering the implications to its organizational structure. Al-Shamiyah project in Makkah, Saudi Arabia, is used as an example to illustrate the practices of MDI. Due to a high level of risk associated with large-scale development projects, it is argued that the traditional risk management approach is not convenient to the context of these projects. Each large-scale project has a high level of uniqueness that renders benchmarks generated out of previous projects obsolete. Hence, a reactive risk management approach is being promoted. For the purpose of optimizing this approach, engaging necessary experts and securing the presence of key decision makers in the process, the formulated system defines key milestones at which risks need to be assessed and proper decisions need to be taken.


2016 ◽  
pp. 1220-1237 ◽  
Author(s):  
Mohammad Baydoun

This case aims to analyze risk management practices of Millennium Development International (MDI) and suggest enhancements based on a theoretical framework derived from the literature while considering the implications to its organizational structure. Al-Shamiyah project in Makkah, Saudi Arabia, is used as an example to illustrate the practices of MDI. Due to a high level of risk associated with large-scale development projects, it is argued that the traditional risk management approach is not convenient to the context of these projects. Each large-scale project has a high level of uniqueness that renders benchmarks generated out of previous projects obsolete. Hence, a reactive risk management approach is being promoted. For the purpose of optimizing this approach, engaging necessary experts and securing the presence of key decision makers in the process, the formulated system defines key milestones at which risks need to be assessed and proper decisions need to be taken.


2007 ◽  
Vol 20 (1) ◽  
pp. 70-82 ◽  
Author(s):  
Tom McBride ◽  
Brian Henderson‐Sellers ◽  
Didar Zowghi

PurposeThe paper seeks to investigate whether project managers regard software development projects as design problems or production problems.Design/methodology/approachProject management literature was examined to determine what evidence there should be to indicate whether a software development project was regarded as a problem to be solved or a product to be produced. Data were then collected through structured interview of project managers currently engaged in managing software development projects. The data were analysed to determine how project managers regarded their projects and whether this matched a theoretical expectation.FindingsThe empirical data indicated that most project managers regard their projects as production problems, where it is assumed that the underlying problem is largely understood, the project encapsulated in a planned schedule of activities and there will be an emphasis on monitoring the project against the planned progress.Research limitations/implicationsOwing to the small sample size of fewer than 30 project managers, external validity is weak. More research is needed to confirm these results over a larger sample and to probe more subtle orientation to production or design projects.Practical implicationsThe research developed a simple test to indicate the degree of novelty of the application to be developed. The test indicates whether the application is novel and should be treated as a design problem, or well known and therefore should be treated as a production problem.Originality/valueThe paper draws attention to the need for project managers to evaluate the type of application to be developed and to adopt an appropriate project management approach. The paper also provides a simple test to achieve that objective.


2022 ◽  
Vol 14 (2) ◽  
pp. 756
Author(s):  
Rocío Rodríguez-Rivero ◽  
Isabel Ortiz-Marcos

When working with international development projects (IDPs), the use of the logical framework approach (LFA) prevails as the most important tool to plan and manage these projects. This paper presents how the methodology has been enriched, including risk management (LFRMA logical framework with risk management approach), proposing an original contribution, tested with professionals that will improve the effectiveness of IDPs by increasing their success rate and their sustainability. The steps followed to design the methodology (problem statement (literature review, interview with experts, questionnaire for professionals. and statistical analysis), case study analysis (eight case studies in Colombia, interviews with IDPs managers, focus groups, questionnaire for participants, qualitative analysis, and fuzzy analysis) and design of LFRMA (focus group with experts)) and the methodology itself (how to introduce risk management during all the life cycle through the methodology steps) are presented. Conclusions answer the research questions: can the effectiveness and sustainability of IDPs be improved? Can risk management help to improve IDPs effectiveness? Would it be useful to introduce risk management into the LFA? The LFRMA methodology consists of two fields of application, the first at the organization level and the second at the project level.


Author(s):  
Rafael Queiroz Gonçalves ◽  
Elisa de Freitas Kühlkamp ◽  
Christiane Gresse von Wangenheim

Many problems in software development projects are due to risks and could be avoided or minimized if identified and treated pro-actively. In this context, software tools to support risk management could be very helpful. However, it is difficult to find a project management tool, accessible to Small and Medium Enterprises (SMEs) that provides adequate support to risk management in conformance with best practices such as the PMBOK. Therefore, this paper has the objective to review support provided by popular project management tools with respect to risk management and to present enhancements made to the open-source tool – dotProject – in order to systematically support risk management aligned with the PMBOK. An initial evaluation identified benefits in the implementation of risk management processes in software SMEs, and, thus, contributing to their projects' success.


Sign in / Sign up

Export Citation Format

Share Document