## 5 Case Study of Applying the Proposed Scope Estimation Methodology
\begin{table}
\begin{tabular}{c c c c c c c c c c} \hline \hline \multirow{2}{*}{**Context**} & \multirow{2}{*}{**NoRAT**} & \multicolumn{2}{c}{**Transformed from**} & \multicolumn{2}{c}{**Transformed from**} & \multicolumn{2}{c}{**Transformed from**} & \multirow{2}{*}{**Transformed from**} & \multirow{2}{*}{**FnoR**} \\  & & \multicolumn{2}{c}{**Story Map**} & & & & & & & \\ \hline  & & **NoRAT** & **NoRO** & **NoRAT** & **NoRO** & **NoRAT** & **NoRO** & **NoRAT** & **NoRO** \\ \hline  & & & & & Actor: Adopter & & & & & \\ \hline Search for a pet & 17 & 6 & 0 & 6 & 4 & 0 & 0 & 5 & 2 & 11 \\ \hline Shelter information & 2 & 2 & 1 & 0 & 0 & 0 & 0 & 0 & 0 & 1 \\ \hline Pet & 14 & 4 & 1 & 1 & 1 & 2 & 0 & 7 & 3 & 9 \\ \hline Application & 25 & 9 & 3 & 5 & 3 & 2 & 0 & 9 & 1 & 18 \\ \hline Communication & 1 & 1 & 0 & 0 & 0 & 0 & 0 & 0 & 0 & 1 \\ \hline Login & 10 & 6 & 2 & 2 & 1 & 0 & 0 & 2 & 1 & 6 \\ \hline Adopter profile & 4 & 0 & 0 & 0 & 0 & 1 & 0 & 3 & 0 & 4 \\ \hline Archive & 3 & 3 & 0 & 0 & 0 & 0 & 0 & 0 & 0 & 3 \\ \hline Total & 76 & 31 & 7 & 14 & 9 & 5 & 0 & 26 & 7 & 53 \\ \hline  & & & & & Actor: Manager & & & & & \\ \hline Pet & 19 & 7 & 2 & 2 & 2 & 1 & 1 & 9 & 3 & 11 \\ \hline Adopter profile & 4 & 2 & 0 & 1 & 0 & 0 & 0 & 1 & 0 & 4 \\ \hline Application & 21 & 1 & 1 & 5 & 3 & 0 & 0 & 15 & 5 & 12 \\ \hline Archive & 9 & 6 & 1 & 0 & 0 & 0 & 0 & 3 & 1 & 7 \\ \hline Shelter & 4 & 0 & 0 & 0 & 0 & 0 & 0 & 4 & 0 & 4 \\ \hline Total & 57 & 16 & 4 & 8 & 5 & 1 & 1 & 32 & 9 & 38 \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Numbers of requirements after transformation from source models and reconciliation (NoRAT—number of requirements after transformation from source; NoRO—number of requirements removed as overlapping; FNoR—final number of requirements after reconciliation). Figure 14: Using the estimation tool in the OTAAT project Estimation step. Figure 15: The results of the scope estimation for the OTAAT requirements in terms of story points and levels of clarity. If the OTAAT project scope estimation had been based only on the Story map (as is quite common in Agile software development projects), the number of gathered requirements would have been much smaller, as only 47 requirements were captured in the Story map during the OTAAT requirements workshop. These 47 requirements were evaluated in 566 story points. By introducing additional models during the requirements workshop, the team was able to capture more of the potential product requirements, and the final number of gathered requirements was 91. The final estimate of the scope for these 91 requirements was 938 story points, which revealed a higher complexity of the potential product than the estimate based only on the Story map. Such a strategy of estimation ensures awareness of the higher complexity of the project in its early phase, both internally in the team and by the client. For the OTAAT project, the contract was prepared for the development of minimum viable product (MVP) based only on the requirements with the highest priority. The number of highest priority requirements used to calculate the MVP scope was 50, and the calculated scope itself was 408 story points. Of the 50 highest priority requirements, 12 were captured in the Story map, and 38 originated from other source models. Some of these 38 requirements might have been also captured in the Story map, but were eliminated during the overlap analysis, when the requirement from another source model was chosen as more suitable. The OTAAT project development team was satisfied with the proposed early phase scope estimation methodology, and stated that the usage of the methodology increased the clarity of the project requirements and revealed its complexity. It has raised the teams' confidence in the captured requirements and the calculated scope. It also helped ensure better alignment both within the team and with the client.