|
| | Scrum | SOA | Commonalities |
|
| 1 | Completed stories versus planned stories | Newly created & used as a percentage of total services | The main purpose of these two metrics is to measure the ratio and percentage of completed work (services) developed in one sprint. |
|
| 2 | Team velocity | Development time & average development time to develop a service | These three metrics measure the team progress in terms of sprint and time required for a service which is to be completed in a particular sprint within time. So these metrics could be combined into team velocity metric which will be considered as a metric for SOA and Scrum integration. |
|
| 3 | Quality delivered to customer | Service quality assurance | The aim of these metrics is to measure the service quality when applying the Scrum development process model. The quality is a common feature for both metrics which can be combined to make a metric for SOA and Scrum integrations measurements. |
|
| 4 | Team enthusiasm | Violation of architecture policies | When the team members are happy and satisfied and work in comfortable environment, then they will communicate with each other collaboratively and in a friendly way. They will have full attention and focus on product development through this product quality will remain standard. Also they will willingly follow the preplanned architecture policies and rules. When the Scrum team is happy and in restful environment, then they can develop a large number of services of high quality in small amount of time. So we can say that the “team enthusiasm & communication” metrics of Scrum and “violations of architecture policies” & “average time to service development” metrics are dependent on each other; these can have an effect on project when these are not concentrated. These metrics are used to measure the behavior of how they follow rules and policies during development environment. |
| 5 | Team communication | Average time to service development |
|
| 6 | Retrospective process improvement | Service accessibility & usability | These two metrics can be integrated together to represent a common metric for both Scrum and SOA. Because the retrospective meeting is held in the last of all practices of Scrum in which the overall activities could be revived, when the services are developed in a sprint, a review meeting will be arranged in which we can test the developed service functionality and usability of how to access the service and how it works. |
|
| 7 | Technical debt management | Reduction in the project and maintenance expense | The main purpose of these two metrics is to reduce the product development cost through best management and utilization of resources and team member’s skills. These two metrics can be integrated in one common metric for combined use of Scrum and SOA approaches. |
|
