Adopting an Agile Approach for the Development of Mobile Applications

Flora, Harleen K.; Chande, Swati V.

doi:10.5120/16454-6199

Cited by 28 publications

(24 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…According to scientific evidence from their research outcome, Scrum will play a vital role in improvement in productivity of software projects. Harleen et al [6] surveyed in 2014 in mobile application development organization and evaluated that agile software engineering management methodologies like Scrum, Lean and XP are best suited for their mobile application software development unit and improved utilization of resources. Scrum has proven itself as a product creation framework by stakeholder involvement for improvement in customer values.…”

Section: Empirical Analysismentioning

confidence: 99%

Scrum: An Agile Process Reengineering In Software Engineering

Bhavsar*¹,

Shah²,

Gopalan³

2020

IJITEE

View full text Add to dashboard Cite

BPR (Business Process Re-engineering) is an organizational mechanism leading organization towards change management as and when it is required. In the form BPR, Agile practices have had a remarkable impact on Software Engineering Management (SEM) in software development organizations across the world. It has enhanced collaboration and productivity of Software Engineering (SE) teams and improved the level of quality of software products. Nowadays Scrum has been trending into software development organizations as a standard SDLC approach. Scrum is the framework of the Agile methodology, built on empiricism control theory, asserts that experience brings knowledge and increases decision making capabilities. The empiricism control theory is built on three pillars: Adaptation, Inspection and Transparency. This research study presents Scrum as a trending SDLC framework using empirical analysis. We have analyzed literature reviews, case studies, and research surveys; and implemented Scrum in our software development unit and carried out the reasons, why Scrum is trending in software development organizations. How the scrum artifacts, events and values play a vital role in upholding the Scrum pillars and strengthen the capabilities of Scrum team members to address the software engineering management challenges; compared to traditional software development approaches.

show abstract

Section: Empirical Analysismentioning

confidence: 99%

Scrum: An Agile Process Reengineering In Software Engineering

Bhavsar*¹,

Shah²,

Gopalan³

2020

IJITEE

View full text Add to dashboard Cite

show abstract

“…Without extensive communication and work on soft skills, we may not achieve the expected performance boost for Scrum. [21] As a result effective Distributed Scrum is possible only when the customer is ready to invest in communication tools and cross-location business trips [3].…”

Section: Literature Reviewmentioning

confidence: 99%

A New Approach for Distributed Software Engineering Teams Based on Kanban Method for Reducing Dependency

Yacoub¹,

Mostafa²,

Farid³

2016

JSW

View full text Add to dashboard Cite

In today's globalization with the shift towards Agility. Agile practices highly evaluates communication to achieve improvement in the software development process and among development team members. Stable communication can be difficult and a challenge in distributed agile environment. Pointless communications and actions in software development projects do not decrease work in progress and may cause failure. Getting rid of such a waste leads to a continuous flow process improvement, decreasing team dependency. This is astudy of a distributed Kanban, for web portal as a proposed solution for mitigating the communication challenges encountered in such environment. The declared benefits of Kanban have gained. significant importance as an agile project management method in the software development industry. Kanban approach helps managing and measuring the flow of work across developing teams. Results show that Kanban has a positive effect, leading the team to communicate together when it is needed. Compared to the previously used Scrum method by the sample teams, the use of Kanban causes dependency reduction for the distributed team by 27%, keeping the pace of the development harmonized across the whole team and improving maturity. This led to 98.9 of a done status for user stories, and 30% customer satisfaction increase.

show abstract

“…Thus, when composing an Agile team, the size of the project and the team must be considered [55]. In Agile method selection, the project nature is taken into account [97], and particularly the project size [17], [41], [64], [66], [80], [95], [97], [102].…”

Section: ) Sizementioning

confidence: 99%

“…Team members' competencies affect the development pace and the delivery of software according to customers' requirements. Thus, the team's technical skills is a crucial factor to consider in the selection of an Agile method as team members may not be familiar with all Agile methods [6], [64], [66], [68], [70], [97], [111].…”

Section: ) Development Teams' Competency (Technical Skills and Expermentioning

confidence: 99%

Key Factors for Selecting an Agile Method: A Systematic Literature Review

Alqudah¹,

Razali²

2017

International Journal on Advanced Science, Engineering and Information Technology

View full text Add to dashboard Cite

Abstract-Agile methods have become popular in recent years because the success rate of project development using Agile methods is better than structured design methods. Nevertheless, less than 50 percent of projects implemented using Agile methods are considered successful, and selecting the wrong Agile method is one of the reasons for project failure. Selecting the most appropriate Agile method is a challenging task because there are so many to choose from. In addition, potential adopters believe that migrating to an Agile method involves taking a drastic risk. Therefore, to assist project managers and other decision makers, this study aims to identify the key factors that should be considered when selecting an appropriate Agile method. A systematic literature review was performed to elicit these factors in an unbiased manner, and then content analysis was used to analyze the resultant data. It was found that the nature of the project, development team skills, project constraints, customer involvement and organizational culture are the key factors that should guide decision makers in the selection of an appropriate Agile method based on the value these factors have for different organizations and/or different projects.

show abstract

Adopting an Agile Approach for the Development of Mobile Applications

Cited by 28 publications

References 11 publications

Scrum: An Agile Process Reengineering In Software Engineering

Scrum: An Agile Process Reengineering In Software Engineering

A New Approach for Distributed Software Engineering Teams Based on Kanban Method for Reducing Dependency

Key Factors for Selecting an Agile Method: A Systematic Literature Review

Contact Info

Product

Resources

About