# Improvements for the Planning Process in the Scrum Method
## 5 Discussion  
In [PERSON]'s case study, he evaluated the proportions regarding the duration of selected specific tasks within the sprint with respect to others. He reported on the development team's performance in completing scheduled tasks by sprint: \"The teams completed on average only 42% (median 35.71%) of story points (tasks) planned for the first sprint and spent on average much more than one ideal day of work per story point (mean value 27.86, median 15.88 h/story point)\" [19]. He further states that in each subsequent sprint, the percentage of tasks completed increases. In the second sprint, the percentage of successfully completed tasks planned for the sprint was around 75% and continued to increase in subsequent sprints. However, the value of successfully completed tasks scheduled for the first sprint (42%) is trivial, and the value in the second sprint is also far from ideal [19]. These issues highlight significant reasons for the failure of projects managed by the agile Scrum method. Project failure is defined as the inability to deliver the completed functional work on time and within the specified cost. The proper scheduling of sprint tasks appears to be one of the most critical phases of project management in Scrum. It can be concluded that leaving such an important phase of project management to human intuition is extremely inadequate. To address this shortcoming of the Scrum method, the implementation of the BeCoMe method could serve perfectly. BeCoMe is a mathematical method for selecting the best compromise solution in a few simple steps. The BeCoMe method provides a very fast calculation in situations where an accurate and rapid compromise solution is needed. Another advantage is that experts can express their opinions using real numbers, fuzzy numbers, or Likert linguistic terms. The use of the above-mentioned method is useful in conflict situations that arise in non-cohesive developer teams or larger teams. The BeCoMe method will offer the right compromise solution quickly and steer the developers in the right direction for the next sprint. However, to fully leverage the advantages of BeCoMe, a few more steps need to be incorporated into the planning process. The first step is to compile an assignment of valued expert opinions. Then, based on this assignment, the second step involves performing the computation using the BeCoMe method to compile the final verified task assignment for  
Figure 5: Graphical expression of the decision situation. the sprint. The question remains of how these added steps will affect the agility level of the project. It would be ideal if this research were further extended to address this question. On the other hand, the results show that this improvement in the planning process of each sprint brings an equal evaluation of the votes of all team experts, thus fulfilling one of the agile principles. Moreover, this step is not mandatory, and not all sprints in the project need to be planned this way. This step can be utilized in rare situations where the entire team cannot unanimously agree on the assignment for the next sprint. A further extension of the research could involve providing precise guidance on the implementation of the BeCoMe method in the Scrum planning process and determining its impact on the success rate of project management. In addition to evaluating the BeCoMe method, it is important to compare it with similar existing methods like Weighted Shortest Job First (WSJF) used in the Scaled Agile Framework (SAFe). WSJF prioritizes tasks based on their cost of delay divided by job size, balancing urgency and effort required. While WSJF is useful for large-scale agile projects, it has limitations in ensuring team consensus and managing diverse opinions effectively [33; 34; 35]. Consensus Building:  
WSJF: WSJF does not inherently address the need for consensus among team members, and it is often driven by key stakeholders, which might lead to a lack of buy-in from all team members [33].