“Powerful Project Leadership Skills” Course – Coming to Calgary!

I am excited to share that Quality Perspectives and Unimagined Testing are offering the Powerful Project Leadership Skills course instructed by industry recognized leadership consultants Wayne and Eileen Strider. Wayne and Eileen each have over 30 years IT experience including over 20 years experience with the Virginia Satir Growth Model. This three day course will be offered in Calgary on April 23-25, 2012.

Course Overview

You are an experienced information technology professional. Regardless of your position, role or title, you may find yourself managing projects. You know the mechanics of project management—initiating, planning, scheduling, staffing, executing, monitoring, controlling, and closing projects. Now you want to strengthen your leadership skills—skills that enable you to work effectively with customers, bosses, peers, staff, and vendors as well as help them work effectively with one another.

This workshop will help you balance your needs and expectations as a leader, the needs and expectations of other project individuals, and the realities of your project’s context. This workshop addresses directly human relationship situations that can put your project at risk—when stresses emerge, tempers flare, and uncertainties and self-doubts arise.

Adapted from the book Powerful Project Leadership by Wayne Strider, this workshop can benefit anyone whose work involves managing relationships among project team members, sponsors, committees, functional users, customers and vendors.

For more details on the Powerful Project Leadership Skills course, please see our PPLS Course Details page.

Registration
Early bird registration of $1625 per person will be offered to Satir Global Network members and $1699 to non-members until January 31, 2012. Starting February 1st registrations will be $1925 per person for Satir Global Network members and $1999 to non-AST members.

Fees include training materials, lunch and refreshments. Participants will also receive a copy of the Powerful Project Leadership book. Please note there is a maximum of 28 spots available.

Dates Location Registration Fees
April 23-25, 2012 Calgary, AB Canada
The Kahanoff Centre
Suite 200, 1202 Centre St SE
www.kahanoffconference.com
Early Bird Registration (Until January 31st)

  • $1625 for Satir Global Network Members
  • $1699 for Non-Members

Registration (Starting February 1st)

  • $1925 for Satir Global Network Members
  • $1999 for Non-Members

Register Now »

For more information on becoming a member of the Satir Global Network, please visit http://satirglobal.org/about/donate-to-support-this-site/membership/.

Do not miss this great opportunity! We look forward to seeing you at the course. Should you have any questions or concerns, please contact us.

Testers in New Orleans!

The Software Test Professionals Spring 2012 conference is looking for submissions. Next year’s conference will be held in New Orleans, LA. from March 26 – 29.

If you are interested in submitting check out their conference submission form here.

Hope to see you there!

Lather, Rinse, and Repeat

Lather, Rinse, RepeatHave you ever closely looked at your shampoo bottle? I recently looked at mine and noticed it came with directions for use. The directions said “Lather, rinse and repeat”. These directions made me chuckle because I have seen many testers use the “lather, rinse and repeat” technique when testing.

Albert Einstein once said “Insanity is doing the same thing over and over again and expecting different results”. This insanity also applies to test execution. Organizations who instruct their testers to run the same suite of test cases over and over again, release after release should not expect to find different results.  Sure, sometimes we do, such as in the case where a code change caused something to break. However, discovering new issues lurking in our software that have existed for sometime will not likely be discovered in this fashion. If they could, they would have already been found on one of the many previous cycles of execution.

That’s why each time we approach testing, we need to change our behaviour and interaction with the system. You may need to test the same areas in the same fashion but challenge yourself to come up with new approaches to see how you could test these same areas differently. What different approach, steps, method, etc could you use that you have not used before.

Most importantly, have fun when trying new approaches. Enjoy changing up your testing and the discovery of new information about yourself and your system.  Not only will you appreciate the break from the monotony, you will also significantly reduce the risk of driving yourself insane!

Woodchucks and Test Estimation

Recently I was reminded of an old tongue twister during a conversation about test estimation. Once again I had heard the question asked to a tester “How much time do you need for testing?”. To me that question practically the same as asking – “How much wood would a woodchuck chuck if a woodchuck could chuck wood?”  Let’s break it down to illustrate.

How muchThe statement “How Much” begs a number of questions:

  • How will we measure “how much” is it by weight, size of the pile, height of the pile, number of pieces, or size of the individual pieces.
  • Perhaps there is a less quantifiable metric we are ‘measuring’ against such as “when the individual who requested wood chucking is happy or satisfied with the results?”
  • Is there a quality concern that would deem some of the wood chucked to be not included in this measurement. Could we have poorly chucked wood that wouldn’t count? Or alternatively would wood chucked in a high quality manner count for more towards this final measurement?

How much woodWhat exactly do we mean by “wood”? Wikipedia defines wood as a “hard, fibrous tissue found in many plants.” The definition continues to say ” wood can be used for fuel or construction. Wood may also refer to other plant materials with comparable properties, and to material engineered from wood, or wood chips or fiber.” So what exactly is our woodchuck chucking?

  • What is the purpose of the wood we are chucking?
  • Does the wood need to meet a certain criteria? Size, type?
  • Are we talking treated wood, recycled wood, unfinished, finished, MDF, oak, pine, cherry, you get the picture?

So when we don’t know what we are chucking, how can we know how much? This adds even more complexity to the question.

How much wood would a woodchuck… Let’s closer examine our hard working little wood chucker the woodchuck. A woodchuck is also known more commonly as a groundhog. (Well who knew!) Woodchucks are a lowland creatures who are found in North America as far north as Alaska and as far south as Alabama. If you have never seen one they are a small creature between 16 – 26 inches long and weighing between 4 – 9 lbs. Not a very big size to be chucking a lot of wood. You also need to consider:

  • Woodchucks hibernate during the winter months. So depending on when the woodchucking is occurring he may not be chucking any at all since he would be sleeping.
  • Once a year woodchucks have a moral duty on Groundhog Day to leave their borrows to check for their shadow and determine if winter will end early or continue for 6 more weeks. Clearly they can’t be chucking wood on such an important day. If winter is extended for 6 more weeks, you will further reduce the available for woodchucking.
  • In the wild woodchucks only live on average 2 – 3 years.  However, in captivity woodchucks can live from 9 – 14 years. Depending on which woodchuck (wild or domestic) is performing the chucking you may have only a year to get said job completed.
  • Woodchucks are aggressive by nature. You may have some personnel issues to deal with in order to get the woodchucking job done.
  • Common predators for woodchucks include wolves, coyotes, foxes, bobcats, bears, large hawks, owls, and dogs. When threaten they retreat to their burrows to hide. You’ll need to invest in some protection of your little wood chucker in order to keep him safe and on task.

How much wood would a woodchuck chuck… The word “chuck” when used as a verb means, “to toss; throw with a quick motion, usually a short distance”.  It also has various other meanings however, I believe in this example this definition is the most fitting. Again additional questions come to mind:

  • Is there a certain preferred chucking technique that our woodchuck must use to perform the wood chucking?
  • Is there a distance requirement that needs to be met in order for the chuck to count?

How much wood would a woodchuck chuck if… My grade school grammar (and the Internet) taught me that in this sentence the word “if” is a conjunction. Its meaning in this sentence could be replaced with “when” or “whenever”. Which could mean that woodchucks can indeed chuck wood. So we could alternatively ask, “How much would would a woodchuck chuck WHEN a woodchuck would chuck wood?” In this case woodchucks can chuck wood if they decide to do so. Now we could use past examples of wood chucking woodchucks to determine how much wood a woodchuck could chuck. (Much like we try to do with past software projects and test estimation). However, still more questions:

  • How accurate is it to compare two woodchucks’ woodchucking ability? If one can chuck a certain quantity of wood, does that mean another should be able to chuck the same? How similar do two woodchucks need to be before we can compare one to another?
  • Are the conditions under in which one woodchuck is woodchucking wood the same conditions as when another woodchuck is woodchucking wood?
  • Are the requirements the same for woodchucking the same for both woodchucking woodchucks?

How much wood would a woodchuck chuck if a woodchuck could chuck wood?… The word could in this sentence leaves me a little concerned. There is some potential risk that even if we found a woodchuck large enough and who was motivated enough to chuck wood he still may not be able to for any number of reasons.

As silly as this question about woodchucks is, there are a number of parallels that can be made to software testing. In our test estimations we face a number of the same questions and concerns listed above and often end up with more questions than answers. For me the biggest challenge isn’t coming up with a test estimate that I know will change, its easy for me to make up any number. Instead the challenge is getting my stakeholders or project manager to understand the complexity of testing.

    So when you are next asked for your test estimate just take a deep breath and think “if I were a woodchuck…..”.

    CAST 2011 Challenge

    Last year I posted a challenge to everyone to find 5 new people to attend CAST 2011. At the conferences I have attended this year I have told a number of people about CAST and encouraged them to attend. Next week at the conference I am hoping to once again reconnect with a few of these people and see how many stepped up to the challenge!

    CAST 2011 promises to be another great conference. There are a number of outstanding presentations scheduled which I am excited to be helping facilitate. You can check out the entire CAST schedule here.

    If you haven’t yet registered for CAST, what are you waiting for? There is still time to be part of this great conference that encourages discussion and interactive, hands-on learning. Register today!