Farhan Sadik Ferdous
Research Subjects
Research Interests
Farhan Sadik Ferdous has a total of 3 co-authors. Here are the top co-authors by number of shared publications:
- Akinul Islam Jony
Economics and Business Studies, Universitat Oberta de Catalunya, 08018 Barcelona, Spain
1 shared publication - Tapu Biswas
School of Mathematics, Statistics and Actuarial Science, University of Essex, Colchester, UK
1 shared publication - Zinniya Taffannum Pritee1 shared publication
Latest Publications
- Open Access
- 8 April 2024
- Published by MECS Publisher in International Journal of Information Technology and Computer Science
- Vol. 16 (2) , 57-65
ScrumSpiral: An Improved Hybrid Software Development Model
In the lightning-quick world of software development, it is essential to find the most effective and efficient development methodology. This thesis represents "Scrum Spiral" which is an improved hybrid software development model that combines the features of Scrum and Spiral approach to enhance the software development process. This thesis aims to identify the usefulness of "ScrumSpiral" methodology and compare it with other hybrid software development models to encourage its use in software development projects. To develop this hybrid model, we did extensive research on the software engineering domain and decided to create a hybrid model by using Scrum and Spiral, named "Scrum Spiral" which is suitable for complicated projects and also for those projects whose requirements are not fixed. Traditional software development models face numerous challenges in rapidly changing markets. By developing this kind of hybrid model, we want to overcome these kinds of limitations and present the software development community with a novel concept for better project results. Final outcome of this thesis was that we developed a model that should be able to complete the project according to the expected schedule, satisfy customer requirements, and obtain productivity through team coordination. The significance of the hybrid model "Scrum Spiral" is reflected in its ability to offer flexibility towards various size projects, proactive risk management to identify all risks before developing the system, and result in higher-quality outcomes for those projects whose requirements are not properly described initially in the project.
- 8 April 2024
- Published by MECS Publisher in International Journal of Information Technology and Computer Science
- Vol. 16 (2) , 57-65
Open AccessScrumSpiral: An Improved Hybrid Software Development Model
In the lightning-quick world of software development, it is essential to find the most effective and efficient development methodology. This thesis represents "Scrum Spiral" which is an improved hybrid software development model that combines the features of Scrum and Spiral approach to enhance the software development process. This thesis aims to identify the usefulness of "ScrumSpiral" methodology and compare it with other hybrid software development models to encourage its use in software development projects. To develop this hybrid model, we did extensive research on the software engineering domain and decided to create a hybrid model by using Scrum and Spiral, named "Scrum Spiral" which is suitable for complicated projects and also for those projects whose requirements are not fixed. Traditional software development models face numerous challenges in rapidly changing markets. By developing this kind of hybrid model, we want to overcome these kinds of limitations and present the software development community with a novel concept for better project results. Final outcome of this thesis was that we developed a model that should be able to complete the project according to the expected schedule, satisfy customer requirements, and obtain productivity through team coordination. The significance of the hybrid model "Scrum Spiral" is reflected in its ability to offer flexibility towards various size projects, proactive risk management to identify all risks before developing the system, and result in higher-quality outcomes for those projects whose requirements are not properly described initially in the project.