Hasil Pencarian  ::  Simpan CSV :: Kembali

"Global Software Development (GSD) adalah metode pengembangan perangkat lunak dengan tim yang tersebar secara geografis di seluruh dunia. GSD merupakan fenomena yang tidak bisa dihindari, karena perkembangan teknologi dan perangkat lunak yang semakin meluas. Persentase tenaga kerja Indonesia yang terlibat dalam GSD hanya 0.2%. Berdasarkan masalah tersebut, tujuan dari penelitian ini adalah mengidentifikasi kompetensi software engineer GSD berbasis KSA (knowledge, skill, & attitude). Penelitian ini mengumpulkan daftar kompetensi KSA menggunakan teknik Systematic Literature Review (SLR), kemudian dilakukan validasi pakar melalui Focus Group Discussion menggunakan kuesioner. Kuesioner kemudian diolah menggunakan Fuzzy Delphi Method untuk mengetahui kompetensi mana saja yang disepakati para pakar. Berdasarkan hasil konsensus pakar, terdapat sepuluh kompetensi GSD yang terdiri dari empat knowledge, empat skill, dan dua attitude. Keempat kompetensi knowledge yang diterima dan diurutkan berdasarkan peringkat tertinggi, yaitu virtual team management, software distribution method, project management, dan information security. Selain itu, keempat kompetensi skill yang diterima dan diurutkan berdasarkan peringkat tertinggi, yaitu collaboration & coordination, programming skill, foreign language skill, dan intercultural communication. Kemudian kedua kompetensi attitude yang diterima, yaitu trust dan cultural sensitivity/awareness. Kompetensi yang telah mencapai konsensus, selanjutnya dicari hubungan keterkaitannya menggunakan fitur cluster analysis pada NVIVO 12 Plus. Berdasarkan analisis, relasi terkuat merupakan kompetensi skill, yaitu intercultural communication (skill) dan collaboration & coordination (skill) dengan nilai Jaccard’s coefficient 0,9. Kemudian relasi terkuat kedua merupakan kompetensi knowledge, yaitu project management (knowledge) dan foreign language skill (knowledge) dengan nilai Jaccard’s coefficient 0,714. Sedangkan kompetensi attitude berada di peringkat ketiga, yaitu relasi antara trust (attitude) dan virtual team management (knowledge) dengan nilai Jaccard’s coefficient 0,714. Langkah terakhir yaitu menyusun rekomendasi menggunakan SLR dan analisis tematik. Penelitian ini menghasilkan rekomendasi untuk meningkatkan dua kompetensi teratas dari knowledge, yaitu virtual team management dan software distribution method; kompetensi teratas dari skill, yaitu collaboration & coordination; dan kompetensi teratas dari attitude, yaitu trust. Selain itu, rekomendasi juga diberikan untuk meningkatkan dua kompetensi yang memiliki relasi tertinggi, yaitu intercultural communication dan collaboration & coordination.

---

Software Development (GSD) is a software development method with teams that are spread geographically across the world. GSD is a phenomenon that cannot be avoided, because of the development of technology and software that is increasingly widespread. The percentage of Indonesian workers involved in GSD is only 0.2%. Based on these problems, the purpose of this study is to identify the competency of GSD software engineer based on knowledge, skill, and attitude. This study compiled a list of KSA competencies using the Systematic Literature Review (SLR) technique, then expert validation was conducted through Focus Group Discussion using a questionnaire. The questionnaire is then processed using the Fuzzy Delphi Method to find out which competencies are agreed upon by the experts. Based on the expert consensus, there are ten GSD competencies consisting of four knowledges, four skills, and two attitudes. The four competencies of knowledge sorted by the highest rank, are virtual team management, software distribution methods, project management, and information security. In addition, the four competencies of skill sorted by the highest rank, are collaboration & coordination, programming skills, foreign language skills, and intercultural communication. Then the two competencies of skill sorted by the highest rank, are trust and cultural sensitivity/awareness. The ten competencies then searched for relationship using cluster analysis feature of NVIVO 12 Plus. Based on the analysis, the strongest relation is a skill competency, namely intercultural communication (skill) and collaboration & coordination (skill) with Jaccard's coefficient value of 0.9. Then the second strongest relation is knowledge competency, namely project management (knowledge) and foreign language skills (knowledge) with Jaccard's coefficient value of 0.714. While attitude competency is ranked third, namely the relationship between trust (attitude) and virtual team management (knowledge) with Jaccard’s coefficient value of 0.714. This research produces recommendations to improve the two top competencies of knowledge, namely virtual team management and software distribution method; top competency of skills, namely collaboration & coordination; and the top competency for attitude, namely trust. In addition, recommendations are also given to improve two competencies that have the highest relations, namely intercultural communication and collaboration & coordination."

""This book focuses on the inherent issues to help practitioners in gaining understanding of software development processes aimed at software professionals,students and researchers in the domain of software engineering in order to successfully employ knowledge management procedures"--Provided by publisher."

"Software House XYZ menggunakan Scrum sebagai salah satu proses pengembangan perangkat lunaknya. Namun, Software House XYZ memiliki beberapa masalah dalam penerapan Scrum sehingga menyebabkan keterlambatan pada rilis produk mereka. Terdapat 2 masalah yang menjadi fokus pada penelitian ini yaitu pengendalian tim Scrum dengan ukuran yang besar dan pengendalian komitmen pekerjaan tim. Scrum at Scale adalah kerangka kerja yang dipilih menjadi solusi kedua permasalahan tersebut. Sebelum menerapkan Scrum at Scale, perlu dilakukan penilaian tingkat kematangan Scrum yang saat ini diterapkan oleh Software House XYZ. Scrum Maturity Model yang disesuaikan dengan Scrum Guide 2020 dipilih sebagai metode yang dapat menilai seberapa baik perusahaan menerapkan Scrum. Kuesioner yang berisi 81 praktik disebar ke 40 tim pengembang. Data hasil kuesioner yang valid sebanyak 10 kuesioner. Dari hasil penilaian menggunakan Scrum Maturity Model, kematangan penerapan Scrum di Software House XYZ saat ini berada di tingkat 1 Initial. Sebanyak 61 praktik diusulkan sebagai perbaikan proses Scrum. Rekomendasi rancangan Scrum at Scale dapat diterapkan apabila perbaikan proses Scrum telah dilakukan. Rekomendasi disusun mengikuti kerangka kerja yang ada di Scrum at Scale Guide 2022. Validasi terhadap rekomendasi rancangan Scrum at Scale telah dilakukan peneliti melalui wawancara dengan perwakilan dari Software House XYZ. Dari hasil validasi, perusahaan tertarik untuk mencoba menerapkan Scrum at Scale. Namun, perusahaan setuju untuk meningkatkan proses Scrum yang ada diperusahaan terlebih dahulu sebelum menerapkan Scrum at Scale secara utuh.

---

Software House XYZ utilizes Scrum as one of its software development processes. However, the company encounters some challenges in implementing Scrum, leading to delays in their product releases. This research focuses on two identified issues: controlling a large Scrum team and managing team commitment to tasks. Scrum at Scale is chosen as the framework to address these problems. Before implementing Scrum at Scale, an assessment of the current Scrum maturity level at Software House XYZ is deemed necessary. The Scrum Maturity Model, aligned with the Scrum Guide 2020, is selected as the method to evaluate the company's Scrum implementation. A questionnaire containing 81 practices is distributed to 10 development team members. Valid data from 10 questionnaires are collected. The assessment using the Scrum Maturity Model reveals that the current Scrum maturity level at Software House XYZ is at the Initial stage. Sixty-one practices are proposed for improving the Scrum process. Recommendations for the Scrum at Scale design can be implemented once these process improvements in Scrum are carried out. The design recommendations adhere to the framework outlined in the Scrum at Scale Guide 2022. The researcher validates the Scrum at Scale design recommendations through interviews with representatives from Software House XYZ. The validation results indicate the company's interest in trying out Scrum at Scale. However, the company agrees to enhance its existing Scrum processes first before fully adopting Scrum at Scale."

"PT XYZ adalah salah satu perusahaan teknologi rintisan terkemuka di Indonesia yang bergerak di bidang e-commerce. Selain di bidang e-commerce, PT XYZ juga melakukan eksplorasi bisnis baru pada bidang teknologi finansial. Tim investasi dan asuransi (Investment and Insurance, IIS) adalah salah satu tim yang mengembangkan produk asuransi dan investasi pada PT XYZ. Dalam proses pengembangan perangkat lunak, IIS menggunakan kerangka kerja Scrum agar dapat beradaptasi dengan cepat sesuai dengan kebutuhan pasar. Dalam pelaksanaannya, ditemukan bahwa deliverable produk mengalami keterlambatan dan objective and key result (OKR) yang tidak terpenuhi. Data pendukung juga memaparkan bahwa rata-rata penyelesaian pada setiap sprint masih berada pada angka 44%. Hal ini dipengaruhi oleh beberapa akar masalah, salah satunya adalah proses acara Scrum yang belum dilakukan sesuai dengan Scrum Guides. Untuk dapat memperbaiki permasalahan ini, penelitian melakukan evaluasi tingkat kematangan pengembangan perangkat lunak dengan Scrum Maturity Model (SMM) dan Standard CMMI Appraisal Method for Process Improvement (SCAMPI) C untuk melakukan penilaian terhadap praktik Scrum. Hasil dari evaluasi ini, ditemukan bahwa IIS masih berada pada level 1 melalui penilaian SMM dengan rentang level 1 hingga 5. Terdapat satu goal yang belum fully achieved, masih terdapat satu goals basic Scrum management dengan penilaian 67,86% (largely achieved) yang menyebabkan organisasi belum dapat mencapai level 2. Selanjutnya, hasil penilaian SCAMPI C digunakan sebagai acuan untuk memilih praktik SMM yang sesuai dengan pertanyaan penelitian dan menyusun usulan rekomendasi perbaikan. Hasil akhir penelitian adalah lima belas rekomendasi terkait acara Scrum. Rekomendasi disusun dan divalidasi dengan harapan untuk dapat memperbaiki dan meningkatkan kinerja proses pengembangan perangkat lunak sehingga dapat tercapai target OKR sesuai dengan harapan perusahaan

---

PT XYZ is one of the leading technology start-ups in Indonesia engaged in e-commerce. Apart from e-commerce, PT XYZ also explores new businesses in the field of financial technology. The investment and insurance team (Investment and Insurance, IIS) is one of the teams that develops insurance and investment products at PT XYZ. In the software development process, IIS uses the Scrum framework to quickly adapt to market needs. In its implementation, it was found that the product deliverables were delayed, and the objectives and key results (OKR) were not met. Supporting data also explains that the average completion of each sprint is still at 44%. This is influenced by several root causes, one of which is the Scrum event process that has not been carried out in accordance with the Scrum Guides. To be able to fix this problem, the research evaluates the maturity level of software development using the Scrum Maturity Model (SMM) and Standard CMMI Appraisal Method for Process Improvement (SCAMPI) C to assess Scrum practices. The results of this evaluation, it was found that IIS is still at level 1 through the QMS assessment with a range of levels 1 to 5. There is one goal that has not been fully achieved, there is still one basic goal of Scrum management with an assessment of 67.86% (largely achieved) which causes the organization has not been able to reach level 2. Furthermore, the results of the SCAMPI C assessment are used as a reference for selecting QMS practices that are in accordance with the research questions and formulating recommendations for improvement. The results of the study are fifteen recommendations related to Scrum events. Recommendations are compiled and validated with the hope of being able to improve and improve the performance of the software development process so that OKR targets can be achieved in accordance with company expectations."

"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.

 

"

"Logee merupakan sub-divisi dari Divisi Digital & Business Technology (DBT) di bawah Directorat Digital Business (DDB) PT Telkom Indonesia. Logee menyediakan platform digital bagi ekosistem logistik nasional dan terhubung ke jaringan global. Dalam pengembangan perangkat lunaknya, Logee menerapkan kerangka kerja Scrum. Namun, sering mengalami masalah seperti masuknya requirement baru di tengah sprint dan kualitas produk yang rendah. Hal ini menyebabkan tidak tercapainya target backlog dan keterlambatan rilis product. Jika hal tersebut tidak diselesaikan berdampak pada penambahan cost pengembangan product, dan potensi kehilangan revenue. Penelitian ini mengevaluasi implementasi Scrum di Logee Distribution dan memberikan rekomendasi perbaikan proses pengembangan perangkat lunak. Penelitian menggunakan mixed-methods dengan pengumpulan data kuantitatif melalui kuesioner berbasis Scrum Guide 2020 dan Essentials Scrum oleh Rubin. Metode kualitatif dilakukan dengan wawancara kepada Scrum Master dan Head of Product Logee Distribution. Hasil evaluasi menunjukkan nilai KPA Rating keseluruhan sebesar 87,39%, diinterpretasikan sebagai Fully Achieved. Squad Sales dan Order menunjukkan implementasi yang baik dengan KPA Rating masing-masing 95,93% dan 91,30%, sementara squad Fulfillment hanya mencapai 75,85%. Rekomendasi perbaikan difokuskan pada 27 rekomendasi untuk 61 praktik yang belum memenuhi standar, dengan prioritas tinggi pada 15 rekomendasi. Evaluasi dan rekomendasi ini bertujuan untuk memperbaiki implementasi Scrum di Logee Distribution dan mengatasi masalah target Backlog yang tidak tercapai pada squad Fulfillment.

---

Logee is a sub-division of the Digital & Business Technology (DBT) Division under the Digital Business Directorate (DDB) at PT Telkom Indonesia. Logee provides a digital platform for the national logistics ecosystem and is connected to a global network. In the software development process, Logee chose to implement the Scrum framework. However, they often experience problems such as the entry of new requirements in the middle of a sprint and low product quality. This causes the backlog target to not be achieved and delays in product releases. If this is not resolved, it will result in additional product development costs and a potential loss of revenue. This research evaluates the implementation of Scrum in Logee Distribution and provides recommendations for improving the software development process. The research used mixed methods with quantitative data collection through questionnaires based on the 2020 Scrum Guide and Scrum Essentials by Rubin. The qualitative method was carried out by interviewing the scrum master and head of product Logee distribution. The evaluation results show an overall KPA rating value of 87.39%, interpreted as Fully Achieved. The Sales and Order squads showed good implementation, with KPA Ratings of 95.93% and 91.30%, respectively, while the Fulfillment squad only reached 75.85%. Recommendations for improvement focused on 27 recommendations for 61 practices that did not meet the standards, with high priority given to 15 recommendations. This evaluation and recommendation aim to improve the implementation of Scrum in Logee Distribution and overcome the problem of backlog targets not being achieved in the Fulfillment squad"