Thursday, May 21, 2009

Two heroes dealing with uncertainty

Last weekend I was surprised by the persistence of my children which made me proud. Even thinking at that moment how they dealt with the situation makes me still give the proud feeling. Perhaps there are some similarities between their situation and projects we have to deal with.

A few weeks ago my son asked me to join a family event organized by his sport club. The event was a cycle tour through our region. As my children like to cycle in our neighborhood, the thought this was a good idea. So we decided to join that event without knowing what situations we would face. My son is 8 years old and my daughter 6 years old and as normal healthy children they complain whenever. I already calculated that a tour of 20km would be possible for my children to succeed without fewer complaints.

When starting the tour I asked what distance we have to cycle. The organizations claimed it would be between 30 and 40km. After a short discussion with my wife we decided that it would be acceptable although it was raining a bit.

During this day we had to face some challenges:
- not knowing what route to follow as after each track ended with a new piece of the map
- not knowing where to finish
- not knowing what whether to face with
- not knowing what quality the roads would have
- not knowing the unknowns on the route

During the day my children didn't complaint at all, although there were reasons to do. They already made me proud as at the end it turns out we cycled over 60km. Cycling this number of meters is already hard for a person who didn't touch a bicycle for a few years, imagine how hard it has to be for those children on those little bikes.

Afterwards it made me think why we succeeded and why they didn't complaint.
The following reasons came to my mind:
- They accepted the uncertainty
- They trusted me as guide
- We helped them by pushing them when wind was tougher or roads are steeper without they asked for it
- We listened and watched when we assumed they needed a short break
- We called the organization when we got lost
- We decided not to participate in the last track and go straight forward to home. Although we had to cycle still about 10 km. Cycle straight home is better then keep playing the last game with the risk to lose direction and stop more often which would cost a lot of energy
- We rewarded them by telling how good they are doing, how proud we are
- We focused on the beautiful environment instead on our burdens

When looking at these reasons I see some similarities with projects I delt with. Perhaps you also were in projects when things are getting tough people are starting to complain. To avoid this perhaps the following actions can be taken by the project manager/ test manager:
- Make people aware of a certain uncertainty so acceptance is easier
- Make it visible when you ask for help and for what reasons
- Help your project members before they start complaining, reducing the pain before they feel it can help avoiding focusing on that feeling
- Make the team focus on what is happen in the big picture instead of focusing on what goes wrong
- Don't stretch their capabilities for to long, give them a break, although there is time pressure
- Keep telling them when they do things right
- Be open, don't focus on the problems you have as management, keep eye for their situation
- Make the fun happen

Saturday, May 2, 2009

There is more behind

When I am allowed to talk about testing I can get thrilled about this topic. People can see in my eyes that I love this profession. Over the years I met several people I had to work with. Sometimes it was easy to convince them about the meaning of testing and sometimes it was hard to test together.

I think there are several types of persons you will face during the job who need different information

1. People who have not any relationship to testing and are interested in what you are doing
2. People who are ordered to test, without knowledge about testing
3. People who are asked to test and want to learn about it
4. People who want to understand what you are doing, without testing
5. People who are dedicated to testing as you are and want to share knowledge
6. People who are dedicated to testing as you are and don't accept your knowledge
7. People who don't want to do anything with testing and just want you to do it
8. People who don't want to do anything with testing and who don't care

Talking about testing cost time and effort. I think it is important to spend those resources wisely. Therefore before you share information you should identify those types what type of person you are facing with. It will help you to avoid losing those people and spending the wrong effort.

If you acknowledge these types you can train your selves as the message will be different for each type. In your group of stakeholders there might be people who have something to say only don't have the time to listen.

Saturday, April 25, 2009

Art, memorials and software testing

Last weekend I was in Berlin with a couple of friends. Just to celebrate our friendship. One of the things I saw there was the Jewish Holocaust Memorial. It is an impressive huge monument of pilars.





As I don't read manuals when installing software so I also didn't read the introduction of this monument. The process of experiencing I had of monument made me think about similarities within software testing.


Initially we stood there wondering what to do. We noticed standing outside the monument that it has a beginning and at the horizon we saw there was an end; although we couldn't see the last stones. It has also sides and you can enter the monument from any position. Another observation was that the pillars stood in obvious straight rows and in line; they seem to be gray and of different sizes. From the point I was standing I could only oversee a small part of what is happening in the monument as not all paths were visible.

Except of just standing there and accepting the monument as it is we tried to learn more from it. We got the idea just to step of our rented bicycles and take a walk across the field of pillars. At that moment there was no defined plan. We just walk to see what is at the end.




Initially I walked with 2 other friends telling each other what we saw which we couldn't see standing outside the monument. Some findings were like: the pillars are not straight in line at all. The bricks on the floor might also be part of the monument. The pillars don't have all the same size and same gray color. The floor is not equal, although we noticed that it had some curves from out starting point to the obvious end. It curved also sideways. Between the bricks on the floor there were lying small stones of almost equally color.

After a few minutes walking I did what most human beings would do, I start playing. While we started walking together in the same direction it was very easy just to step to the left and "loose" the friends, walk a bit faster and pop up just a few stones ahead while they didn't noticed it. This was the trigger, they started playing along. In the beginning we had no direct goal, only to see if we were able to surprise each other showing up on a different position.

In the beginning we knew in which area the other was, when stepping behind from some stones or crossing other lines and catching a short view of the shoes or jacket. After a moment we were so busy to surprise each other we lost each other. This brought me back to the monument and I made my own context what the monument should represent. I realized how easy it is to loose dear friends with just a small action. In the beginning you know were they should be, after a while you just know they are somewhere, and at the end you don't have nothing; just the believe that they are still there.

After I lost the friends in the monument I tried to find them. I figured out a plan how to approach the web of pillars, walking different routes with different speed. Assuming that they are going from beginning to end I started to walk from left to right. I also deliberately walked the same route back and also backwards. Just to get some information which should give me a clue in which part they were walking. After a while I accepted that I lost my friends in the maze and continued walking alone.

At that moment I noticed I went back to my initial goal: to learn from and experience the monument. Based on my gained knowledge I reshaped the context of the monument. It is not just a pile of stones lined up. It has also the ability to loose people (information) or to gain information (meet other people). I now walked between the pillars just to see what others are doing. I watched their behavior in the center of the monument and also at the borders. I now noticed that some people are doing the same as what I did with my friends. Others were just walking through and talking to each others. A few were using the paths to get to the end and at certain places people were just sitting thinking about the monument or enjoying the nice weather.

That day I learned a lot. Therefore I'm writing this blog. What I learned/did was:

  1. approaching a object not based on best practices, instead asking myself questions what could be the purpose of it and what can I do with it. Thinking about possible value
  2. approaching the object with questions
  3. observing what I see while I experience and trying to redefine new questions
  4. what initially wasn't there can be of importance later on like the difference of depth in the object
  5. rules changing: initially we were just walking, then trying to surprise each other, losing each other in the game, accepting the lost and redefining goals
  6. context is changes after a while
  7. items change of importance: the little stones between the bricks. At a certain moment they had some value. Only at that moment when the thought arise they keep the bricks together
  8. Different moments need different questions and lead to different observations
  9. I would have missed a lot if I approached the object with a fixed plan based on best practices
  10. I enjoyed being there, walking there, learning from it.

Sunday, April 5, 2009

Sun Tzu Art of war and software testing

Finally I found some time to start reading Sun Tzu's The art of war.

In one of the first pages I noticed some text which might explain why it is hard to manage a test process.

"A general must see alone and know alone, meaning that he must see what others do not see and know what others do not know. Seeing what others do not see is called brilliance, knowing what others do not know is called genius. Brilliant geniuses win first, meaning that they defend in such a way as to be unassailable and attack in such a way as to be irresistible. (Thomas Cleary, page 7, Sun Tzu: The Art of War)"

Imagine that you have three generals: one general from business, one general from development and one general from software testing.

As a general from software testing you stand in between the war zone from the other generals. They expect you to provide information so they see what you see about the system and the process. For example: does the process to create the system contain enough information to meet the requirements. They also expect you to provide information so they know what you know. For example: are there some defects in the system.

If the software testing general has to give the views and knowledge away, he can barely be a brilliant genius. Although this is often what the other generals expect from him as he should give positive news about the quality and an advice to go to production. In this case he will give away his knowledge and views away.

To me it seems that we should keep providing this information which will lead that no one will see you’re a brilliant genius. Also you cannot fulfill the role of a software testing general as you will not be successful when you have to give away all information.

Wednesday, April 1, 2009

Magazine: Quality Matters, now with contribution of myself

Recently I send in an article with a though I had in my mind for some while about improving test processes. Sometimes it is better to neglect improvements how obvious they are.

In the 2nd edition of the magazine: Quality Matters my story is presented under the title: "Be innovative! Stop improving your test process."

Sunday, March 29, 2009

The Art of War in Software Testing

Introduction
One of the things I like to do is checking for similarities between history or other methods and software testing. Recently I was heading towards my assignment and got stuck in a traffic jam. You have some of those days. A radio station brought again some information about some war somewhere. Like software testing, no war is the same. No test process is the same. I think there should be some similarity between war and test processes due to the fact they are build upon a mission, vision, strategy, objectives, leadership and a context.
Types of war

On WikiPedia I searched if there was some information about different types of War . On this site I found a table containing types of war explained. (see below)

Environments of warfare

In warfare the environment has a huge impact on the type of battle which take place. You have conventional and unconventional warfare. In conventional warfare an attempt is made to reduce an opponent’s capability through open battle. In unconventional warfare is trying to achieve victory through acquiescence, capitulation, or clandestine support for one side of an existing conflict.



Environments of testing

I think in Software Testing you also might consider conventional and unconventional environments. Below a shot how this could be presented.


Each type of environment has its own type of leadership and needs its own type of strategy and approach.

War strategy

In an old computer game (Civilization II) I learned about Sun Tzu. I understood that this book is a must read for any strategist. Sun Tzu: The Art of War In this book in thirteen chapters an explanation is given how the context of warfare an be defined.


The combination of leadership, environment and goal makes each war different. I think therefore there is a similarity between warfare and software testing. In software testing you also have different objectives, circumstances and resources.

Test approach
When looking at the thirteen chapters of The art of War there is some similarity which can be translated to testing. I tried to visualize it in the image below.
Similarity between warfare and software testing
Is there a similarity between warfare and software testing?
Perhaps there is, in both situations:
- The environment and goal has impact on the type of execution and leadership
- The chance for creating chaos is high
- Dealing with chaos should be part of the strategy
- The desired outcome is victory, only at the end you know about failure
- Best practices is not a guarantee for success, it depends, and most of the time on the context.

Tuesday, March 17, 2009

TestData Generator

A colleague tester pointed me recently about the importance of test data management and the recently offered site towards test data management: Testdata Management.

Behind one of his links there was a free test data generator: GenerateData.com
GenerateData.com offering a free test data generation tool with several functions to generate "standard" test data in several formats: HTML, MS Excel, XML, CSV and SQL.

Next to generate data online you have to ability to download the script which is under GNU open Source License.

I have to admit that this tool is easy to use although I think you have still to manipulate the data for your own use.

This triggers me to search for more opensource generation tools related to testing. A new world opened in front of my eyes, :)

Here some other open source tools:
dbmonster : can be used for DB tuning
benerator: performing load and performance tests
Database populator : Examines the table and populate it according to it (note: downloadable version is from 2004)

These seems somehow promising, perhaps in the nearby future I can try them sometimes.

Monday, March 16, 2009

All those fine test methods and approaches

There are people who think software testing is easy. There are testers who claiming to be experts in the testing area. There are companies who believe their tool is the solution for everything. There are program managers who know that mentioning a method in a plan and using templates solve all problems. There are developers who are able to use development methods as they were intended to do.

I cannot not believe we live in a world this beautiful. I'm a tester and somehow I'm an expert. In certain areas in certain conditions I know more about software testing then others. And still I'm eager to learn. This is one of my main goals. I like software testing as an occupation and as a way of thinking.

Only I believe this world is not that beautiful as it is. And we all know it. Most of the people are claiming that their methods, approaches and tools are just the way we have to work and then all problems will be solved. There are testers who work according those methods and are forcing organizations to change otherwise they are not able to do their job. They forgot that a method or approach is just a tool to help and can and should never be used as it is written on paper.

How often did you hear or did you mention that we should do this because it is: ITIL, CMMi, TMMi, Prince2, TMap, ISTQB, Agile, RUP, or whatever method/approach/ best practice? How often did you ask yourselves if it values the method or the organization?

As methods are often models how to handle things. A model is just a representation of the actual world. Models are fallible and therefore methods too. Using those methods as written makes you fallible.

Fortunately, because of human nature we are trying to avoid being fallible and we are striving for success. Preventing fallibility we adapt. We adapt our vision about methods and adjust our approaches. By doing this we have to be aware that we change the chosen methods/approach which supports the organization.

This is what makes software testing interesting for me; finding solutions under given circumstances reflecting against organizational defined methods and models using the boundaries of those methods/approaches/tools/best practices to provide information about risks and benefits for the organization when rules are broken.

Therefore software testing is not easy and we are not experts and there is not one solution. Testing is fun and should be done by people having expertise and gaining knowledge, able to adapt and having the courage to think out of the box, within the context. Testers should use their knowledge about methods etc. to value organizations instead of preaching their knowledge of a method or tool is the best solution.

Sunday, March 15, 2009

Pretending to be green and not explicitly measuring it

Last year I already introduced on my blog "Ecoliability" as a potential new quality attribute. I still believe this quality attribute can be of use to explicitly measure how "Green" a company or software is.

On CeBIT green IT a entire hall was dedicated to innovations related to energy saving solutions in the IT-world. Looking at this site it seems those solutions are for a wide scale of potions, from efficient usage of processor time through cloud-computing or SaaS till hard ware solutions to save energy.

If organizations pretending or intending to be green; why not explicitly measure this? Most of the software testers like to talk about quality attributes when they need to test something. It is common knowledge that if certain quality attributes getting more attention in projects it have a positive influence on some attributes and a negative influence on others. For example increasing functionality could have positive effects on usability and efficiency only the sustainability and portability might be lesser.

Management make decisions on those effects. If this is so important for management to decide what to choose based on the impact on certain quality attributes this new quality attribute "Ecoliability" can also be of use and must be introduced.

If we start using this quality attribute it can help management to decide if they accept the costs on other attributes for being "Green" or forcing projects to look for other solutions. If being "Green" is a management decision based on a company’s vision we should help them making it measurable and therefore visible.

If you are "Green" you might think about this and start discussions about this new attribute.

Monday, February 23, 2009

Do you change your testing strategies?

Just out of curiosity I'm wondering if you change your testing strategy. Is there room for change? Are you willing to change? Are your brave enough to change?

Deliberately I'm not asking for the need for change. Because of the current recession I think there is an urgent need to change. The question is what should be changed?

In many projects, people are working with proven technologies and methods. Some of the methods are very useful to cover all risks and measure the quality proved by those methods. Some methods are useful as they rely on best practices. Some methods are necessary as organizations are forcing to use those kinds of project management methods.

In all cases those methods are used to solve problems for organizations. I'm just wondering if there is time enough to keep using those solid methods. Is there budget enough to measure all quality? Are resources and skills available to make it a success using those methods?

Perhaps it is time to change. With change I'm more thinking of a context driven test approach as James Bach, Cem Kaner, Michael Bolton and others are suggesting. If I understood that approach good enough the basis of that approach is defining the context first instead of defining the framework for the project first and the "proven" test method.

When thinking about the context and considering the time we live in now we might understand that resources are not available to make it a success. Because of a clear context decisions can be made to accept risks.

Under current conditions risks have to be taken. Accepting risks might lead to new opportunities since the focus is just there were the organization sees it challenges, opportunities and problems which have to be solved.

I'm just curious:
- Do you dare?
- Do you care?
- Do you have enough resources, budget and skills to continue as you did in the past?
- Or do you change?