Comparing Traditional and Agile Software Development Approaches: Case of Personal Extreme Programming

Asri, Sri Andriati and Sunaya, I Gusti Agung Made and Prihatini, Putu Manik and Setiawan, Widyadi (2018) Comparing Traditional and Agile Software Development Approaches: Case of Personal Extreme Programming. In: International Conference on Science and Technology (ICST 2018), 18-19 Oktober 2018, Nusa Dua, Bali.

	Text (Similarity Check) IIIA2a1b_cek_similarity_Comparing_Traditional_and_Agile_Software_Development_Approaches.pdf - Supplemental Material Available under License Creative Commons Attribution Non-commercial Share Alike. Download (902kB)
	Text (Correspondence Letter) IIIA2a1b_Bukti_korespondensi_prosiding_Comparing_Traditional_and_Agile_Software_Development_Approaches_Case_of_Personal_Extreme_Programming.pdf - Supplemental Material Available under License Creative Commons Attribution Non-commercial Share Alike. Download (1MB)
	Text (Article) IIIA2a1b_artikel_Comparing _Traditional_and_Agile_Software_Development_Approaches.pdf - Published Version Available under License Creative Commons Attribution Non-commercial Share Alike. Download (2MB)

Abstract

Generally, there are two approaches to software development, traditional and agile. Traditional is heavy and well documented, agile is light and less documentation. Personal Extreme Programming (PXP) is one of the agile approaches that iterative, more flexible and responsive to changes. This research compared Waterfall as one of the traditional methods and PXP as agile in the requirement analysis, planning and implementation processes. The project that used to compares those approaches is job training A application. PXP used a closed questionnaire with weighted questions to determined which one of user requirement has the highest priority. The planning phase determined the time estimation for completed each task of making the application. PXP provided more short developing time less than three months. Implementing phase in PXP is a unit testing, code generation, and code refactoring when a user story finished, there for a mistake or an error can be detecting earlier, unlike the waterfall that often tested the application at the end of project development. The result is the agile approach (PXP) gives more convenient and flexibility for developing the application

Actions (login required)

View Item