Remembering Steve Irwin

I was truly saddened to hear of the freak accident that killed Steve Irwin (The Crocodile Hunter) recently. It took me a while to realize what I will miss most about Steve. After all, it was so easy for me to drop a quick impersonation into a class – “Crikey, mate! That’s a mean defect!”

The thing about Steve that will stay in my memory is his passion for what he did. He died doing what he loved and there is no way he could have lived without being immersed in nature. Twenty feet away from a crocodile just wouldn’t do for Steve. He had to have his arms wrapped around the croc. I saw him once crawl right up to the opening of a den of rattlesnakes. I live in rattlesnake country and one mile away is a comfortable distance for me.

In my test team leadership courses and tutorials, I discuss the importance of finding where people are passionate and then letting them do things they really love to do. However, the first thing is that people must have a passion for something. I think most people have at least one thing they really love to do. I pity those that don’t.

Passionate people do what they love to do and perform with excellence. They go the extra step to make sure things are right because 1) they love getting it right and 2) they don’t want to appear to be a novice.

A passionate customer service representative spends the extra time with a customer to make sure things are right and gives friendly service, not treat a customer like they just interrupted Monday Night Football.

A passionate delivery person doesn’t leave perishable items on the doorstep in 100 plus degree heat without ringing the doorbell.

I think you get what I mean.

There's a great little book called "The Fred Factor" which I highly recommend. It's a true story about a postman named Fred that does an ordinary job in an exceptional way.

A passionate software tester looks for ways to improve their craft. They mentor other testers and contribute to the profession. They take pride in what they do. They don’t blame others for mistakes. Instead, they learn and improve from them.

I love what I do. (A special shout out to American Airlines “That’s why I fly!”) It means a lot to me when others see that I have passion for what I do. Sometimes people will comment on a class evaluation that they can tell I am passionate about software testing. I know that may seem odd that something as detailed (and sometimes boring) as software testing would float my boat.

Software testing is just the vehicle. What I love is to help people be their personal best so they will have a better job and live. I love helping people that create software find, or better yet, avoid, the problems that may one day cause a user to experience problems, perhaps even injury or death.

I personally hate defective software and the ensuing frustration, but I really love being part of the solution instead of the problem. So, as an honor to Steve Irwin and his contribution to this world, I invite you to join me in praying for Steve’s family and reflecting on:

“What am I passionate about?”

“How can I do more of what I love?”

“Do others see my passion for what I do?”

I’m sure that honors Steve’s life and keep his memory going in our own lives.

At the end of the day, there is much more to life than work. However, as a wise person once said, "If you love what you do, you'll never work another day in your life." As I say, love what you do, but before that, love those around you.

By the way, remember the movie "City Slickers?" Passion is that "one thing" that you care about more than anything else.

Take care and have a blessed day,

Randy

Links of Interest

Here’s an interesting link. It’s the text of a commencement address given by Steve Jobs that echoes this theme:

http://news-service.stanford.edu/news/2005/june15/jobs-061505.html

Here’s a link about “How to Do What You Love by Paul Graham:

http://www.paulgraham.com/love.html

Randy Rice's Software Testing & Quality Blog

The Risks of Risk-Based Testing

I'm sorry about not posting sooner. Things have been busy lately.

I've been doing a lot of writing and training lately. I've been working on some cool new projects as well.

One thing I want to let you all know about is an article that will be published in the October 2006 issue of Better Software. It is titled, The Risks of Risk-based Testing. It occured to me while listening to a recent presentation about risk-based testing that although I use risk-based testing quite often, I have also been burned by risk. So, I wrote an article to detail the 12 ways I have been fooled by risk. In the meantime, you can read a rough version of the article at: http://www.riceconsulting.com/articles/risks_of_risk_based_testing.htm.

Bill Perry and I are also working hard to finish our next book, Testing Dirty Systems. I'm not making any predictions on when the book will be available, but we are working diligently on making final comments for the editors at Dorset House.

Thanks for your support and for reading my blog. I'll be back soon!

Randy

Lessons Learned and Re-learned

This week I embarked on a search for one particular conference presentation I remember hearing at a testing conference a few years ago. This journey down memory lane took me through conference notebooks from the last 15 years.

I started seeing things that I had forgotten from software testing conferences since 1989. Of course, there's a lot of water under those bridges.

Just a couple of weeks ago I was talking with Rick Craig at StarEast about some of those conferences we were at a long time ago and he remarked about how interesting it is that many things are still the same in software testing. A test plan is still a test plan, management still doesn't "get it", we are still on the search for the "magic" test tool, etc.

There have also been some notable new things such as exploratory testing, pairwise testing, and agile methods that have added greatly to the software testing profession.

I could not help but wonder about how much of all of this collective testing knowledge has actually been put to use. I hope for the investment in presenting and receiving this information, it has been helpful to many people, but still I wonder...

I also saw presentation by many friends and remembered many fun times at the conferences with these people.

I've been an independent consultant for over 16 years now and last week I had to relearn a lesson forgotten. The exact lesson is not the important thing. The point is that we often take for granted what we have learned and we can forget even hard lessons over time if we don't revisit them occasionally.

Journaling is helpful for reviewing past lessons learned, but so is reflection. I may even embark on a project to write my own "lessons learned book" just for me.

The great thing is that after relearning this recent lesson, I feel it has burned in even deeper to my being. These are not trivial things. These can be life lessons as well as professional lessons.

How do you revisit your "lessons learned?"

Sudoku - A Great Learning Game for Testers

It happened innocently enought. I was getting ready to board a flight to London and this book of Sudoku puzzles caught my eye in the airport. So, with 7 hours of time ahead of me and 1.5 hours of laptop battery life, I thought, "why not?"

I had seen people engrossed over these puzzles with only numbers instead of words. They look similar to crossword puzzles, but only have the numbers 1 through 9 in the completed puzzle. It normally takes between 15 to 45 minutes to solve a puzzle.

I am now an addict. What I have discovered that these puzzles are a great way to develop mental abilities of deduction and elimination. (Guessing only messes you up.) Of course, these are key skills for testers - to be able to deduce software processing rules and behavior by only what you can observe. (Unfortunately, testers all too often lack access to well-defined software requirements.)

There are also strategies you can learn that makes the process go faster. That's also part of the fun - developing a system you can use over and over. Sound like testing?

So, if you are looking for ways to build you or your test team's abilities to solve problems by deduction, try working a Sudoku puzzle (I recommend starting with the easy ones.), but be careful - they can be addictive!

Here are a couple of links: www.sudoku.com
www.websudoku.com

The Habit of Software Testing

In a software testing class I was teaching last week, the manager of the department made some opening remarks to his team. In emphasizing the importance of the class, he said that his goal was that people would see testing as a habit.

This got my attention because I have heard testing described as an art, a craft, a process, a discipline, but never as a habit.

I have used the illustration before of testing being like flossing teeth - at least for developers. We all know we need to do it, but for lack of time, lack of floss, messes on the mirror, etc., we (at least "I") many times neglect to floss. Then, the dental hygenist gets onto me about it. I feel guilty for awhile, floss every day, then I start skipping days. Before long I'm out of the habit I never really developed in the first place.

Habits are both good and bad, developed over time by repeated performance. You don't necessarily need a written set of instructions to follow every time you do something, but at first they may help.

Before long, you do something so regularly, it starts to feel natural - like stopping by Starbucks every morning on the way to work, or picking up a morning paper at the newsstand.

What would testing look like if it were a habit? Perhaps we would by second nature take a second or third look at something. Or, we would have a checklist or set of test cases we would perform each time just before we sent something to someone.

As testers, we have the habit. We check and double-check things. We look both ways before crossing one-way streets because...well, we just do it.

My thought is that if we can make testing easier, less intimidating, people may see it as more achievable and do it more often until...it becomes a habit instead of a duty.

I've always said in my presentations that if something is easy to do, it's easy not to do.

I really believe this is true in testing. Sure, there are things about testing that can get complex and hard to wrap our minds around. However, there are many aspects of testing that are more related to habit or discipline than knowledge.

So, regardless of your role in your organization - developer, tester, user, etc., I encourage you to do the little things in testing one step at a time and get into the habit of testing.

Welcome!

Hi everyone!

Well, I finally took the plunge and decided to start this blog dedicated to software testing and other software quality-related issues. I still plan to continue to publish The Software Quality Advisor Newsletter online, but this will allow me to create and share information much quicker than I ever can with the newsletter.

I also look forward to interacting with you through the comments to the postings.

Here we go...enjoy the ride,

Randy