Mar 28, 2011

Appreciative Enquiry

The drive to improve the maturity of the IT processes has been around for a few decades. There have been some significant developments and evolutions in the maturity models that govern the software processes. Software Testing also has seen some very significant developments including enhancements to the existing models and introduction of new models. While I appreciate the methodologies that are used by each of these models, I see a larger commonality among all these models. They focus on what is not standard, what is not repetitive, what is not scalable and what ever else that is not right. Once we know what is not right, we try to prescribe solutions to fix the problems. So, organisations also look at these “inspectors” or assessors as people who probe for issues and deficiencies, and rate them at a certain level of maturity. Every assessment includes some information about the good practices, but the focus is generally on the “opportunities for improvement” by fixing the deficiencies. Little consideration is given to what has worked well in the groups or teams within the organisation and to see how that be replicated across the organisation. It is in this context that I consider Appreciative Inquiry as a means for organisational transformation. Shifting from what is not working to what works well or what has worked well is offcourse a major shift in the approach, and hence may require a lot of preparation and facilitation so that the efforts are driving the organisation towards its ‘desired’ end state. Appreciative Inquiry is not a new concept. In fact, it has been around since 80’s and has been used by a lot of practitioners facilitating change management. What attracted me is the focus on driving change through identifying the positive aspects (appreciation) of something successful and using that to design what will help in bringing in desired outcomes. Probably a very powerful and positive way of bringing in all those changes that we have been triggering through pointing gaps and prescribing fixes. I think I need to take a deeper look at this.

I test. Therefore I am.

Nov 15, 2009

From a tiny island in Australasia

It has been quite some time since I posted something to my blog. Not because there was nothing mych to post nor because the testing industry was clam and stagnant since I posted last...Infact, something new is happening to testing every lunar cycle or even earlier.

The worl has started hyping about cloud, not the ones that cover the moon but the one that connect too many computers in too complex a way that every one start loosing it it - as if they are covered by a dense colud. All was well till Garter came up and declared that the entire hue and cry about cloud computing is a myth that will burst in 2010! what a sadistic way to kill an emerging spirit...

Whether the myth of cloud computing will stand or wither away, the testing industry has caught on with its on new hype - CROWD TESTING. Who said the testers lack creativity! Many successfull crowd sourcing initiatives have already come up and is fast becoming more and more popular. Will this lead to a creation of a true gloal team built on collaboration and trust? I do not know. I did not even knew that that I was participating in a successful crowd sourcing experiment when I played Google Image labeller sometime (long) back!
Now I am in North Island, a small yet beautiful island in New Zealand where I see very few people around - leave alone testers... the terms croud sourcing and crowd testing excites me because I can easily visualize a lot of people sitting around me and testing... I am wrong again... There are beautiful and robust platforms coming up to support crowd testing. After seeing the UTest platform for crowd testing, I really have started wondering why it took so long for some one to think of building it... I think I need to learn to sit alone in a crowd and do testing...
I test. Therefore I am.

Jul 14, 2007

Context Driven School

It has been quite some time since my last post. I was about to share my excitement about context driven testing, and a lot of changes happened in my career including changing job, taking up new responsibilities etc. Anyways, Context Driven testing is still a new and active topic, and I believe it will continue to be so.

The testing industry was ‘maturing’ with Best Practices and Industry Standards when the context driven school evolved. The knowledge that there are no best practices that exists in the testing domain was (and to some extent, still is) against the conventional wisdom that preaching by the testing service providers which tried to build their strength on best practices that are based on prior experience, which iteratively refined the testing process over time.

‘Context driven testing’ takes into account, the different ways in which the software program will be used. It also considers the varying capabilities, interests and needs of the individuals using the program along with other influencing environmental factors. This brings in a lot of agility to testing, which makes context driven to be considered a variant of agile practices.

The approach identifies tests based on the context, and explores the possibilities so as to optimize the software for its intended users and target environment rather that going by the traditional method of validating requirements using a defined and static approach.

But, there could be issues with this approach in terms of the traditional test metrics, and might even require a new set of measures altogether. I tried to draw a set of rules for this games, to make it ‘more structured’ to the testing wisdom. I was successful in doing that to a certain extent at which I got a revelation that I am actually bringing it back to the traditional method, thus stripping off the benefits, un-intentionally. In other words, I was trying to draft another ‘Best Practice’ that the context driven school challenged in the very beginning!

Listen to this article

Lazy? Listen to this article

Jul 5, 2006

Thoughts on Best Practices

Whole of June I was on a consulting assignment at a company in Wall Street. Right from the project initiation, our sales team has mentioned about our newly achieved CMMi Level5 certification on every available opportunity. I was also proud that I am associated with something big. During the last few years, our SQA team which works for maintaining and upgrading all these, have enlightened me on the great certifications that we are preparing for.

In one of the casual discussions with the client, the CMMi came up again and I started explaining to him in detail, the great processes that we religiously follow because we are CMMi Level 5. After listening for some time, he asked me “So, how do I benefit from your certification?”

What a stupid question to ask! Doesn’t he understand that I follow a lot of “processes”? Why can’t he appreciate all the effort that goes in to the system to prepare all those matrices and analyzing them? Did he not get a chance to have a look at our “quality site” that lists an ever growing list of processes? Even with all these questions in mind, I was struggling for an answer.


As testers, what are we delivering to our client if we have a CMMi Level X certification? Does Carnegie Mellon Institute hold the key to quality, which they distribute on a retail basis? What is the best testing practice that every testing company in the world should follow? It triggered my curiosity.

I was searching for best practices, searched on Google, I got many. Talked to friends, I got still more. I looked at our company’s quality site. I got still more. There cannot be so many best practices! Something is seriously wrong.

Yes. There cannot be so many best practices. But are there any? Unfortunately, the answer is “NO”. I came to agreement with some of the best names in the industry as to “There are no best practices in software testing. There are only good practices”.
I am sure, I have experienced it, even though never formalised the thought, that every project needs a different focus, a different approach and a different set of heuristics. Only difference is that now I understand it as a reality. Probably the only process that is relevant to all projects is to find the processes that suits the project. The ones that fits into the context. This revelation has lead to one good thing: I got attracted to the context driven school.


More about it later.

Jul 4, 2006

Testing Test Readiness

Qualifying a build for test is not easy always. A build that is not “ready” for test, pushed into the test environment can eat a considerable amount of your testing effort thus upsetting the test estimates as well as schedules.

There of course cannot be a universally applicable way to test the test readiness of a build before it gets deployed in the test environment. But, carefully planned smoke tests prior to acceptance of a build for testing can considerably save the time and effort that goes into testing. In a perfect world, developers unit test their code before they deliver the build. But unfortunately we all live in a world that is far less than perfect. We do need to test; we also need to test whether the build is ready for the test. Probably this is one of the most important instances where the testers “refuse to test”.

It therefore becomes important that the selection of tests for smoke testing (the test readiness test) should be appropriate and well representative. There can be a core test set and a supplementary test set based on bug history, testers error guessing capability, prior experience with this or similar applications etc. Some of these tests may retire during successive cycles.

It is a good idea to automate the core test set to reduce the cycle time. You may even want to share the smoke test suite with the developers so that they know what you are looking for. It is always a good idea to brainstorm before arriving at the core smoke test set.

I found some interesting thoughts on smoke testing here...