Experience in Applying of ISO 29110 to Agile Software Development
Article Sidebar
Main Article Content
Abstract
We advocate the fact that the standard for software development should be established in an organisation, since the dynamic of software development projects leads more error-prone and time consuming. The standard is expected to reduce the difficulties of development activities, in particular, analysis and design. This research is aimed to apply the standard ISO/IEC 29110 and agile method. The standard is studied and the supporting tools are analyzed. The good practice of applying the standard ISO/IEC 29110 with agile practice is purposed. A sample group of software development teams is created and coached according to our approach. Then, the sample group works on their own software development projects based on the purposed good practice. The questionnaire is given to the group in order to collect the feedback and comments on the approach. Based on the results of questionnaire, it shows that software development teams are satisfied with the approach, especially, in the term of requirements tracking, responding time to customers, and change management with 4.73, 4.52, and 4.33 out of 5, respectively.
Article Details
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
I/we certify that I/we have participated sufficiently in the intellectual content, conception and design of this work or the analysis and interpretation of the data (when applicable), as well as the writing of the manuscript, to take public responsibility for it and have agreed to have my/our name listed as a contributor. I/we believe the manuscript represents valid work. Neither this manuscript nor one with substantially similar content under my/our authorship has been published or is being considered for publication elsewhere, except as described in the covering letter. I/we certify that all the data collected during the study is presented in this manuscript and no data from the study has been or will be published separately. I/we attest that, if requested by the editors, I/we will provide the data/information or will cooperate fully in obtaining and providing the data/information on which the manuscript is based, for examination by the editors or their assignees. Financial interests, direct or indirect, that exist or may be perceived to exist for individual contributors in connection with the content of this paper have been disclosed in the cover letter. Sources of outside support of the project are named in the cover letter.
I/We hereby transfer(s), assign(s), or otherwise convey(s) all copyright ownership, including any and all rights incidental thereto, exclusively to the Journal, in the event that such work is published by the Journal. The Journal shall own the work, including 1) copyright; 2) the right to grant permission to republish the article in whole or in part, with or without fee; 3) the right to produce preprints or reprints and translate into languages other than English for sale or free distribution; and 4) the right to republish the work in a collection of articles in any other mechanical or electronic format.
We give the rights to the corresponding author to make necessary changes as per the request of the journal, do the rest of the correspondence on our behalf and he/she will act as the guarantor for the manuscript on our behalf.
All persons who have made substantial contributions to the work reported in the manuscript, but who are not contributors, are named in the Acknowledgment and have given me/us their written permission to be named. If I/we do not include an Acknowledgment that means I/we have not received substantial contributions from non-contributors and no contributor has been omitted.
References
2. ISO/IEC 29110-2-1, Software Engineering - Lifecycle Profiles for Very Small Entities (VSEs) - Part 2-1: Framework and taxonomy, ISO/IEC 29110, 2015.
3. ISO/IEC TR 29110-3-1, Software Engineering - Lifecycle Profiles for Very Small Entities (VSEs) - Part 3: Assessment Guide, ISO/IEC 29110, 2015.
4. ISO/IEC 29110-4-1, Software Engineering - Lifecycle Profiles for Very Small Entities (VSEs) - Part 4-1: Profile specifications: Generic profile group, ISO/IEC 29110, 2011.
5. F. Plante, and C. Y. Laportee, “Implementation of an Agile-ISO 29110 Software Process in a Large Canadian Financial Institution,” 2018. [Online]. Available: ResearchGate, https://www.researchgate.net/publication/326271657_Implementation_of_an_Agile-ISO_29110_Software_Process_in_a_Large_Canadian_Financial_Institution. [Accessed: June 5, 2019].
6. M. Takeuchi, N. Kohtake, S. Shirasaka, Y. Koishi, K. Shioya, “Report on an assessment experience based on ISO/IEC 29110,” Journal of Software: Evolution and Process, 26(3), pp. 306-312. 2014.
7. D. A. Marca and B. Perdue, “Software engineering approach and tool set for developing Internet applications,” in Proceedings of the 22nd international conference on Software engineering, 2000. pp. 738-741.
8. W. Jirapanthong, "Comparative Study Between Software Product Line and Waterfall Process," Journal of Information Science and Technology, Vol.1, No.1 , pp.1-8, Jan 2010.
9. บัญญพนต์ พูลสวัสดิ์ และ พนมพร ดอกประโคน, "เกมบนโปรแกรมเชิงจินตภาพและแนวคิดเชิงคำนวณอย่างเป็นระบบ," Journal of Information Science and Technology, Vol.6, No.2, pp.9-16, July 2016 .
10. I. Suttichurchart, P. Metapatara, P. Chuangyanyong, and P. Chiravirakul, " Esc Challenge Game application for enhancing executive functions ," Journal of Information Science and Technology, Vol.8, No.1 , pp.35-46, Jan 2018.
11. “Manifesto for Agile Software Development”. 2001.[Online]. Available: https://agilemanifesto.org/. [Accessed: March 26, 2019].
12. K. Beck, Extreme Programming Explained: Embrace Change, 2nd edition. Addison-Wesley, 2004. ISBN 978-0-321-27865-4.
13. J. Carroll and D. Morris. Agile Project Management in easy steps, 2nd edition. In Easy Steps. p. 162. ISBN 978-1-84078-703-0.
14. “The home of Scrum”. [Online]. Available: https://www.scrum.org/. [Accessed: April 23, 2019].
15. “Atlassian JIRA”. [Online] Available: https://www.atlassian.com/software/jira. [Accessed: March 17, 2019].
16. “Bugzilla”. [Online]. Available: https://www.bugzilla.org/. [Accessed: March 17, 2019].
17. “Redmine”. [Online]. Available: https://www.redmine.org/. [Accessed: March 19, 2019].
18. “GNATS”. [Online]. Available: https://manpages.ubuntu.com/manpages/precise/man7/gnats.7.html. [Accessed: April 4, 2019].
19. “YouTrack”. [Online]. Available: https://www.jetbrains.com/youtrack/. [Accessed: April 4, 2019].
20.“Trac”. [Online]. Available: https://www.jetbrains.com/youtrack/. [Accessed: April 5, 2019].
21. A. Chernigovskiy, R. Tsarev, and D. Kapulin, “Scheduling algorithms for automatic control systems for technological processes,” Journal of Physics: Conference Series 803 art. no. 012028, 2017.
22. A. Chernigovskiy, D. Kapulin, E. Noskova, T. Yamskikh, and R. Tsarev, “Production scheduling with ant colony optimization,” IOP Conference Series: Earth and Environmental Science 87 art. no. 062002, 2017.
23. W. Clark, The Gantt Chart: A Working Tool of Management. New York, NY: Ronald Press, 1922.
24. T. Flouris and D. Lock, Managing Aviation Projects from Concept to Completion. Ashgate Publishing Limited, 2012. ISBN 978-1-4094-8613-8.
25. “Gitlab”. [Online]. Available: https://gitlab.com/gitlab-org. [Accessed: April 11, 2019].
26. “ProWorkflow”. [Online]. Available: https://www.proworkflow.com/. [Accessed: April 11, 2019].
27. “Hive”. [Online]. Available: https://hive.com/. [Accessed: April 11, 2019].
28. “MS Project, Release notes for Monthly Channel releases in 2019". [Online]. Available: https://docs.microsoft.com/en-us/officeupdates/monthly-channel-2019. [Accessed: April 19, 2019].
29. “Eclipse”. [Online]. Available: https://www.eclipse.org/. [Accessed: April 11, 2019].