Last month the Association for Software Testing (AST) announced a new partnership with Altom, the owner of BBST®, that enables the AST to refresh our curriculum lineup with the new BBST® Community Track and help fund the future growth of the materials. This partnership and refresh are a huge milestone for the AST.
For some perspective: Cem Kaner developed the BBST courses over a long period of time, starting with Hung Nguyen in the 90s. In the 2000s after Cem Kaner was recruited to Florida Institute of Technology he and Becky Fielder received grants from the National Science Foundation to adapt them into online courses. Some time later Cem began collaborating with the AST to teach and develop the courses further. Those courses became known as AST-BBST to differentiate the way they developed and were taught (by passionate volunteers). Eventually Cem formed his own company, developed BBST® further and sold it to Altom after he retired.
BBST® classes are well known for their depth of core testing knowledge and focus on improving through peer review work. That’s great for students but frankly it’s a maintenance challenge. Long before I started with the AST the problem has been, how do we properly maintain and evolve the materials and classes?
A month ago someone on LinkedIn thanked a website and the person running it for helping them learn. They recommended others use the site. When people in my network commented on how the site wasn’t any good, I took notice. It reminded me of what Seth Godin said in ‘Not good enough’ is an easy place to hide:
The people who are paying attention are the ones who are trying. And shaming people who are trying because they’re not perfect is a terrific way to discourage them from trying. On the other hand, the core of every system is filled with the status quo, a status quo that isn’t even paying attention.
This is a really hard but important distinction to remember: It’s easy to criticize work in the name of peer review but end up on the bandwagon of not good enough. (There’s a fine line between effective peer review and unwanted comment).
One major lesson I’ve learned from interviewing testers is most aren’t paying attention. They aren’t looking around at how to improve. They don’t read blogs, books or take classes. So while it’s tempting to criticize the work people are putting out, it’s more impactful to reach out to those who are doing nothing and encourage them to try.
I recorded and submitted my 7 minute talk on “Using Test Idea Catalogs for Better Testing”. The premise is:
Testers can develop a set of tests or test concepts for a specific object or risk and re-use them in similar projects or products. Catalogs come in many shapes and forms, they can be lists or more detailed. They can be public or private. They can be developed by individual testers or as teams within companies. But they all help you test better!