# Improvements for the Planning Process in the Scrum Method
## 4 Results
### Case Study--Conflict Resolution in Sprint Planning Using BeCoMe Method
#### 4.7.2 Selection of the Correct Number of Tasks for the Next Sprint  
The team had to resolve a conflict of opinion on the ideal number of scheduled tasks for the fourth sprint of the project and find the best compromise. The question was \"What is the ideal number of tasks for fourth sprint from a list of relevant tasks that could be implemented in this sprint?\" To resolve this conflict, the solution of implementing the BeCoMe method was used. The advantage of the BeCoMe method is that experts (team members) can express their standpoints in three ways: (1) as a crisp number; (2) as a fuzzy number in a format: Preferable value, Lower limit, Upper limit; and (3) as a quantity in the Likert scale: \"Strongly disagree\", \"Rather disagree\", \"Neutral\", \"Rather agree\", \"Strongly agree\" or a similar linguistic scale. A list of relevant tasks that could be implemented in the second sprint was compiled. Furthermore, an interval!5;!15? for the number of tasks in the second sprint of the project was designed. The team members chose the ideal number of tasks from a pre-prepared list of tasks they could potentially implement in the second sprint. Team members were asked their opinion on the following:  
* Best proposal for sprint 2 (see Figure 4);
* The lower limit of feasible tasks for sprint 2;
* The upper limit of feasible tasks for sprint 2. \begin{table}
\begin{tabular}{c l c c c} \hline \hline \multicolumn{1}{c}{**Task**} & \multicolumn{1}{c}{**Best**} & \multicolumn{1}{c}{**Max. Error of**} & \multicolumn{1}{c}{**Include in**} \\  & \multicolumn{1}{c}{**Compromise**} & \multicolumn{1}{c}{**Estimate**} & \multicolumn{1}{c}{**Assignment**} \\ \hline
8 & User Roles—Access Control Implementation: & & & \\  & Implement access control based on the defined roles. & 60.75 & 0.75 & NO \\ \hline
9 & Workflow Automation—Sales Process Templates: & & & \\  & Create and implement a workflow template for a typical & 89.5 & 0.5 & YES \\  & sales process. & & & \\ \hline
10 & Workflow Automation—Task Escalation: & & & \\  & Implement rules for automatic task escalation when & 88.75 & 1.25 & YES \\  & deadlines are missed. & & & \\ \hline
11 & Data Export—CSV Format: & & & \\  & Implement functionality for exporting data to CSV format. & 56 & 1.5 & NO \\ \hline
12 & Data Import—CSV Format: & & & \\  & Implement functionality for importing data from CSV files. & 58.5 & 1.5 & NO \\ \hline
13 & Mobile Application—Contact Synchronization: & & & \\  & Implement contact synchronization between the mobile & 62 & 4.5 & NO \\  & app and the web CRM. & & & \\ \hline
14 & Mobile Application—Lead Display: & & & \\  & Implement lead display in the mobile application. & 55 & 5 & NO \\ \hline
15 & Dashboard—Sales Report: & & & \\  & Create a basic sales report on the dashboard. & 68.25 & 0.75 & YES \\ \hline \hline \end{tabular}
\end{table} 
Table 2: _Cont._Figure 4 illustrates the simplicity of the BeCoMe calculation (determining the best compromise solution). To obtain the result, all one has to do is to enter the individual expert opinions into a table in the BeCoMe Excel software. Figure 4 shows step 1 of the BeCoMe calculation from Section 3.3 of this paper, where expert opinions were constructed using triangular fuzzy numbers. Next, the figure shows the values of step 3, i.e., the computation of the centroids of each expert opinion Gx. The intermediate results of step 2 of the BeCoMe calculation are \(\alpha\ =\ 6.6\), \(\beta\ =\ 12\), \(\gamma\ =\ 9.4\). In step 5, the median is solved, and the calculations of this step are \(\rho\) = 6.5, \(\sigma\) = 11.5, \(\omega\) = 8.5. In the last step (step 5) before calculating the maximum deviation, the results are \(\pi\) = 6.6, \(\varphi\) = 11.75, \(\xi\) = 8.95. Max. The error of estimate can be seen in Figure 4, where its value is 0.27. The result of BeCoMe and the value of the best compromise solution from the given triangular fuzzy numbers is 9.1. From this value, we can deduce that the best possible compromise is the value of nine tasks for the next sprint.