|
| | SCRUM | SOA | Commonalities |
|
| 1 | Ones that have been finished vs. stories that have been scheduled | As a percentage of overall services, new created services and utilized | The proportion and percent of finished tasks (services) performed in one sprint are determined to use these two indicators. |
| 2 | Team velocity | The length of time it takes to build a service and the average length of time it takes to develop a service | Such three factors track the team’s efforts for a service that should be delivered within a sprint in regard to per-sprint and duration. These metrics could be combined to determine SOA and SCRUM integration by developing a team velocity metric. |
| 3 | Customer satisfaction | Confirmation of quality of service | When adopting the SCRUM developmental methodological framework, certain metrics can be employed to assess the efficiency of service. Both measures have quality as a common attribute, and they can be utilized to provide the metric for evaluating SOA and SCRUM integration. |
| 4 | Team enthusiasm | Violation of architecture policies | The team members will interact in a friendly, collaborative fashion when they are happy, content, and working in a pleasant environment. They will devote their whole attention and concentration to product development, ensuring that product quality remains standard. They will also obediently observe the predetermined architectural policies and rules. We can also produce a huge number of high-quality services in a short length of time if the SCRUM team is happy and in a relaxing environment. As a result, we can say that the SCRUM metrics “team excitement & communication”, “violations of architecture policies”, and “median period to service creation” is dependent and also can affect the project when they were not targeted. Within the development platform, such metrics are employed to assess how employees adhere to rules and processes. |
| 5 | Team communication | Average time to service development |
| 6 | Advancement of the process in retrospect | Availability and usefulness of the service | A single SCRUM and SOA metric can be created by combining the two metrics. Because all SCRUM procedures conclude with a retrospective meeting, it is the last opportunity to revive the overall activities. Whenever these services get completed in a sprint, an evaluation meeting will be conducted to evaluate the produced service's performance and usefulness, such as how to access the service & how it operates. |
| 7 | Control of technological debt | Project and maintenance costs are reduced | The major goal of these two measures is to lower product development costs by making the maximum use of resources and team members' abilities. These two measures can be combined into a single metric to allow SCRUM and SOA techniques to be used together. |
|
