Abstract

This paper shows the conduct and result of an experiment regarding combining two software development technologies – Scrum and Kanban – into one technology that will take the best sides of these methodologies and will be convenient and efficient to use. Scrum and Kanban development methodologies are the object of study. Existing flexible development methodologies are analyzed, including XP, Lean, FDD, as well as Scrum and Kanban in more detail. A comparative table of the last two methodologies is also drawn up, reflecting their differences in a number of criteria. These methodologies are found to have some drawbacks and could be removed in the new methodology, thus improving existing methodologies for specific purposes. The new methodology should be fairly flexible and adaptable for all members of the software development team. This methodology should be easy to use and have some set of rules. An experiment is conducted to demonstrate how to combine the methodology with maximum efficiency using Petri nets. First, the Scrum and Kanban methodologies were modeled. Then, based on these two models, as well as the new rules, a new model for the methodology was formed. After conducting the experiment, the model reveals what the proposed development methodology should look like. It can be used in software development. Creating this methodology on the basis of two existing ones is a very challenging task today, as it has 3 tasks – to improve the existing methodologies of Scrum and Kanban, to create a set of rules for the new methodology, and to make it as flexible, adaptive and useful as possible.

Highlights

  • Nowadays, it is very important to adhere to a certain methodology during software development for managing product development, which provides, in particular, planning, monitoring and analysis of the implementation of current tasks to achieve the project goal

  • The adaptation and use of a specific methodology for software development, as well as the creation of a combined methodology that would be better adapted to the current conditions of implementation of software projects, is an important and relevant task

  • The new methodology is suitable for different types of teams and improves their performance

Read more

Summary

Introduction

It is very important to adhere to a certain methodology during software development for managing product development, which provides, in particular, planning, monitoring and analysis of the implementation of current tasks to achieve the project goal. – classical methodologies, for example, Waterfall, Iterative; – Flexible development methodologies such as Extreme Programming (XP), Lean (Lean software development), FDD (Feature Driven Development), DSDM (Dyna­ mics System Development Method), Crystal, Scrum and Kanban. Each of these methodologies needs to be adapted to the implementation of the specific project taking into account the peculiar properties of the organization that creates a project. One of the best approaches is Agile methodology, which is a flexible development methodology, and its representatives for small development teams are Scrum and Kanban They are used in work on software projects and allow to complete the tasks as quickly and efficiently as possible. These qualities were investigated in an experiment which allowed to compare the characteristics on the graph models and to offer a combined variant of the method with better performance

The object of research and its technological audit
The aim and objectives of research
Research of existing solutions of the problem
Methods of research
Research results
SWOT analysis of research results
Conclusions
Kratko o metodologiyakh razrabotki PO
12. Kanban Encyclopedia
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call