PENERAPAN TOOLS MANAJEMEN PROYEK PADA PT. KRAKATAU IT CILEGON
Abstract
PT. Krakatau IT adalah suatu perusahaan yang bergerak di bidang jasa mempunyai visi menjadi penyedia Solusi ICT yang terpercaya di Indonesia. Untuk meningkatkan kinerja pelanggan dengan cara memberikan kepuasan mengenai proyek-proyek dimiliki oleh perusahaan maka diperlukan perencanaan dan eksekusi proyek yang berkualitas. Kualitas proyek dapat dilihat dengan tercapainya penyelesaian proyek sesuai dengan anggaran dan tepat waktu. Saat ini PT. Krakatau IT masih sering mengalami keterlambatan penyelesaian proyek sehingga menimbulkan kerugian, untuk itu peneliti menerapkan tools project management di krakatau IT dalam penyelesaian proyek-proyeknya. Tools Manajemen Proyek yang diusulkan penulis dinamakan dengan krakatau pro dilengkapi dengan fitur-fitur mengenai informasi antara rencana dan realisasi penyelesaian pekerjaan sehingga dapat membantu proyek lebih efesien dalam pengelolaan dan pengawasan dalam proyek.References
Abdul Muhyi, F. A. (2022). Pengendalian Biaya Dan Waktu Proyek Dengan Menggunakan Metode Earned Value. Bisnis, Sosial dan Teknologi, Volume 12 No 1, 64-72.
Afifa Witania, A. D. (2022). Analisis Perbandingan Metode Manajemen Proyek TI Yang Paling Sering Digunakan Di Indonesia Dan Luar Negeri: A Literature Review. Journal Of Management Small and Medium Entreprises (SME’s),Vol 15, No. 2, 299-316.
Afrisco Ardytia Febrian Amarta1, I. G. (2021). Implementasi Agile Scrum Dengan Menggunakan Trello Sebagai Manajemen Proyek Di PT Andromedia. Jurnal Nasional Komputasi dan Teknologi Informasi Vol. 4 No. 6 , 528 - 534.
Ajar Rohmanu M.Kom, A. E. (2022). Penerapan Agile Project Management Pada Pembuatan Sistem E-Warga Taman Cibodas Lippo Cikarang. Jurnal Nuansa Informatika Volume 16 Nomor 1, 1-9.
Duncan, W. R. (1996). A Guide to The Project Management Body of Knowledge. Sylva: PMI Communication.
Ervianto, W. I. (2003). Manajemen Proyek Kontruksi. Yogyakarta: Penerbit ANDI.
ExamsPM.com. (2022). PMI, PMBOK, PMP, PgMP, PfMP, CAPM, PMI-SP, PMI-RMP, PMI-ACP, and PMI-PBA are registered marks of the Project Management Institute, Inc. Retrieved from examspm: https://www.examspm.com/pmbok-6th-edition-pdf/
Fernanda Rachmadini, S. S. (2021). Peran Project Owner dalam Menjalankan Agile Project Management (Studi Kasus: PT. XYZ). Jurnal Manajemen dan Organisasi (JMO) Vol. 12 No. 3, 166-176.
Husen, A. (2009). Manajemen Proyek. Yogya karta: Penerbit ANDI.
Iman, S. (1995). Manajemen Proyek : Dari Konseptual Sampai Operasional. Jakarta: Erlangga. Retrieved from Media Jobs: https://www.ekrut.com/media/product-backlog-adalah
Institute, P. M. (2000). A Guide to The Project Management . Newtown Square, USA. Retrieved from A Guide to The Project Management .
Institute, P. M. (2013). A Guide to the Project Management Body of Knowledge (PMBOK Guide). Pennsylvania, USA: Project Management Institute, Inc. .
Institute, P. M. (2018). Pedoman Kerangka Ilmu Manajemen Proyek (PMBOK Guide) Edisi Keenam. Jakarta: PMI Indonesia Chapter.
Kristanto, A. (2004). Rekayasa Perangkat Lunak: Konsep Dasar. Yogyakarta: Penerbit Gava Media.
Nurjaman, D. H. (2014). Manajemen Proyek. Yogyakarta: Pustaka Setia.
Project Management Institute, I. (2013). Software Extension to the PMBOK® Guide Fifth Edition. Project Management Institute, Inc. .
Soeharto, I. (2002). Studi Kelayaan Proyek Industri. Jakarta: Erlangga.
Vidianto, S. A. (2018). Sistem Informasi Manajemen Proyek Berbasis Kanban (Studi Kasus: PT.XYZ). Jurnal Teknologi Informasi dan Ilmu Komputer (JTIIK) Vol 7 No. 2, 283-292.
Copyright (c) 2023 JIKA (Jurnal Informatika)

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
License and Copyright Agreement
In submitting the manuscript to the journal, the authors certify that:
- They are authorized by their co-authors to enter into these arrangements.
- That it is not under consideration for publication elsewhere,
- That its publication has been approved by all the author(s) and by the responsible authorities – tacitly or explicitly – of the institutes where the work has been carried out.
- They secure the right to reproduce any material that has already been published or copyrighted elsewhere.
- They agree to the following license and copyright agreement.
Copyright
Authors who publish with International Journal of Advances in Intelligent Informatics agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License (CC BY-SA 4.0) that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this journal.Â
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgment of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work.
Licensing for Data Publication
International Journal of Advances in Intelligent Informatics use a variety of waivers and licenses, that are specifically designed for and appropriate for the treatment of data:
Open Data Commons Attribution License, http://www.opendatacommons.org/licenses/by/1.0/ (default)
Creative Commons CC-Zero Waiver, http://creativecommons.org/publicdomain/zero/1.0/
Open Data Commons Public Domain Dedication and Licence, http://www.opendatacommons.org/licenses/pddl/1-0/
Other data publishing licenses may be allowed as exceptions (subject to approval by the editor on a case-by-case basis) and should be justified with a written statement from the author, which will be published with the article.
Open Data and Software Publishing and Sharing
The journal strives to maximize the replicability of the research published in it. Authors are thus required to share all data, code or protocols underlying the research reported in their articles. Exceptions are permitted but have to be justified in a written public statement accompanying the article.
Datasets and software should be deposited and permanently archived inappropriate, trusted, general, or domain-specific repositories (please consult http://service.re3data.org and/or software repositories such as GitHub, GitLab, Bioinformatics.org, or equivalent). The associated persistent identifiers (e.g. DOI, or others) of the dataset(s) must be included in the data or software resources section of the article. Reference(s) to datasets and software should also be included in the reference list of the article with DOIs (where available). Where no domain-specific data repository exists, authors should deposit their datasets in a general repository such as ZENODO, Dryad, Dataverse, or others.
Small data may also be published as data files or packages supplementary to a research article, however, the authors should prefer in all cases a deposition in data repositories.