Feature prioritization in SAFe model using COCOMO II
Software requirements prioritization is considered as one of the significant challenges for software managers in today’s IT business. Depends on the software development model, the requirements ranking technique is different. This paper presents a case study to demonstrate the accuracy and practicality of using COCOMO II in the SAFe model to estimate the effort that is required to develop new features. The effort can be used for what SAFe recognizes as size in Weighted Shortest Job First (WSJF) model to prioritize the work for each Program Increment (PI).
In traditional project management, determining a process that can clarify project objectives and deliverables, show the scope of the work, control risks, and manage resources are the primary goals of the project manager. Depends the organization structure is closer on which side of the matrix management spectrum, some of the responsibilities can be shared among the other units, but regardless of dealing with a strong matrix, week matrix, or something between these two ends, the objective is to establish this process first. On the other hand, Agile is the ability to create and respond to change.