| This type testing is a part of agile testing. | In waterfall testing, testing is a separate phase. |
| In Scrum testing, development team and testing team work together. | In waterfall testing, development team and testing team work separately. |
| It also checks performance of the software. | It doesn’t check performance factor. |
| This needs co-ordination between development and testing process. | Development and testing process are separate. |
| The works needs to be divided into teams, and then in teams as an individual responsibility. | Here, work is divided into phases. |
| This testing is used in Agile Software Development process. | This testing is used in traditional software development process. |
| Testers are involved in the requirements. | Testers may or may not be involve in the requirements. |
| This tests each module after its development. | Whole software is tested together. |
| It is used commonly. | Waterfall testing is less used now-a-days in software engineering. |
| This is used in complicated software testing. | Simplicity of Waterfall testing is simple. |
| This is more reliable. | This is less reliable. |
| User involvement in Scrum testing is for the whole development process. | User involvement in Waterfall testing is only in beginning. |
| Customer is kept on loop about every step taking place. | Customer is contacted only on the delivery date. |
| In Scrum testing activities starts along side development. | In Waterfall testing activities start after the development activities are over. |
| It works well with difficult projects. | It works well with smaller projects. |
| There is no defined stage. | There are defined stages to work on any project. |