Improving the Quality of Requirements Engineering Process in Software Development with Agile Methods: a Case Study Telemedicine Startup XYZ

Abstract

XYZ is a telemedicine startup company that uses Scrum, an Agile methodology, as a software development method. The company uses Scrum to deliver good products and services to customers on time, even with limited requirements. However, the company faced problems in product development, so the company could not release the product on time. Based on interviews with internal experts, the company has issues determining the priority scale of requirements and change requirement management, where both problems are part of requirement engineering. This study discusses the problems of the company XYZ regarding the requirement engineering process, especially the problem of determining the priority scale of requirements and change requirement management. This research uses the CMMI-Dev 1.3 specific process area to assess the requirement engineering process in the company using sub-specific practices in the Requirement Development (RD) and Requirement Management (REQM) process areas. Researchers conducted interviews with product managers to appraise sub-specific RD and REQM practices with current activities in the company. The results of this study are recommendations to improve the quality of the requirement engineering process by using Objective Key Result (OKR) and Action Priority Matrix (APM).