Testing in Agile: roles merge but don't disappear
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpGcK6s8CyElZBGIs4qYBfBUovPv4iSdsOwhdhCzl9MJSUMclnR1LXDKmP4DWbPzUzLZ3g-O0f0wGRSOF2tq4KwngNhARgaqbp33qvmgy2Tiqf_nmlj1QnXiHWOoKQQU9aSfiGnu178AE/s400/1fijo7.jpg)
With "Agile methodologies" currently gaining more and more ground, there's a little bit of anxiety, especially among Software Testers, about "Roles merge" idea. Let me comfort you - roles do merge, but they do not disappear. Let's have a look at this in a little bit more details - first, let's discuss why roles do and should merge in Agile projects, then why they will never disappear. Why roles merge An agile team is typically is a cross-functional team having a shared goal (well, at least in theory). For instance, this goal may be to paint a room, prepare a party, write the best ever software or anything else. This means that there will be a situation where one needs to step in and help others do their job.