Effectiveness comparison between Kanban and Scrum on software development projects

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.

Download Full-text

Risk Management and Assessment in Software Development Projects

Èlektronnoe modelirovanie ◽

10.15407/emodel.43.04.113 ◽

2021 ◽

Vol 43 (4) ◽

pp. 113-124

Author(s):

D.V. Saveliev ◽

Keyword(s):

Risk Management ◽

Software Development ◽

Risk Index ◽

Development Projects ◽

Risk Status ◽

Threat Model ◽

The World ◽

Web Systems

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.

Download Full-text

Project and Analyst and Software Engineer Ranking and Job Assignment Problem Solution in Software Development Projects with Fuzzy Multi Criteria Decision Making Techniques

Intelligent and Fuzzy Techniques in Big Data Analytics and Decision Making - Advances in Intelligent Systems and Computing ◽

10.1007/978-3-030-23756-1_94 ◽

2019 ◽

pp. 787-795

Author(s):

İbrahim Yel

Keyword(s):

Decision Making ◽

Software Development ◽

Assignment Problem ◽

Software Engineer ◽

Development Projects ◽

Problem Solution ◽

Multi Criteria Decision Making ◽

Job Assignment

Download Full-text

Suppliers’ software development project start-up practices

International Journal of Managing Projects in Business ◽

10.1108/ijmpb-10-2016-0083 ◽

2017 ◽

Vol 10 (4) ◽

pp. 880-896

Author(s):

Helena Merikoski ◽

Paula Savolainen ◽

Jarmo J. Ahonen

Keyword(s):

Life Cycle ◽

Software Development ◽

Development Project ◽

Cycle Phase ◽

Development Projects ◽

Content Type ◽

Business Context ◽

Software Development Project ◽

Business Goals ◽

Start Up

Purpose The purpose of this paper is to present a life cycle phase of a software development project which is substantial for the success of the project. This paper visualizes the project start-up phase from suppliers’ perspective. Design/methodology/approach The method is a theory building from case studies. The data were collected from three software supplier firms by conducting process modeling separately in each firm. Findings The study resulted in a model of a supplier’s software project start-up which includes start-up practices and involved roles. The results indicate that project start-up is an integral and structured phase of project life cycle, which influences the execution of a software development project, especially from the supplier’s perspective in the project business context. Research limitations/implications The study focuses on the start-up phase of software development projects delivered to external customers. Therefore, developed project start-up model is applicable as such in software supplier firms. Practical implications The project start-up model presented in this paper indicates that project start-up is a complex and multi-dimensional activity in a supplier firm. This study suggests that if the project start-up phase is clearly defined, planned and followed in a supplier firm, it reduces confusion and miscommunication among the people involved in the project and helps to achieve the business goals of a project. Originality/value This study emphasizes that it is necessary to make a distinction between the perspectives of the customer and the supplier when studying projects in the project business context. The findings contribute the new knowledge for managing outsourced software development projects.

Download Full-text