Testing in Agile: roles merge but don't disappear

-
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.



A very great example of it was a truly agile and cross-functional team of criminals trying to rob a Casino in the movie "Ocean's Eleven". It consists of criminals with various primary skills, but when necessary, one is abandoning his primary skill and doing something he is not specialized in.

Thus nature of any project in a complex and ever-changing environment - you will have to adjust your plan to conform to real life. In software developer terms, when QA specialist struggles with testing some functionality, Development specialist may help or do some other test related work. Similarly, if all developers got flu (shit happens), somebody will have to proceed with implementing the functionality. There's no time to wait, a value should be delivered no matter what, and the team should do it's best to help this happen.

Naturally, team members are widening their skills in adjacent areas becoming more general specialist, merging roles. This also is a great tool of decreasing project "Bus factor"

Why roles don't disappear

Still, one can't be very good at everything. It is hardly possible to be great front-end and back-end developer or be both good at writing and testing software. Each skill requires some time to grow. Skill exercised most will always be better developed than others.

Look at "Ocean's Eleven" again. Each of the team members is particularly good at somethings. In a similar fashion, your team will require somebody particularly good in front-end, database development and testing. Naturally, those who have particularly good skills in something will spend more time on exercising their skill, both because it lets us get value faster and because they just like doing their kind of things more. Roles will never disappear entirely, just be less prominent.

So what should I do?

Well, first of all, identify the primary skill you want to have. Choose whatever you like. Be good at it. Try to be best at it. Second, learn something outside your comfort zone. Make curiosity your habit.

And a small disclaimer - fact, that roles will not disappear doesn't mean demand for all roles will stay the same. It is possible that for particular role demand is going down, so try to have other options (secondary skill may be helpful here).

Comments

Post a Comment

Popular posts from this blog

Test automation framework - do I need it at all?

-
Image
While there're lots of information published on the internet about how one should develop/buy a Test Automation solution, there's an elephant in the room - which is the fundamental question "Do I need to do it at all?". That is a good question. While I think that there’re some legitimate contexts where product/project/team can benefit from having a sophisticated test automation solution/framework, my general rule of thumb is “If you need a framework - you do it wrong” . There’re at least several decent papers showing the benefit of unit-testing ([1],[2], [3]), while I could not find any research proving that system level tests could bring better results. Please let me know if you can prove me wrong. There’s at least one half-scientific paper showing the benefits of unit tests in comparison to integration/system level tests [4] There’s a good paper bringing a notion of running/writing and maintaining test vs. the benefit of having/running it at...
Read more

Efficient test automation - Secret #1 | Test Club

-
Image
It seems everyone talks about efficient test automation, but not so many people have actually seen it! To cover this I decided to make several videos regarding the secrets of efficient test automation. Today we will talk about the first (and, arguably, the main) secret - realistic expectations. Very often, test automation projects or initiatives are started with the following unrealistic expectations: "Test automation will replace 'manual' testing" "Test automation will provide fast results and benefits" "Test automation efficiency depends solely on test automation engineers" Unfortunately, all those expectations are not realistic! Watch the video to know more!
Read more

An alternative to ubiquitous UI-level checking - Subcutaneous tests

-
Image
Let's assume a hypothetical situation - you were assigned to a project to help with the "test automation" initiative. You have a huge "test plan" as an input, containing hundreds (if not thousands) of "test cases" and you need to do something about it, quick. Problem statement Your first urge (if it is a Web application) may be to write some UI-level automated checks using tools like, you know, Selenium. In fact, there's a huge demand for such "Selenium test automators" in the industry these days. But please, please, don't do this. There're lots of things which make UI-level automated checking the least desirable approach: UI-level automated checks will be slow. There's just no way to avoid it. You can parallel them or do some other tweaks to speed them up somehow, but they still will be slow. UI-level automated checks will be flaky. Partly - because they're slow. Partly because Web browser and UI interface w...
Read more