Hasil Pencarian  ::  Simpan CSV :: Kembali

"Agile project management adalah salah satu metode yang digunakan olehperusahaan untuk dapat mengatur proyek software development. Metode inimemiliki proses untuk dapat beradaptasi secara cepat dan tanggap dalam memenuhiekspektasi dari customers. Namun, dalam implementasi metode agile memikitantangan tersendiri di setiap proyek software development. Hal ini menjadi pentinguntuk dapat mengidentifikasi tantangan agile yang terjadi pada proyek softwaredevelopment untuk dapat menjaga kesuksesan proyek. Penelitian ini bertujuanuntuk (1) mengidentifikasi tantangan dari agile software development (2)mengidentifikasi tantangan yang paling sering dan dominan mempengaruhipenerapan (3) mengidentifikasi hubungan tantangan dengan kesuksesan proyek.Sembilan belas tantangan dan pemetaan kedalam lima kategori teridentifikasimelalui systematic literature review dan metode Delphi. Hasil survei yangdilakukan kepada praktisi Agile di Indonesia mengidentifikasi tantangan yangpaling sering terjadi pada penerapan Agile adalah kultur organisasi sedangkantantangan yang memiliki dampak paling besar adalah penolakan untuk berubahmelalui Henry Garrett’s ranking dan z-score ranking. Hasil dari metode PLS-SEMmenunjukan tantangan terkait human resources management, coordination, dantechnology mempunyai hubungan positif dan signifikan dengan kesuksesan proyek.Penelitian ini dapat berfungsi untuk mengantisipasi tantangan yang terjadi padapenerapan 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."

"This book constitutes the refereed proceedings of the 13 International Conference on Product-Focused Software Process Improvement, PROFES 2012, held in Madrid, Spain, in June 2012. The 21 revised full papers presented together with 3 short papers and 4 workshop and tutorial papers were carefully reviewed and selected from 49 submissions. The papers are organized in topical sections on process focused software process improvement, open-source agile and lean practices, product and process measurements and estimation, distributed and global software development, quality assessment, and empirical studies."

"ABSTRAKKelangsungan bisnis PT XYZ sangat tergantung pada SI/TI yang dimanfaatkannya. Namun PT XYZ tidak memiliki proses pemeliharaan perangkat lunak yang terdefinisi. Tidak tercapainya target pemeliharaan perangkat lunak berpotensi menghambat pemanfaatan SI/TI, yang dapat merambat pada terhambatnya proses bisnis yang menggunakan SI/TI tersebut.Untuk mengatasi masalah manajemen pada pemeliharaan perangkat lunak, perlu diketahui tingkat kematangan proses pemeliharaan terlebih dahulu, agar dapat menyusun strategi SPI. Penelitian ini mengukur tingkat kematangan berdasarkan S3m menggunakan S3mAssess. Strategi SPI akan disusun menggunakan tingkat kematangan yang lebih tinggi dari saat ini.Penelitian ini menghasilkan strategi SPI yang dapat digunakan sebagai saran perbaikan bagi PT XYZ untuk meningkatkan kematangan proses pemeliharaan perangkat lunaknya. Peningkatan kematangan proses tersebut diharapkan dapat membantu dalam pencapaian visi dan misinya.

---

ABSTRACTBusiness continuity of PT XYZ depends on the usage of IS IT. However, PT XYZ does not have defined processes for its software maintenance. Unachieved maintenance target has potential to hamper the utilization of IS IT, thus could obstruct the business processes that depends on the IS IT as well.To solve the management problem of the software maintenance process, the maturity level of current process need to be figured out first, so the SPI strategy can be established. This research appraises maturity level based on S3m using S3mAssess. The SPI strategy will be established using higher maturity level than the current maturity level.This research establishes the SPI strategy that will be used to as a suggestion for improvement for PT XYZ to increase its maturity level of its software maintenance process. The increase in maturity level is expected to help it in achieving its vision and mission."

"Münch and his co-authors aim at providing knowledge that enables readers to develop useful process models that are suitable for their own purposes. They start with the basic concepts. Subsequently, existing representative process models are introduced, followed by a description of how to create individual models and the necessary means for doing so (i.e., notations and tools). Lastly, different possible usage scenarios for process management are highlighted (e.g. process improvement and software process simulation)."

"PT XYZ merupakan perusahaan rintisan yang menjual produk-produk alami melalui situs web dan aplikasi mobile mereka. Proyek perangkat lunak di PT XYZ diimplementasikan menggunakan metode agile dan kerangka kerja Scrum agar tanggap dengan kebutuhan pasar dan pelanggan. Nyatanya, proses pengembangan perangkat lunak masih mengalami keterlambatan dalam perilisan karena rendahnya tingkat ketercapaian target untuk sprint. Dampak yang ditimbulkan adalah tidak tercapainya Objective and Key Result (OKR). Berdasarkan wawancara dengan narasumber dari PT XYZ, yaitu anggota tim Scrum yang terdiri dari Product Manager, Technical Lead, Senior Software Engineer, dan QA Analyst menunjukkan bahwa akar permasalahaan yang dihadapi perusahaan erat kaitannya dengan proses implementasi Scrum, terutama acara dan artefak Scrum. Permasalahan tersebut menjadi pemicu penelitian ini untuk melakukan evaluasi terhadap implementasi Scrum di perusahaan. Evaluasi implementasi Scrum dilakukan dengan menggunakan kerangka kerja Scrum Maturity Model (SMM) dan metode penilaian Standard Capability Maturity Model Integration Appraisal Method for Process Improvement (SCAMPI) kelas C. Hasil penilaian menunjukkan bahwa implementasi Scrum di PT XYZ masih berada pada tingkat kematangan 1 karena terdapat sebuah goal di tingkat kematangan 2 belum fully achieved, yaitu goal basic Scrum management dengan nilai 71,43% largely achieved. Setelah melakukan penilaian, penelitian ini menghasilkan 3 rekomendasi untuk artefak Scrum, 4 rekomendasi untuk acara Scrum, 2 rekomendasi untuk komponen pendukung Scrum, dan 5 rekomendasi untuk akar permasalahan penelitian. Penelitian ini juga menyertakan langkah-langkah perubahan yang dapat dilaksanakan perusahaan untuk memperbaiki alur proses Scrum terkait acara dan artefak Scrum. Rekomendasi dan langkah-langkah perubahan diharapkan mampu untuk meningkatkan ketercapaian target sprint sehingga memungkinkan perilisan proyek perangkat lunak yang tepat waktu dan mencapai nilai bisnis yang diharapkan perusahaan

---

PT XYZ is a start-up company that sells natural products through its website and mobile application. The software project at PT XYZ is implemented using agile methods and the Scrum framework to respond to the market and customer needs. In fact, the software development process is still experiencing delays in release due to the low rate of achieving targets for sprints. The impact is not achieving the Objective and Key Result (OKR). Based on interviews with representatives from PT XYZ, namely members of the Scrum team consisting of Product Manager, Technical Lead, Senior Software Engineer, and QA Analyst, it shows that the root problems faced by the company are closely related to the Scrum implementation process, especially Scrum events and artifacts. These problems are the trigger for this research to evaluate the implementation of Scrum in the company. Evaluation of Scrum implementation is carried out using the Scrum Maturity Model (SMM) framework and the Standard Capability Maturity Model Integration Appraisal Method for Process Improvement (SCAMPI) Class C assessment method. The results of the assessment show that the implementation of Scrum at PT XYZ is still at maturity level 1 because there is a goal at maturity level 2 that has not been fully achieved, namely the basic Scrum management goal with a value of 71.43% (largely achieved). After conducting the assessment, this research resulted in 3 recommendations for Scrum artifacts, 4 recommendations for Scrum events, 2 recommendations for Scrum supporting components, and 5 recommendations for the root causes of the research. This research also includes change steps that companies can implement to improve the Scrum process flow regarding Scrum events and artifacts. Recommendations and change steps are expected to be able to improve the achievement of the sprint targets to enable the timely release of software projects and achieve the expected business value of the company."

"Sebuah metode untuk mengukur kualitas desain berdasarkan hasil implementasinya dalam Java source codes diusulkan dalam penelitian ini. Metode yang diusulkan menggabungkan Metrics for Object-Oriented Software Engineering (MOOSE), properti kualitas desain software dan konsep Analytic Hierarchy Process (AHP). Sebagai studi kasus, metode ini diterapkan pada sejumlah aplikasi ERP yang bersifat open source yaitu Adempiere, OpenBravo, Plazma, FreedomERP, dan JAllInOne. Pengukuran MOOSE dilakukan dengan bantuan tool CKJM 1.8. Hasil ukur MOOSE dikelompokkan dalam properti kualitas yaitu efficiency, understandability, reusability, testability dan maintainability. Kombinasi MOOSE dan AHP yang dihasilkan dapat menjadi alat bantu dalam menentukan peringkat kualitas software dari aspek orientasi objek.

---

A method for measuring the quality of the design is based on the results of its implementation in the Java source codes proposed in this study. The proposed method combines Metrics for Object-Oriented Software Engineering (MOOSE), property and the concept of software design quality Analytic Hierarchy Process (AHP). As a case study, this method is applied to a number of applications that are open source ERP is Adempiere, Openbravo, Plazma, FreedomERP, and JAllInOne. MOOSE measurements done with the aid tool CKJM 1.8. MOOSE measuring results are grouped in quality properties that are efficiency, understandability, reusability, testability and maintainability. MOOSE and AHP combination that have been produced can be a useful tool in determining the quality ratings of aspects of object oriented software."

"PT Kliring Penjaminan Efek Indonesia (KPEI) merupakan lembaga kliring dan penjaminan di pasar modal Indonesia. Dalam mencapai visi dan misinya diperlukan layanan sistem berkualitas yang ditandai dengan tercapainya zero defect sistem di lingkungan produksi. Kenyataannya, gangguan terhadap sistem bisnis utama telah menjadi top risk organisasi karena terjadi 36 kali dalam setahun terakhir ini yang berdampak terhadap finansial dan reputasi organisasi. Berdasarkan hal tersebut, diketahui bahwa permasalahan utama yang dihadapi organisasi adalah kurangnya proses pengujian. Untuk mengatasi hal ini, dilakukan penilaian tingkat kematangan dan memberikan rekomendasi perbaikan proses pengujian. Penilaian tingkat kematangan proses pengujian perangkat lunak dilakukan menggunakan Test Maturity Model Integration (TMMi) pada tingkat kematangan 2 (managed) dan mengacu pada ketentuan TMMi Assessment Method Accreditation Requirements (TAMAR). Praktik yang belum dipenuhi akan menjadi rekomendasi perbaikan proses menggunakan metode deming cycle (PDCA). Berdasarkan hasil penilaian diperoleh bahwa PT KPEI masih berada pada tingkat kematangan 1 (initial). Area proses yang memperoleh nilai terendah adalah test planning (PA 2.2) dengan nilai partially achieved. Rekomendasi perbaikan yang perlu dilakukan yaitu penyusunan test plan secara konsisten dan ditinjau secara berkala serta perbaikan isi dokumen test plan. Rekomendasi perbaikan proses pengujian ini diharapkan dapat mengurangi kemunculan bugs sistem di lingkungan produksi.

---

PT Kliring Penjaminan Efek Indonesia (KPEI) is a clearing and guarantee institution in the Indonesian capital market. In achieving its vision and mission, a quality system service is needed, which is marked by the achievement of zero-defect systems in the production environment. In fact, disruption to key business systems has become an organization's top risk because it has occurred 36 times in the past year, which has an impact on the organization's finances and reputation. Based on this, it is known that the main problem faced by the organization is the lack of a testing process. To overcome this, an assessment of the maturity level is carried out and provides recommendations for improvement of the testing process. The assessment of the maturity level of the software testing process is carried out using the Test Maturity Model Integration (TMMi) at maturity level 2 (managed) and refers to the provisions of the TMMi Assessment Method Accreditation Requirements (TAMAR). Practices that have not been met will be included as recommendations for process improvement using the Deming Cycle (PDCA) method. Based on the results of the assessment, it was found that PT KPEI is still at maturity level 1 (initial). The process area that obtained the lowest score was test planning (PA 2.2) with a partially achieved value. Recommendations for improvements that need to be made are the preparation of a test plan consistently and reviewed periodically as well as improvements to the contents of the test plan document. Recommendations for improving the testing process are expected to reduce the appearance of system bugs in the production environment."

"Tidak ada di dunia ini yang tidak berubah kecuali perubahan itu sendiri. Hampir setiap aspek dunia, khususnya dunia IT, dapat berubah. Dalam perangkat lunak manajemen proyek, misalnya, orang harus bekerja pada perangkat lunak yang sering mengalami perubahan. Itu sebabnya tantangan terbesar yang dihadapi perusahaan dalam dunia yang kompetitif saat ini adalah bagaimana menghadapi perubahan tersebut. Sehubungan dengan penjelasan sebelumnya, tujuan dari penelitian ini adalah untuk standarisasi manajemen proyek dalam pengembangan perangkat lunak dengan menggunakan manajemen perubahan. Tujuan akhirnya akan membantu pengembang proyek untuk memastikan bahwa manajemen proyek memiliki kebutuhan standarisasi yang penting untuk mencerminkan kebutuhan bisnis saat ini. Untuk mencapai tujuan tersebut, penelitian ini juga akan mencoba menunjukkan mengapa standarisasi menggunakan manajemen perubahan adalah tugas penting yang tidak dapat dihindari. Penelitian ini diarahkan untuk membahas tentang manajemen perubahan sebagai cara umum untuk mengurangi risiko, biaya dan memaksimalkan manfaat dari perubahan besar dalam bisnis teknologi dan informasi. Hasil penelitian menunjukkan bahwa proyek tersebut dapat dinyatakan sukses karena disampaikan tepat waktu, sesuai budget dan memiliki kualitas standar.

---

AbstractThere is nothing in this world that do not change unless the change itself. Almost every aspect of the world, particularly the world of IT, can changed. In project management software, for instance, people have to work on software that frequently subject to change. That is why the greatest challenge faced by the company within today's competitive world is how to deal with those changes. In relation with the previous explanation, the objective of this research is to standardize project management in software development by using change management. Objective will finally help project developer to ensure that the management of project has a need of standardization that essential for reflecting the current business needs. To achieve the objectives, this research will also attempt to show why does the standardization using the change management is essential task, which is almost inevitable. This research directed for discussing about the management of change as a common way to reduce risks, costs and maximizing the benefit from major changes in business and information technology. The result showed that the project can determined as success because it delivered on time, on budged and have a standardized quality"