Adopting Agile Testing Practices

Adopting Agile Testing Practices

This case study can be considered the result of adopting the Scrum framework without applying the suggested Agile testing practices and the impact after actual embracing them. Below you can find issues that were found and the practices that helped to overcome those issues. The main changes where the formation of cross functional teams and the use of test automations. From what it seems, we made one of the most common mistakes as a new Agile team that previously worked with incremental methodologies and tried to use Scrum. After creating multiple projects of different scope, size and technologies, the problem was visible when we went to enterprise level with a platform of 14 different applications, with more than 300K lines of code and near to 10k unit tests. This platform was about to go live but it should be stabilized first. Trying to add functionality on the platform we got in to a spiral of massive bug fixing rounds that worked as an alert, informing us that something did not work as it was supposed to. By this spiral effect it was obvious that something went wrong with the processes that we followed. How we worked Working with Agile methodologies is about building small increments in small iterations, one to four weeks top. At that time, besides the XP engineering practices, the team had adapted partially the Scrum framework by using some of the events such as sprint planning, daily scrum and sprints, but the collaboration between the testing and the development seemed more like a mini waterfall. The developers build a complete functionality (user story) or even a whole sprint...