Claim Missing Document
Check
Articles

Found 2 Documents
Search
Journal : bit-Tech

Stock Control-Based Personal Protective Equipment Inventory System for Work Safety Santika, Komang Yuli; Putri, Putu Chrisdayanti Suada; Sridyantari, Luh Verra; Anggara, Komang Drei Bayu; Permana, Putu Adi Guna; Mahajaya, Nyoman Sarasuartha
bit-Tech Vol. 8 No. 3 (2026): bit-Tech
Publisher : Komunitas Dosen Indonesia

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.32877/bt.v8i3.3842

Abstract

Effective management of Personal Protective Equipment (PPE) is crucial for ensuring worker safety in hazardous environments. However, manual PPE management often leads to issues, such as discrepancies between recorded stock and actual quantities and challenges in tracking tool distribution. As a result, there is a need for an inventory system that can effectively monitor and control PPE stock levels. This research aims to design a web-based inventory system capable of managing PPE with integrated stock control using the Economic Order Quantity (EOQ), Safety Stock, and Reorder Point (ROP) methods. The methodology used in this study is a Research and Development (R&D) approach with a prototyping model. The research includes the design of data structures and system process flows, as well as the implementation of key features, including a dashboard, inventory management, and PPE distribution. The data used consists of employee data, supplier information, PPE types, and existing stock, all of which are analyzed to support the stock control system. The results show that the developed system can record and monitor PPE stock levels more systematically than manual methods. Additionally, the system allows for accurate monitoring of PPE distribution to employees. In conclusion, the web-based PPE inventory system can significantly improve stock management efficiency and support workplace safety by ensuring the timely availability of appropriate PPE. Future research is recommended to test the system with real operational data and assess its impact on managing occupational safety risks.
Analysis of Scrum Project Management Maturity in Software Development Anggara, Komang Dreibayu; Permana, Putu Adiguna; Santika, Komang Yuli; Pradhana, Adhi Agam
bit-Tech Vol. 8 No. 3 (2026): bit-Tech
Publisher : Komunitas Dosen Indonesia

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.32877/bt.v8i3.3853

Abstract

The increasing need for adaptive and responsive software development has encouraged organizations to adopt Scrum as an Agile project management framework. However, the formal use of Scrum does not always indicate that its practices have been implemented consistently or maturely across projects. Software House XYZ has implemented Scrum since 2017, but no formal maturity assessment had previously been conducted. This study aims to analyze the maturity level of Scrum project management in software development projects and identify Key Process Areas that require improvement. A quantitative descriptive approach was employed using the Scrum Maturity Model and Agile Maturity Model. The study assessed three Scrum-based projects, namely Project A, Project B, and Project C. Scrum Masters were selected through purposive sampling as respondents. Data were collected using a validated 66-item questionnaire with four response options: Yes, Partially, No, and Not Applicable. The achievement level of each Key Process Area was calculated using the Agile Maturity Model scoring formula. The findings show that Basic Scrum Management, Software Requirements Engineering, Iteration Management, and Performance Management were categorized as Fully Achieved. Customer Relationship Management was categorized as Largely Achieved, while Standardized Project Management was categorized as Partially Achieved. Overall, Software House XYZ's Scrum project management maturity was Level 3: Defined. This study contributes empirical evidence by conducting a project-level Scrum maturity assessment in a real software development organization, demonstrating how long-term Scrum adoption can still reveal inconsistencies in project standardization, Product Owner involvement, backlog management, and metric-based decision-making.