Scrum with the Spices of Agile Family: A Systematic Mapping

Ashraf, Sara

doi:10.5815/ijmecs.2017.11.07

Cited by 18 publications

(19 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Salah et al [9] recommended a hybrid form of agile based frameworks in 2017, to overcome the challenges with Scrum like budget estimation, project delivery and goal achievement. In 2017, Ashraf and Aftab [7] proposed with insightful understanding that the Scrum requires to be plugged in with different Agile models to enhance the productivity and quality of the product. Hanslo and Mnkandla [6] performed narrative reviews in 2017, on Scrum challenges like structure of organization and its suitability with Scrum, lack of expertise in Scrum team members and proposed Scrum variants by adopting traditional software development model.…”

Section: Empirical Analysismentioning

confidence: 99%

Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

Bhavsar*¹,

Shah²,

Gopalan³

2020

IJITEE

View full text Add to dashboard Cite

Software Engineering (SE) technologies are emerging day by day and seeking ABPR (Agile Business Process Reengineering) for Software Engineering Management (SEM) frameworks in software development organizations. BPR can enable organizational capabilities to initiate and implement critical change in execution. Under the roof of agile and on the base of empiricism, the Scrum has been proven itself as an ABPR approach for software engineering management in the software development organizations, across the world, by improving productivity, self-organization and collaboration for standard software development processes. Scrum has been leading software project development practices using its own characteristics: Artifacts, Pillars, Values, Events and Roles. But still software project development organizations are facing some issues with their software project development and management processes, like no documentation policy which results into inaccurate estimation, internal states of each work item flowing through the Scrum Board, Sprint tracker and prediction towards goal achievement which can be considered as challenges for Scrum due its limitations as well as Scrum does not allow, any alteration in its rules. Such issues have raised a question against implementation of Scrum and have opened the door for the next level of research to answer the question, how to overcome the limitations of Scrum. Kanban can provide the solution to some of these issues but it can’t provide complete SEM solutions to software Development Organizations. The aim of this research study is empirical analysis about how the formation of hybrid framework Scrumban as an integration of Scrum with Kanban, can resolve challenges of Scrum; using literature reviews, case study reviews, and research surveys; and this research has proposed a conceptual customized Scrumban framework, by keeping Kanban in the center of customization under the bound of Scrum rules. This research also concludes limitations of Scrumban, like project documentation, planning, large scaled project, distributed environment, team capabilities etc.; as each method has its own limitations.

show abstract

Section: Empirical Analysismentioning

confidence: 99%

Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

Bhavsar*¹,

Shah²,

Gopalan³

2020

IJITEE

View full text Add to dashboard Cite

show abstract

“…In [15] the authors showed the importance of the SCRUM agile method and how it's critical when other researchers think about making or producing a new hybrid agile methodology. SCRUM is the best from the author's opinion based on a review they already made.…”

Section: Related Workmentioning

confidence: 99%

An Iterative Hybrid Agile Methodology for Developing Archiving Systems

Almajed¹,

Medhat²,

El-Shishtawy³

2019

IJSEA

View full text Add to dashboard Cite

With the massive growth of the organizations files, the needs for archiving system become a must. A lot of time is consumed in collecting requirements from the organization to build an archiving system. Sometimes the system does not meet the organization needs. This paper proposes a domain-based requirement engineering system that efficiently and effectively develops different archiving systems based on new suggested technique that merges the two best used agile methodologies: extreme programming (XP) and SCRUM. The technique is tested on a real case study. The results shows that the time and effort consumed during analyzing and designing the archiving systems decreased significantly. The proposed methodology also reduces the system errors that may happen at the early stages of the development of the system.

show abstract

“…They achieved improved quality and on-time delivery simultaneously through implementation of this hybrid. Similarly, other researchers also integrated Scrum with other Agile members [41].…”

Section: Background and Related Workmentioning

confidence: 99%

“…Therefore, metrics help the teams to acquaint with the development progress, as well as to discover the unattended areas that need improvement. Moreover, metrics improve the understanding of stakeholders by increasing the transparency and visibility of end-to-end flow in a complex system [41]. Conventional metrics are not appropriate for ASD, so there are some specific metrics used to track the progress, team's performance, and product quality.…”

Section: Product and Process Metricsmentioning

confidence: 99%

Pragmatic Evaluation of IScrum & Scrum

Ashraf¹,

Aftab²

2018

IJMECS

Self Cite

View full text Add to dashboard Cite

Scrum has emerged as a most adopted and most desired Agile approach that provides corporate strategic competency by laying a firm foundation for project management. Scrum, being more of a framework than a rigid methodology, offers maximum flexibility to its practitioners. However, there are several challenges confronted during its implementation for which certain researchers not only adapted, but also augmented Scrum with other Agile practices. One such effort is IScrum, an Improved Scrum process model. In this paper an empirical study has been conducted for analyzing the two models i.e. classical Agile Scrum model and IScrum process model. There are two goals of this study: first is to validate the IScrum and the second goal is to evaluate it in comparison with the traditional Scrum model. Subsequently, the study will describe and highlight which characteristics of Scrum are enhanced in IScrum. Furthermore, a survey is used to investigate the teams' experience with both models. The results of survey and case-study have been examined and compared to find out if IScrum performs well than Scrum in software development. The outcomes advocate that the improvements were quite effective in resolving most of the problem areas. The IScrum can thus be adopted by industry practitioners a best choice.

show abstract

Scrum with the Spices of Agile Family: A Systematic Mapping

Cited by 18 publications

References 27 publications

Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

An Iterative Hybrid Agile Methodology for Developing Archiving Systems

Pragmatic Evaluation of IScrum & Scrum

Contact Info

Product

Resources

About