| Metric | Traditional development process | Agile development process | Study that reported |
| SDLC | Linear | Iterative | [9] [10] |
| Development style | Traditional methods are predictive (plan?driven) | Agile methods are adaptive | [11] - [14] |
| Documentation | Enough documentation to be able to answer all questions that might be asked in the future. | Light (replaced by face to face communication) | [7] [15] |
| Customer involvement | in traditional approaches the customer is mainly engaged during the early phase of the project | Agile methods engage the customer throughout the whole development process. | [13] [16] - [18] |
| Change | Resistance to change | Welcoming to change, even changes are brought in late in the project. | [19] [20] |
| Size | traditional methods are able to manage effectively large project | Manage effectively requirements in small projects but not in large ones. | [13] |
| Planning scale | Long term | Short term | [13] |
| Management | process oriented, command and control | People oriented, leadership and conformity. | [11] [12] [15] [21] [22] |
| Team organization | Pre- structured teams | Self organizing teams | [23] |
| Ownership | Ownership belongs to only project manager | Shared ownership | [19] |
| Prioritization | Requirements are typically prioritized once. | Prioritize feature lists repeatedly during development | [24] |
| Customer feedback | At the termination of the project | At the completion of every sprint | [25] |
| Risk identification | No risk identification. | Early identification and mitigation in every sprint. | [25] |
| Time between specification & implementation | Long | Short | [13] |
| Delivery | Delivering artifacts phase wise and delivery of working software at the end of project. | Demonstration and delivering working software et the end of every sprint. | [25] |
| Measure of Success | Conformance to plan | Business value delivered | [3] |