Scrum with eXtreme Programming: An Agile Alternative in Software Development

2020 ◽  
pp. 350-361
Author(s):  
S. Barahona Rojas ◽  
L. Pucha Guzmán ◽  
P. Villamarín Coronel ◽  
A. Yunga Benítez
Keyword(s):  
Software Development ◽  
Extreme Programming

scholarly journals AGILE SOFTWARE DEVELOPMENT

2021 ◽  
Vol 5 (12) ◽  
Author(s):  
Gopalkrishna Waja ◽  
Jill Shah ◽  
Pankti Nanavati
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Extreme Programming ◽  
Software Project ◽  
Research Papers ◽  
Agile Methodology ◽  
Development Methodology ◽  
Software Development Methodology ◽  
Agile Software ◽  
The Impact

Agile Software Development plays a quintessential part in modern day software development. The term Agile refers to frequent reassessment and adaptation of plans and techniques and dividing tasks into shorter tasks for efficiency. Agile Software Development differs considerably from Traditional Software Development Methodology. Agile methodology aims to deliver features of a software project in small steps within a short duration of time (i.e., iterations). Hence, it becomes necessary to use agile software development methodology in todays’ fast-paced revolutionizing software industry. This paper discusses the important subtopics of Agile Software Development which gathered by reviewing/surveying of research papers. First, is the Agile Planning Life Cycle which consists of various stages such as pre-planning, planning, release planning and product backlog management. In the next section, principles such as Scrum, Extreme Programming, Kanban and Lean are discussed. The last section comprises the impact of Agile principles on software quality.

scholarly journals Implementasi Metode Personal Extreme Programming dalam Pengembangan Sistem Manajemen Transaksi Perusahaan (Studi Kasus : CV. Todjoe Sinar Group)

Repositor ◽  
2020 ◽  
Vol 2 (3) ◽  
pp. 261
Author(s):  
Muhammad Ulfi ◽  
Gita Indah Marthasari ◽  
Ilyas Nuryasin
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Extreme Programming ◽  
Agile Software

CV. Todjoe Sinar Group merupakan salah satu perusahaan perusahaan yang bergerak di bidang percetakan. Beberapa masalah yang terjadi dalam pelaksanaan proses bisnis disebabkan oleh pengelolaan proses bisnis yang dijalankan secara manual. Oleh karena itu, diperlukan suatu sistem informasi yang dapat dibangun secara tepat dan cepat. Metode pengembangan perangkat lunak yang dapat memenuhi hal tersebut termasuk kedalam agile software development. Salah satu metode yang termasuk kedalam agile software development adalah Personal Extreme Programming atau PXP. PXP merupakan metode pengembangan dari Extreme Programming yang disesuaikan agar dapat dikerjakan oleh pengembang tunggal. Sistem yang akan dibangun dalam penelitian ini merupakan sistem manajemen transaksi perusahaan. Kebutuhan sistem didapat pada fase requirements. Tahap pengembangan akan dilanjutkan dengan perencanaan iterasi dengan menentukan prioritas kebutuhan dan diskusi bersama. Pengembangan sistem akan dilakukan secara iteratif berdasarkan perencanaan yang telah dilakukan. Apabila terdapat perubahan atau penambahan kebutuhan, maka akan dilakukan perencanaan ulang. Berdasarkan hasil penelitian ini, PXP dapat diimplementasikan dalam studi kasus ini. Kemampuan, pemahaman, dan pengalaman dari seorang pengembang dalam mengerjakan suatu sistem dapat menentukan kesesuaian estimasi pengerjaan sistem dalam metode PXP. Interaksi dengan klien berperan penting dalam proses pengembangan sistem agar proses pengembangan sistem tetap terarah sesuai dengan kebutuhan klien.

Software Modeling Processes

2009 ◽  
pp. 169-178
Author(s):  
Roy Gelbard
Keyword(s):  
Software Development ◽  
System Analysis ◽  
Unified Modeling Language ◽  
Extreme Programming ◽  
Software Modeling ◽  
Application Development ◽  
Levels Of Abstraction ◽  
Model Driven ◽  
Waterfall Model ◽  
Future Direction

Applications require short development cycles and constant interaction with customers. Requirement gathering has become an ongoing process, reflecting continuous changes in technology and market demands. System analysis and modeling that are made at the initial project stages are quickly abandoned and become outmoded. Model driven architecture (MDA), rapid application development (RAD), adaptive development, extreme programming (XP), and others have resulted in a shift from the traditional waterfall model. These methodologies attempt to respond to the needs, but do they really fulfill their objectives, which are essential to the success of software development? Unified modeling language (UML) was created by the convergence of several well-known modeling methodologies. Despite its popularity and the investments that have been made in UML tools, UML is not yet translatable into running code. Some of the problems that have been discovered have to do with the absence of action semantics language and its size. This chapter reviews and evaluates the UML evolution (UML2, xUML), providing criteria and requirements to evaluate UML and the xUML potential to raise levels of abstraction, flexibility, and productivity enhancement. At the same time, it pinpoints its liabilities that keep it from completely fulfilling the vision of software development through a continuous exactable modeling process, considered to be the future direction for modeling and implementation.

Challenges of Gathering User Requirement in eXtreme Programming Project: A Case Study of Highway Construction Monitoring System

2013 ◽  
Vol 594-595 ◽  
pp. 511-515 ◽  
Author(s):  
Ida Aryanie Bahrudin ◽  
Mohd Ezree Abdullah ◽  
Rafizah Mohd Hanifa ◽  
Noordiana Kassim ◽  
Rosfuzah Roslan
Keyword(s):  
Software Development ◽  
Monitoring System ◽  
Highway Construction ◽  
Development Project ◽  
Extreme Programming ◽  
Active Member ◽  
End User ◽  
User Requirement ◽  
Construction Monitoring ◽  
Software Development Project

The successfulness of a software development project is not only based on the tools and the technology used but also really depends on how the developed software meets the end user requirements. Involving end user as an active member of software development team, one of the popular agile methods known as eXtreme Programming (XP) had been selected as the software development methodology. This paper is focused on one of the main practices called on-site customer. The project under study is a web based Highway Construction Monitoring System (HIGHCONS). Challenges related to its implementation throughout the development process and also the suitable solutions in facing the challenges were also considered.

scholarly journals The Role of Customers in Extreme Programming Projects

2021 ◽  
Author(s):  
◽  
Angela Michelle Martin
Keyword(s):  
Software Development ◽  
Well Being ◽  
Development Project ◽  
Extreme Programming ◽  
Agile Methods ◽  
Acceptance Testing ◽  
Software Development Project ◽  
Big Picture ◽  
Definition Of ◽  
Key Steps

<p>eXtreme programming (XP) is one of a new breed of methods, collectively known as the agile methods, that are challenging conventional wisdom regarding systems development processes and practices. Practitioners specifically designed the agile methods to meet the business problems and challenges we face building software today. As such, these methods are receiving significant attention in practitioner literature. In order to operate effectively in the world of vague and changing requirements, XP moves the emphasis away from document-centric processes into practices that enable people. The Customer is the primary organisational facing role in eXtreme Programming (XP). The Customer's explicit responsibilities are to drive the project, providing project requirements (user stories) and quality control (acceptance testing). Unfortunately the customer must also shoulder a number of implicit responsibilities including liaison with external project stakeholders, especially project funders, clients, and end users, while maintaining the trust of both the development team and the wider business. This thesis presents a grounded theory of XP software development requirements elicitation, communication, and acceptance, which was guided by three major research questions. What is the experience of being an XP Customer? We found that teams agree that the on-site customer practice is a drastic improvement to the traditional document-centric approaches. Our results indicate, however, that the customers are consistently under pressure and commit long hours to the project in order to fulfil the customer role. So while this approach to requirements is achieving excellent results, it also appears to be unsustainable and thus constitutes a great risk to XP projects. Who is the XP Customer? The initial definition of XP resulted in many people interpreting the onsite customer to be a single person. This research has highlighted that a customer team always exists, and goes further to outline the ten different roles that were covered on the team, which range from the recognised "Acceptance Tester" role to the less recognised roles of "Political Advisor" and "Super-Secretary". What are the practices that support an XP Customer to perform their role effectively on a software development project? An additional eight customer-focused practices have been uncovered to supplement the existing XP practices. These customer-focused practices together enable customers to sustainably drive XP projects to successful completion. The practices range from those that specifically focus on interaction (both with the programmer team and the larger organisation) e.g. "Programmer On-site" and "Roadshows" to those that specifically look to the well-being and effectiveness of the customer (e.g. "Pair Customering") to those that highlight the key steps or activities that need to occur along the way (e.g. "Big Picture Up-Front" and "Recalibration").</p>

scholarly journals Optimalisasi Manajemen Penerimaan & Penyimpanan Dokumen Fax Menggunakan Algoritma Greedy

2019 ◽  
Vol 6 (6) ◽  
pp. 625
Author(s):  
Intan Purnamasari ◽  
Oman Komarudin
Keyword(s):  
Software Development ◽  
Programming Language ◽  
Interface Design ◽  
Programming Model ◽  
Small And Medium Enterprises ◽  
Unified Modeling Language ◽  
Design Tool ◽  
Extreme Programming ◽  
Machine Maintenance ◽  
Medium Enterprises

<p class="SUBAB1">Mesin <em>fax</em> pada dasarnya mutlak diperlukan bagi sebuah instansi maupun organisasi tertentu. Namun kesulitan yang dihadapi oleh beberapa perusahaan kecil maupun menengah adalah tidak dapat mengalokasikan dana bagi pembelian mesin <em>fax</em>, perawatan, dan perlengkapan komputer sebagai media penunjang. Bagi perusahaan yang telah memiliki mesin <em>fax</em> pun, manajemen dokumen yang diterima melalui<em> fax</em> menjadi kesulitan tersendiri, dari mulai perawatan mesin <em>fax</em>, pemeriksaan ketersediaan kertas dan <em>cartridge</em> tinta, pemeriksaan dokumen yang diterima, serta penyimpanan arsip <em>fax</em> yang diterima. Metodologi penelitian yang akan digunakan pada penelitian ini adalah metode rakayasa perangkat lunak atau <em>Software Development Life Cyle</em> (SDLC) dengan model pemrograman cepat atau <em>Extreme Programming</em>. Desain pemodelan aplikasi menggunakan UML (<em>Unified Modelling Language</em>) yang diimplementasikan menggunakan bahasa pemrograman PHP sebagai algoritma program dan bahasa pemrograman HTML untuk desain tampilan aplikasi dengan <em>tools</em> aplikasi Notepad++. Hasil implementasi dari aplikasi ini adalah yang semula awalnya penerimaan dokumen <em>fax</em> dengan menggunakan mesin <em>fax</em> harus tercetak dan membutuhkan media kertas sebanyak 100% mengingat mesin <em>fax</em> hanya dapat menampilkan pesan dan dapat dibaca setelah tercetak namun setelah  menggunakan apliksi <em>digifax</em> ternyata dapat menghemat penggunaan kertas sebanyak 24,6% sehingga penggunaan kertas menurun menjadi 78,6%. Hal ini karena dengan aplikasi <em>digifax</em> dokumen atau <em>file fax</em> yang diterima dapat disimpan dan dapat dicetak (<em>print</em>) maupun diatur sesuai kebutuhan pengguna.</p><p class="SUBAB1"> </p><p class="SUBAB1"><em><strong>Abstract</strong></em></p><p class="Normal7"><em>Fax machine basically is absolutely necessary for a particular institution or organization. However, the difficulties faced by some small and medium enterprises are not able to allocate funds for the purchase of a fax machine, maintenance, and computer equipment as supporting media. For companies that already have a fax machine too, management documents received via fax into its own difficulties, ranging from fax machine maintenance, checking the availability of paper and ink cartridges, examination of documents received, and the received fax archival storage. The research methodology that will be used in research is a method of software engineering or Software Development Life Cyle (SDLC) with fast programming model or Extreme Programming. Design application modeling using UML (Unified Modeling Language) which is implemented using the PHP programming language as the program algorithm and HTML programming language for interface design tool applications with Notepad + + applications.</em><em> </em><em>The results of</em><em> the implementation of this application is that the original fax document acceptance initially using fax machines need to be printed and paper media as much as 100% given the fax machine can only display a message and can be read as printed digifax but after using the same practice was able to save the use of paper as much as 24, 6%, so the use of paper decreased to 78.6%. This is because the application digifax documents or files received faxes can be stored and can be printed (print) and arranged according to user needs.</em><em></em></p><p class="SUBAB1"><em><strong><br /></strong></em></p><p class="SUBAB1"><strong><br /></strong></p>

Sign in / Sign up

Export Citation Format

Share Document