The State of Testing survey investigates how the testing profession develops. Last week the State of Testing 2018 report has been published. I’m a blog collaborator for this survey, so I highly recommend reading it!
The State of Testing is the largest testing survey worldwide. With about 1,500 participants from more than 80 countries, the survey aims to provide the most accurate information of the testing profession and the global testing community. Held yearly, the survey also captures current and future trends. In collaboration with leading testing bloggers and thought leaders helping us make this survey a reality (…), this survey is all about giving you, as a tester, the ability to better understand your professional status compared to other testers and companies worldwide, and to be better prepared based on current and future trends.
I did an interview with the organizers of the State of Testing survey for InfoQ which explores how trends have developed in the testing profession and provides visibility into different angles of testing and technical aspects of testing.
One of the questions that I asked was about the adoption of Agile Retrospectives:
InfoQ: The report mentions a significant increase in retrospective meetings. What causes this and what can be the result?
Bhamare: This is what I partly meant by multi-faceted role of testers and their contribution to project teams.
By nature of their job-role and the abilities they posses thereby, I feel that testers are endowed with great observation skills that can benefit project teams to improve things that eventually add to product quality. These observations can be at the system level, application level, people level and what not, but the point is, there better be someone who “observes” things, analyses them and presents them in a form that enables team members to see things from a different perspective.
Skilled testers, with their sharp observation skills can make retrospectives far more effective. As Jerry Weinberg explains in his ideas of System Collapse/Explosions and feedback loops to control them, “act early, act small” is the key and testers are naturally best candidates to make the feedback loop optimum for the controller. That’s how I look at this whole retrospective thing.
Montvelisky: Again here we see another indication that testers are joining Scrum and agile teams, taking part in the different activities these teams do.
And in parallel it also indicates that the teams, and the testers among them, are becoming more aware of the value of retrospectives, counting them as “static testing” activities where we have a chance to look not only at the bugs we are finding, but also at the incorrect processes generating these issues, in order to fix the process and not only the bug.
Testers have been striving to work in the quality of the process for ages, and in many ways agile practices such as retrospectives can give us a chance to finally achieve this goal.
The result of this type of processes will hopefully be a more integrated quality culture, where we celebrate and learn from our mistakes in order to improve our working methods and culture.
Read the full interview on InfoQ: 2018 State of Testing Report.