Hasil Pencarian  ::  Simpan CSV :: Kembali

Abstrak :
Penggunaan teknologi digital yang semakin luas mendukung perusahaan untuk membuat strategi bisnis yang lebih baru, yaitu mengembangkan ekosistem digital berbasis perangkat lunak dengan memanfaatkan hubungan antara bentuk dan fungsi produk di dalam perusahaan. Perusahaan perbankan dituntut untuk menerapkan pengembangan dengan metodologi agile agar dapat bersaing dengan cepat, meningkatkan kepuasan pelanggan, memperluas segmen pasar, meningkatkan produktivitas dan mengetahui kebutuhan pelanggan. Namun dalam realita nya penerapan metodologi agile itu sendiri dapat menjadikan suatu tantangan dikarenakan praktik-praktik yang harus dipatuhi dan dilaksanakan diperlukan prosedur yang dapat mengakibatkan deliverables fungsi atau fitur tidak sesuai dengan rencana pengembangan. Hal ini berakibat juga pada target bisnis perusahaan tidak terpenuhi karena volume transaksi tidak maksimal. Penelitian ini bertujuan untuk merancang suatu metodologi terhadap proses pengembangan perangkat lunak dan membuat panduan untuk implementasinya di suatu perusahaan berdasarkan prinsip-prinsip dari Essence Framework. Pelaksanaan penelitian ini menggunakan pendekatan Design Science Research (DSR). Penerapan Essence Framework pada penelitian ini dilakukan dengan menetapkan metode, memilih praktik-praktik dan pelaksanaan ujicoba demonstrasi. Pada proses pembangunan metode dengan Kernel, dilakukan penggabungan praktik lintas metode terhadap 24 praktik terpilih yang dihasilkan dari proses Focus Group Discussion (FGD) dengan tim pengembangan PT XYZ berdasarkan metode terpilih dari hasil studi literatur. Metode Agile untuk transformasi yang besar dan kompleks berdasarkan studi literatur adalah Scrum, Kanban, Extreme Programming dan Spotify. Metode Scaled Agile Framework (SAFe) dan Large Scale Scrum (LeSS) juga dimasukkan dalam metode terpilih karena SAFe dan LeSS merupakan metode scaling Agile paling populer berdasarkan hasil survei VersionOne tahun 2021. Penyesuaian metodologi berdasarkan hasil evaluasi dan juga dilakukan konfirmasi kepada para ahli adalah dengan menambahkan 5 praktik dan 2 metode baru selain dari 24 praktik yang telah dilakukan ujicoba demonstrasi. ......The wider use of digital technology supports companies to create a new business strategy, namely to develop a software-based digital ecosystem by exploiting the relationship between the form and function of products within the company. Banking companies are required to apply development with an agile methodology in order to compete quickly, increase customer satisfaction, expand market segments, increase productivity and understand customer needs. However, in reality the application of the agile methodology itself can be a challenge because the practices that must be complied with and carried out require procedures that can result in function or feature deliverables not in accordance with the development plan. This also resulted in the company's business targets not being met because the transaction volume was not optimal. This study aims to design a methodology for the software development process and create guidelines for its implementation in a company based on the principles of the Essence Framework. The implementation of this research uses the Design Science Research (DSR) approach. The application of the Essence Framework in this study was carried out by establishing methods, choosing practices and carrying out demonstration trials. In the method development process with the Kernel, a combination of cross-method practices was carried out on 24 selected practices resulting from the Focus Group Discussion (FGD) process with the PT XYZ development team based on the selected methods from the results of the literature study. Agile methods for large and complex transformations based on literature studies are Scrum, Kanban, Extreme Programming and Spotify. The Scaled Agile Framework (SAFe) and Large Scale Scrum (LeSS) methods are also included in the selected methods because SAFe and LeSS are the most popular scaling Agile methods based on the results of the 2021 VersionOne survey. Methodological adjustments are based on evaluation results and also confirmed by experts by adding 5 practices and 2 new methods apart from the 24 practices that have been piloted demonstrations.

Abstrak :
This book contains the refereed proceedings of the 13th International Conference on Agile Software Development, XP 2012, held in Malmö, Sweden, in May 2012. The topics covered include general aspects of agility, agile teams, studies related to the release and maintenance of software, and research on specific practices in agile and lean software development. They are complemented by four short papers capturing additional aspects of agile and lean projects.

Abstrak :
ABSTRAK Agile adalah sebuah metode pengembangan software yang fleksibel dalam menangani perubahan kebutuhan software. Begitupula scrum sebagai salah satu framework yang populer dari agile juga fleksibel terhadap perubahan kebutuhan software. Namun kelebihan ini ternyata harus diiringi dengan beberapa kekurangan terutama pada bagian dokumentasi software dikarenakan agile lebih mengandalkan komunikasi langsung. Knowledge management pada scrum juga turut dipengaruhi dengan meningkatnya tantangan dalam pengembangan software seperti letak tim pengembang yang berjauhan tempat, atau adanya pergantian pengembang software, penggunaan metode untuk proyek bersakala besar, adanya kebutuhan software dengan kualitas tinggi. Permasalahan ini perlu diselesaikan untuk menghidari banyaknya knowledge loss. Knowledge merupakan salah satu unsur vital dalam meningkatkan kinerja dari suatu organisasi. Sehingga jika knowledge antara anggota tim tidak tertangani dengan baik akan menghambat kecepatan pengembangan dan kinerja tim. Beberapa pendekatan telah dilakukan untuk menangani permasalahan knowledge tersebut salah satunya dengan menggunakan knowledge management system. Oleh karena itu peneliti ingin mengetahui lebih jauh bagaimana pengaruh knowledge management system pada pengembangan software berbasis scrum dan pengaruhnya terhadap kinerja pengembang. Penelitian ini menggunakan pendekatan quasi-experimental dengan penerapan di dunia nyata pada perusahaan startup. Penelitian yang dilakukan adalah penelitian dengan metode pra-uji dan pasca-uji dengan membandingkan kondisi sebelum dan sesudah penerapan knowledge management system. Percobaan ini dilakukan dengan dua minggu menggunakan sistem pendukung scrum standar dan dua minggu dengan knowledge management system. Hasil temuan yang diperoleh dari percobaan tersebut yaitu terjadi peningkatan performa kontesktual sebesar 12%, performa tugas sebesar 5%, performa adaptasi sebesar 8%, serta perbaikan sirkulasi knowledge dari tim pengembang. Knowledge Management System terbukti mampu meningkatkan dan menangani sirkulasi knowledge pada scrum dan memberikan dampak pada pengembang dan proses pengembangan software.

---

ABSTRACT Agile is a software development method that easily adapts to changing software requirements. Scrum as one of the popular frameworks of agile is also flexible to changing software requirements. But this advantage turns out to be accompanied by several shortcomings, especially in the software documentation section because agile relies more on direct communication. Knowledge management in Scrum was also influenced by the increasing challenges in software development such as the location of the development team that was far apart, or the change of software developers, the use of methods for large-scale projects, the need for high quality software. This problem needs to be resolved to avoid the amount of knowledge loss. Knowledge is one of the vital elements in improving the performance of an organization. So if knowledge between team members is not handled properly it will slow down the development and team performance. Several approaches have been made to deal with the knowledge problems, one of them is by using the knowledge management system. Therefore this research want to find out more about how the knowledge management system influences the development of scrum-based software and its effect on developer performance. This study uses a quasi-experimental approach with the application in the real world with startup companies. The research conducted is research with pre-test and post-test methods by comparing the conditions before and after the implementation of the knowledge management system. This experiment was conducted in two weeks using a standard scrum support system and two weeks with a knowledge management system. The findings obtained from the experiment were 12% increase in contest performance, task performance of 5%, adaptation performance of 8%, and improvement of knowledge circulation from the development team. The Knowledge Management System is proven to be able to improve and handle the knowledge circulation in Scrum and have an impact on developers and the software development process.

 

Abstrak :
[The approach described in this book focuses on the notion of a service as a piece of functionality that offers value to its customers. Instead of solely looking at agility in the context of system or software development, agility is approached in a broader context. The authors illustrate three kinds of agility that can be found in an agile enterprise: business, process and system agility. These three types of agility reinforce each other and establish the foundation for the agile enterprise. Architecture, patterns, models, and all of the best practices in system development contribute to agile service development and building agile applications. This book addresses two audiences. On the one hand, it aims at agile and architecture practitioners who are looking for more agile ways of working in designing and building business services or who are interested in extending and improving their agile methods by using models and model-based architectures. On the other hand, it addresses students of (enterprise) architecture and software development or service science courses, both in computer science and in business administration., The approach described in this book focuses on the notion of a service as a piece of functionality that offers value to its customers. Instead of solely looking at agility in the context of system or software development, agility is approached in a broader context. The authors illustrate three kinds of agility that can be found in an agile enterprise: business, process and system agility. These three types of agility reinforce each other and establish the foundation for the agile enterprise. Architecture, patterns, models, and all of the best practices in system development contribute to agile service development and building agile applications. This book addresses two audiences. On the one hand, it aims at agile and architecture practitioners who are looking for more agile ways of working in designing and building business services or who are interested in extending and improving their agile methods by using models and model-based architectures. On the other hand, it addresses students of (enterprise) architecture and software development or service science courses, both in computer science and in business administration.]

Abstrak :
Angel Medinilla will provide you with a comprehensive understanding of what Agile means to an organization and the manager’s role in such an environment, i.e., how to manage, lead and motivate self-organizing teams and how to create an Agile corporate culture. Based on his background as a “veteran” Agile consultant for companies of all sizes, he delivers insights and experiences, points out possible pitfalls, presents practical approaches and possible scenarios, also including detailed suggestions for further reading.

Abstrak :
Agile software development approaches have had significant impact on industrial software development practices. Today, agile software development has penetrated to most IT companies across the globe, with an intention to increase quality, productivity, and profitability. Comprehensive knowledge is needed to understand the architectural challenges involved in adopting and using agile approaches and industrial practices to deal with the development of large, architecturally challenging systems in an agile way. Agile software architecture focuses on gaps in the requirements of applying architecture-centric approaches and principles of agile software development and demystifies the agile architecture paradox. Readers will learn how agile and architectural cultures can co-exist and support each other according to the context. Moreover, this book will also provide useful leads for future research in architecture and agile to bridge such gaps by developing appropriate approaches that incorporate architecturally sound practices in agile methods.

Abstrak :
Agile project management adalah salah satu metode yang digunakan oleh perusahaan untuk dapat mengatur proyek software development. Metode ini memiliki proses untuk dapat beradaptasi secara cepat dan tanggap dalam memenuhi ekspektasi dari customers. Namun, dalam implementasi metode agile memiki tantangan tersendiri di setiap proyek software development. Hal ini menjadi penting untuk dapat mengidentifikasi tantangan agile yang terjadi pada proyek software development untuk dapat menjaga kesuksesan proyek. Penelitian ini bertujuan untuk (1) mengidentifikasi tantangan dari agile software development (2) mengidentifikasi tantangan yang paling sering dan dominan mempengaruhi penerapan (3) mengidentifikasi hubungan tantangan dengan kesuksesan proyek. Sembilan belas tantangan dan pemetaan kedalam lima kategori teridentifikasi melalui systematic literature review dan metode Delphi. Hasil survei yang dilakukan kepada praktisi Agile di Indonesia mengidentifikasi tantangan yang paling sering terjadi pada penerapan Agile adalah kultur organisasi sedangkan tantangan yang memiliki dampak paling besar adalah penolakan untuk berubah melalui Henry Garrett’s ranking dan z-score ranking. Hasil dari metode PLS-SEM menunjukan tantangan terkait human resources management, coordination, dan technology mempunyai hubungan positif dan signifikan dengan kesuksesan proyek. Penelitian ini dapat berfungsi untuk mengantisipasi tantangan yang terjadi pada penerapan Agile sehingga dapat mencapai kesuksesan proyek. ......Agile project management is one of the methodologies used by organizations to manage software development projects. The method allows processes to adapt quickly and respond to customer expectations. Nevertheless, agile method utilization has its challenges in software development projects. It is crucial to identify the relevant challenges of agile software development to attain project success. This study aims to (1) identify agile software development (2) identify most common challenges and most impact challenges (3) identify impact of challenges related to project success. Nineteen challenges and map the challenges into five categories are identified using the systematic literature review and Delphi method. The result of survey was conducted on Agile practitioners in Indonesia showed the most common challenge in implementing Agile is organizational culture, meanwhile the challenge that has the greatest impact is resistance to change using Henry Garret’s ranking and z-score ranking. The results of PLS-SEM method show that the challenges related to human resources management, coordination, and technology have a positive and significant impact on project success. This study can serve to anticipate the challenges that occur in agile implementation to lead into project success.

Abstrak :
Bank XYZ mengembangkan Mobile Apps ABC, sebuah aplikasi Super Apps, yang digunakan untuk mendukung kebutuhan nasabah dan pencapaian target bisnis. Metode Scrum yang digunakan dalam pengembangan ABC belum optimal. Dari data terlihat bahwa belum tercapainya target bisnis dan IT Bank XYZ, salah satunya karena terdapat keterlambatan implementasi fitur penting produk ABC. Penelitian mixed method ini melakukan evaluasi proses yang berjalan dengan menggunakan Capability Maturity Model Integration (CMMI V2.0). Mengacu pada Common Business Problem dalam dokumen Adoption and Transition Guidance terpilih 8 practice area dengan total 73 praktik. Berdasarkan Standard CMMI Appraisal Method for Process Improvement (SCAMPI) dihasilkan capability level untuk practice area sebagai berikut: IRP, PLAN, GOV, II di level 3; RDM, EST, MC di level 2; serta RSK di level 1. Dari 73 praktik, 59 praktik telah tercapai berdasarkan CMMI V2.0 atau sekitar 80% dari ruang lingkup practice area pada penelitian ini. Rekomendasi disusun dengan analisis weakness dari SCAMPI dan Underlying Causes dari CMMI V2.0 didapatkan 11 rekomendasi perbaikan yang telah divalidasi oleh perwakilan bank studi kasus. Saran untuk penelitian berikutnya dilakukan tahap Deploy Improvement, dan Assess Capability sesuai Adoption and Transition Guidance Circle CMMI V2.0, untuk mengukur kembali impact rekomendasi yang telah diberikan. ......XYZ Bank developed Mobile Apps ABC, a Super Apps application, which is used to support customer needs and business target. The Scrum method used in ABC development is not optimal. From the data it can be seen that Bank XYZ's business and IT targets have not been achieved, partly due to delays in the implementation of important ABC features. This mixed method research evaluates the running process using Capability Maturity Model Integration (CMMI V2.0). Referring to Common Business Problems in the Adoption and Transition Guidance document selected 8 practice areas with a total of 73 practices. Based on the Standard CMMI Appraisal Method for Process Improvement (SCAMPI), the ability levels for practice areas are: IRP, PLAN, GOV, II at level 3; RDM, EST, MC at level 2; and RSK at level 1. Of the 73 practices, 59 practices have been achieved based on CMMI V2.0 or around 80% of the scope practice areas in this study. Recommendations were compiled using weakness analysis from SCAMPI and Underlying Causes from CMMI V2.0 found 11 recommendations for improvement that have been validated by bank representative case studies. Suggestions for further research are to carry out the deployment improvement stage, and assessment capability according to the Adoption and Transition Guidance Circle CMMI V2.0, to remeasure the impact of the recommendations that have been given.

Abstrak :
Agile oracle application express shows how skilled, motivated, and self-organizing developers can realize extraordinary commercial benefits from oracle application express. The secret is to couple application express with an agile software development approach. Application express supports a gamut of enabling technologies such as SQL, HTML, CSS, JavaScript, and more that enable you to deliver any type of web application to meet your development needs. Agile Oracle Application Express helps you take the feature set of Application Express and marry it with the processes of agile development to iteratively design, create, and deliver quality applications on time and within budget.

Abstrak :
Terdapat kebijakan baru untuk program studi sarjana Fakultas Ilmu Komputer Universitas Indonesia, yaitu pelaksanaan tugas akhir menjadi wajib dilakukan untuk angkatan 2018 ke atas dan dapat dilakukan secara mandiri atau berkelompok dengan jumlah anggota maksimum 3 orang. Kebijakan tersebut menjadi alasan utama dibutuhkannya proses pengembangan lebih lanjut Sistem Informasi Sidang Tugas Akhir Fakultas Ilmu Komputer Universitas Indonesia (SI Sidang) agar dapat menangani tugas akhir kelompok. Requirements gathering dilakukan dengan melakukan Joint Application Development (JAD) meetings dengan pengguna dan product owner. Metode agile software development dan JAD digunakan untuk mengembangkan aplikasi SI Sidang. Setelah aplikasi dikembangkan, evaluasi dilakukan untuk menilai kualitas aplikasi yang dikembangkan. Proses evaluasi dilakukan dengan metode User Acceptance Test (UAT).  Berdasarkan evaluasi yang telah dilakukan, sistem berhasil memberikan hasil yang sesuai dengan ekspektasi yang telah ditentukan. ......There is a new policy for undergraduate programs at the Faculty of Computer Science, University of Indonesia. Thesis is mandatory for class of 2018 and above. It can be done individually or in groups with a maximum number of 3 members. This change of policy is the main reason for further development of Information System for Final Project of the Faculty of Computer Science, University of Indonesia (SI Sidang) in order to be able to handle group theses. Joint Application Development (JAD) meetings were conducted in order to gather requirements from users. JAD and Agile Software Development were used to develop SI Sidang. After the development of SI Sidang, an evaluation is carried out to assess the quality of the developed application. The evaluation process was carried out by using the User Acceptance Test (UAT) method. Based on the evaluation, the system has succeeded in providing results in accordance with predetermined expectations.