# Improvements for the Planning Process in the Scrum Method
## 4 Results
### Case Study--Conflict Resolution in Sprint Planning Using BeCoMe Method
#### 4.7.1 Choosing the Right Tasks for Sprint  
A conflict arose when setting up the tasks for the next sprint. The entire team was unable to reach a unanimous agreement on selecting the appropriate tasks for the fourth sprint in the project. To construct the best compromise sprint assignment, the team utilized the results of this research and employed the BeCoMe method to select the correct tasks. The BeCoMe method can find the best compromise solution using a Likert scale of 0-25-50-75-100 (Strongly disagree/Rather disagree/Neutral/Rather agree/Strongly agree). A preliminary broad assignment of 15 tasks was selected, for which there was a general consensus that they could be considered for the next sprint.  
The question for each task under consideration was as follows: \"Rate whether the task [task name] belongs in the next sprint on a Likert scale of 0-25-50-75-100 (Strongly disagree/Rather disagree/Neutral/Rather agree/Strongly agree)\". Each team member then anonymously rated the prepared tasks using this Likert scale.  
By integrating the BeCoMe method into the sprint planning process, the team could effectively resolve conflicts and make more data-driven decisions, enhancing the overall efficiency and effectiveness of their project management approach.  
The Table 2 shows the results of the team's investigation. Each task was rated by each team member on a scale of 0-100 (Strongly disagree--Strongly agree). The answers obtained were entered into the BeCoMe calculation, and each task received its rank-rating, determining the common consensus and the best compromise solution for the entire team.  
\begin{table}
\begin{tabular}{c l c c c} \hline \hline \multirow{2}{*}{**Task**} & \multicolumn{2}{c}{**Best**} & \multicolumn{1}{c}{**Max. Error of**} & \multicolumn{1}{c}{**Include in**} \\  & **Compromise** & **Estimate** & **Assignment** \\ \hline \multirow{2}{*}{1} & \multirow{2}{*}{Email System Integration—Receiving Emails: Implement functionality for receiving emails into the CRM.} & \multirow{2}{*}{94.5} & \multirow{2}{*}{0.5} & \multirow{2}{*}{YES} \\  & & & & \\ \hline \multirow{2}{*}{2} & \multirow{2}{*}{Email System Integration—Sending Emails: Implement functionality for sending emails from the CRM.} & \multirow{2}{*}{93.5} & \multirow{2}{*}{1.5} & \multirow{2}{*}{YES} \\  & & & & \\ \hline \multirow{2}{*}{3} & Notifications—New Lead: Implement notification for the creation of a new lead. & \multirow{2}{*}{68.65} & \multirow{2}{*}{1.35} & \multirow{2}{*}{YES} \\  & & & & \\ \hline \multirow{2}{*}{4} & Notifications—Lead Status Change: Implement notification for the status change in an existing lead. & \multirow{2}{*}{68} & \multirow{2}{*}{0.5} & \multirow{2}{*}{YES} \\ \hline \multirow{2}{*}{5} & Database Optimization—Table Review: Review and optimize the structure of database tables.} & \multirow{2}{*}{75.95} & \multirow{2}{*}{4.05} & \multirow{2}{*}{YES} \\ \hline \multirow{2}{*}{6} & Database Optimization—Implement Indexes: Add and optimize indexes in the database. & \multirow{2}{*}{72.75} & \multirow{2}{*}{2.25} & \multirow{2}{*}{YES} \\ \hline \multirow{2}{*}{7} & User Roles—Define Roles: Define various user roles and their permissions. & \multirow{2}{*}{84.25} & \multirow{2}{*}{0.75} & \multirow{2}{*}{YES} \\ \cline{1-1} \cline{4-4} \cline{5-5}  & & & & \\ \hline \hline \end{tabular}
\end{table}
Table 2: BeCoMe results based on expert evaluation of the individual tasks.  
From this knowledge gained, further progress can be made, and agile team discussions can take place to compose the tasks for the next sprint. However, in this particular case, the team could not agree on the exact number of tasks for the next sprint. The resolution of this additional conflict situation is described in the second part of this case study, Section 4.7.2.