IDEAS home Printed from https://ideas.repec.org/a/gam/jsusta/v13y2021i4p1909-d497043.html
   My bibliography  Save this article

Agile Beeswax: Mobile App Development Process and Empirical Study in Real Environment

Author

Listed:
  • Hazem Abdelkarim Alrabaiah

    (Department of Languages and Computer Systems, University of Granada, 18010 Granada, Spain)

  • Nuria Medina-Medina

    (Department of Languages and Computer Systems, University of Granada, 18010 Granada, Spain)

Abstract

Mobile application development is a highly competitive environment; agile methodologies can enable teams to provide value faster, with higher quality and predictability, and a better attitude to deal with the continuous changes that will arise in the mobile context application (App), and the positive impact of that on sustainable development through continuous progress. App development is different from other types of software. For this reason, our objective is to present a new agile-based methodology for app development that we call Agile Beeswax. Agile Beeswax is conceived after identifying the mobile development process’s issues and challenges, and unique requirements. Agile Beeswax is an incremental, iterative development process composed of two main iterative loops (sprints), the incremental design loop and the incremental development loop, and one bridge connecting these two sprints. Agile Beeswax is structured in six phases, idea and strategy, user experience design, user interface design, design to development, handoff and technical decisions, development, and deployment and monitoring. One of its main strengths is that it has been created with academic and business perspectives to bring these two communities closer. To achieve this purpose, our research methodology comprises four main phases: Phase 1: Extensive literature review of mobile development methodologies, Phase 2: Interviews with mobile application developers working in small to medium software companies, Phase 3: Survey to extract valuable knowledge about mobile development (which was carefully designed based on the results of the first and the second phases), and Phase 4: Proposal of a new methodology for the agile development of mobile applications. With the aim of integrating both perspectives, the survey was answered by a sample of 35 experts, including academics and developers. Interesting results have been collected and discussed in this paper (on issues such as the development process, the tools used during this process, and the general issues and challenges they encountered), laying the foundations of the methodology Agile Beeswax proposed to develop mobile apps. Our results and the proposed methodology are intended to serve as support for mobile application developers.

Suggested Citation

  • Hazem Abdelkarim Alrabaiah & Nuria Medina-Medina, 2021. "Agile Beeswax: Mobile App Development Process and Empirical Study in Real Environment," Sustainability, MDPI, vol. 13(4), pages 1-33, February.
  • Handle: RePEc:gam:jsusta:v:13:y:2021:i:4:p:1909-:d:497043
    as

    Download full text from publisher

    File URL: https://www.mdpi.com/2071-1050/13/4/1909/pdf
    Download Restriction: no

    File URL: https://www.mdpi.com/2071-1050/13/4/1909/
    Download Restriction: no
    ---><---

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:gam:jsusta:v:13:y:2021:i:4:p:1909-:d:497043. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: MDPI Indexing Manager (email available below). General contact details of provider: https://www.mdpi.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.