Skip to main content

A Year in Review

The following post came to mind as I was writing my year-end self-evaluation, and provides a brief glimpse of where I started the year and how I got to where I am today. 

This year has been filled with diverse challenges, including ongoing employee issues, the continued mindset of "get it out the door", another reorg of the IT department, and the real possibility of the commoditization of testing within IT. However, as is often the case, challenge spurs innovation.

In preparing for working on the team's seven-year strategic plan, I stepped back from the day-to-day operations of my team, and took a critical look at the work we were doing and the services we performed. What I saw was that the testing services we were providing for the company were, in many cases, nearly indistinguishable from the testing services provided by alternative sourcing strategies, with the primary differentiator being cost, not quality. Seeing the threat of the commoditization of testing as a real possibility emphasized, to me, the need to improve the quality of service the team provides.  

I began by redoubling my efforts to establish a testing organization that provides true value to the business. I knew that I needed more ideas than I could generate by myself, so I started looking for industry colleagues from outside the company to better understand the challenges I faced, the solutions that are available, and to discover new ideas to incorporate into our practices. Leveraging the power of social media, I have been able to establish relationships with peers and leaders from the international software testing community. Through these relationships I have received not only validation, correction, and extension of ideas that I have had regarding changes and improvements to the way that we test software, but also an influx of new and innovative ideas that, once implemented, will truly establish the team as the definitive source of testing expertise and services within the company.

Many of the ideas require a fundamental shift in the way we think about quality and the skills required to provide quality. If we view quality as value to some person at some time, then we realize that quality changes as the needs and priorities of the business change. It also highlights the importance context plays in delivery of a quality service. By moving towards a context-driven approach, the team has taken the first steps in establishing a position that allows us to stay more relevant to the business by asking the business "what is of value to you" and using that information to address their needs rather than what we think those needs are.

There is another benefit of the new paradigm in that it allows us to address the commoditization singularity - the point at which the value of the testing we provide becomes indistinguishable from the value of the testing provided by alternate sourcing strategies, and thus becomes a commodity. This paradigm shift allows us to address that by keeping in touch with the needs of the business, and having the skills and agility to be proactive as those needs are changing, rather than being simply reactive after the change is complete or, even worse, not changing at all.
Labels:

Comments

Post a Comment

Popular posts from this blog

Takeaways from the Continuous Automated Testing Tutorial at CAST2014

I had the opportunity to attend Noah Sussman's tutorial on Continuous Automated Testing last week as part of CAST2014. It was a great tutorial, with most of the morning spent on the theory and concepts behind continuous automated testing, and the afternoon spent with some hands-on exercises. I think that Noah really understands the problems associated with test automation in an agile environment, and the solutions that he presented in his tutorial show the true depth of his understanding of, and insight into, those problems. Here are some of the main highlights and takeaways that I got from his tutorial at CAST2014. Key Concepts Design Tools – QA and testing are design tools, and the purpose of software testing is to design systems that are deterministic Efficiency-to-Thoroughness-Trade-Offs – (ETTO) We do not always pick the best option, we pick the one that best meets the immediate needs Ironies of automation – Automation makes things more complex and, while tools can make
11 comments
Read more

Mission Statement, Definition of Software Testing, and Goals of Software Testing

Why I blog? What’s the difference between a good tester and a great tester? I think the main thing is the ability to think for yourself and to be able to incorporate your experiences as a tester back into the context of your testing practices.  I think that if you look at the software testing community and pay attention to who has good ideas and who does not, you’ll find that the vast majority of people with good ideas emphasize their experience, what they have learned from it, and how they incorporate that back into their testing. Writing about my thoughts and experiences in software testing provides an opportunity for me to take a critical look at what I thought about a subject, assess it in the context of experience and information gained since I first came to think that way, and then update or reaffirm my thoughts on the subject. It also allows me to share my thoughts, experiences, successes and failures with others, creating an additional feedback loop. That, to me, is one
6 comments
Read more

Let’s Continue to Drive Software Testing Education Forward

It’s Time to Embrace the Student Who Learns Differently Last in a series. In my last two posts I’ve written about enhancing the student and instructor experience in the AST’s BBST courses by focusing on updating the Fieldstones and making BBST courses more accessible by identifying some of the more common obstacles to BBST participation, and then working collectively to find ways to lower or remove those obstacles. In this post, I want to discuss the third and final area I would like to concentrate on if elected to the Board of Directors: researching and establishing alternate approaches to teaching that better suit different learning styles. As members of the AST, we have access to some of the best information and training available in the field of software testing. The AST hosts the Conference of the Association for Software Testing (CAST) each year, providing full-day tutorials, keynotes, and track sessions. They also offer four separate BBST courses:  Foundations, Bug
11 comments
Read more