The DOI matches its Crossref record.
Agile Beeswax: Mobile App Development Process and Empirical Study in Real Environment
Open accessAbstract
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.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 25
- Flora, 2014, Adopting an agile approach for the development of mobile applications, Int. J. Comput. Appl., 94, 43
- Wasserman, A.I. (2010, January 7–8). Software engineering issues for mobile application development. Proceedings of the FSE/SDP Workshop on Future of Software Engineering Research—FoSER, Santa Fe, NM, USA. · DOI
- Kumar, 2016, Challenges and best practices in mobile application development, Imp. J. Interdiscip. Res., 2, 1607
- Mahmud, D., and Abdullah, A. (2015, January 28–31). Agile: A natural fit in mobile application development process. Proceedings of the 7th International Conference on Internet (ICONI), Abu Dhabi, United Arab Emirates.
- Abrahamsson, P., Hanhineva, A., Hulkko, H., Ihme, T., Jlinoja, J., Korkala, M., Koskela, J., Kyllnen, P., and Salo, O. (2004, January 4–28). Mobile-D. Proceedings of the Companion to the 19th Annual ACM SIGPLAN Conference on Object-Oriented Programming Systems, Languages, and Applications—OOPSLA, Vancouver, BC, Canada. · DOI
- Jeong, Y., Lee, J., and Shin, G. (2008, January 17–20). Development process of mobile application SW based on Agile methodology. Proceedings of the 10th International Conference on Advanced Communication Technology, Gangwon-Do, Korea. · DOI
- Rahimian, V., and Ramsin, R. (2008, January 3–6). Designing an Agile methodology for mobile software development: A hybrid method engineering approach. Proceedings of the Second International Conference on Research Challenges in Information Science, Marrakech, Morocco. · DOI
- Ågerfalk, P.J., Brinkkemper, S., Gonzalez-Perez, C., Henderson-Sellers, B., Karlsson, F., Kelly, S., and Ralyté, J. (2007). Modularization constructs in method engineering: Towards common ground?. Situational Method Engineering: Fundamentals and Experiences, Springer.
- Scharff, C., and Verma, R. (2010, January 1–8). Scrum to support mobile application development projects in a just-in-time learning context. Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering—CHASE, Cape Town, South Africa. · DOI
- Cunha, T.F., Dantas, V.L., and Andrade, R.M. (2011, January 28–30). SLeSS: A Scrum and Lean Six Sigma integration approach for the development of Sofware customization for mobile phones. Proceedings of the 25th Brazilian Symposium on Software Engineering, Sao Paulo, Brazil. · DOI
- Alsabi, E., and Dahanayake, A. (2016). Smart modeling for lightweight mobile application development methods. New Trends in Databases and Information Systems, Springer. Communications in Computer and Information Science. · DOI
- Martinez, 2020, An Agile-based integrated framework for mobile application development considering Ilities, IEEE Access, 8, 72461, 10.1109/ACCESS.2020.2987882 · DOI
- Kirmani, 2017, Agile methods for mobile application development: A comparative analysis, Int. J. Adv. Res. Comput. Sci., 8, 1200
- Ahmad, 2018, An empirical study of investigating mobile applications development challenges, IEEE Access, 6, 17711, 10.1109/ACCESS.2018.2818724 · DOI
- Al-Rabaiah, H.A., and Medina-Medina, N. (August, January 29). Mobile application development process in real environments. Proceedings of the International Conference on Software Engineering Research and Practice (SERP), Las Vegas, NV, USA. Available online: https://csce.ucmss.com/cr/books/2019/LFS/CSREA2019/SER4050.pdf.
- Ghandi, L., Silva, C., Martinez, D., and Gualotuna, T. (2017, January 14–17). Mobile application development process: A practical experience. Proceedings of the 12th Iberian Conference on Information Systems and Technologies (CISTI), Lisbon, Portugal. · DOI
- Ashishdeep, 2016, Software process models for mobile application development: A review, Comput. Sci. Electron. J., 7, 150
- Rubin, J., and Chisnell, D. (2008). Handbook of Usability Testing: How to Plan, Design and Conduct Effective Tests, John Wiley and Sons.
- Aguilar, M., and Zapata, C. (2016). Integrating UCD and an Agile methodology in the development of a mobile catalog of plants. Advances in Ergonomics Modeling, Usability & Special Populations, Springer. · DOI
- Pratt, A., and Nunes, J. (2013). Interactive design: An introduction to the theory and application of user-centered design. Choice Rev. Online, 50. · DOI
- Mojica, 2014, A large-scale empirical study on software reuse in mobile apps, IEEE Softw., 31, 78, 10.1109/MS.2013.142 · DOI
- Ruiz, I.J., Nagappan, M., Adams, B., and Hassan, A.E. (2012, January 11–13). Understanding reuse in the Android market. Proceedings of the 20th IEEE International Conference on Program Comprehension (ICPC), Passau, Germany. · DOI
- Mascheroni, M.A., and Irrazábal, E. (2018, January 8–12). Problemas que afectan a la Calidad de Software en Entrega Continua y Pruebas Continuas. Proceedings of the XXIV Congreso Argentino de Ciencias de la Computación, La Plata, Argentina.
- Schwaber, K. (2004). Agile Project Management with Scrum, Microsoft Press.
- Garneli, 2016, Serious games as a malleable learning medium: The effects of narrative, gameplay, and making on students’ performance and attitudes, Br. J. Educ. Technol., 48, 842, 10.1111/bjet.12455 · DOI
Cited by
Sorted by citations
Bakhtiar, M., & Chotijah, U. (2025) · Jurnal Nasional Komputasi dan Teknologi Informasi (JNKTI) · doi:10.32672/jnkti.v8i6.10118
Metadata
- Authors
- Alrabaiah, H. A., & Medina-Medina, N.
- Affiliations
- Universidad de Granada (ES)
- Corresponding author
- Alrabaiah, Hazem Abdelkarim
- Venue
- Sustainability
- Publisher
- MDPI AG
- Published
- 2021-02-10
- Volume
- 13
- Issue
- 4
- Pages
- 1909
- ISSN
- 2071-1050 (ISSN-L)
- OpenAlex
- W3126823017
- Cited by
- 19
- References
- 0
- Citations by year
- 2025: 6 · 2024: 3 · 2023: 7 · 2022: 3
- FWCI
- 2.94
- Type
- journal article
- Language
- en
- Open access
- gold
- doi.org
- Licence
- Locations
- Sustainability (publishedVersion, cc-by)
- RePEc: Research Papers in Economics (submittedVersion)
- Institutional Repository of the University of Granada (University of Granada) (submittedVersion, cc-by)
- DOAJ (DOAJ: Directory of Open Access Journals) (submittedVersion, cc-by-sa)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Information Systems › Mobile and Web Applications
- Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
- Keywords
- mobile application development, agile software development, sprinting, incremental development, user experience design, user interface design, handover, developer survey
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
