One of the teams that I am currently working with is using agile practices. First of all, let me put out my definition of this. The word practice, as I view it more often than not, is "repeated performance or systematic exercise for the purpose of acquiring skill or proficiency" (Dictionary.com). So, regardless of the definition of agile being used, and regardless of the connotations this word has... the key, to me, is practice.
One of the first things that I took notice of was the conditions of the team. A couple of us had worked together, but most had not. Because of this, the condition of the team was that of a new team. A new team generally goes through the Forming-Storming-Norming-Performing model. However there seems to be a big difference in the way these stages of the model are approached when each of the team members is geared more towards the overall success of the project and not in a competitive mode.
One obvious thing that makes a team have an easier time to get to the Performing stage is communication. A noticable benefit of working with a team that is using agile practices is the amount of communication that takes place. This can often start out a bit awkward for the team, who may not be used to talking about what they are doing, but as the practice continues, the communication becomes more open and beneficial to the team and the project.
Another benefit of being on this type of team is that there are no real defined practices. We have the added advantage of creating our own way - and changing it when/if it needs to change. It is freedom with responsibility. Allowing the team to be individually creative while the whole group keeps each other on task toward the goal.
The word practice can incite a lot of different feelings depending upon the context that it is used in. I personally like the word because it inspires me to continue to learn and grow, while allowing me the freedom to try things out and see if they fit - which grants me permission to fail on occassion. While this is not what I hope/expect the outcome to be, it is necessary to be permitted to have some failures along the road to success, otherwise nothing would ever improve personally or professionally.
One pretty good example of the inspiration of the word practice that I find helpful is when it is used in conjunction with medicine. Doctors are referred to as Practicing Medicine. Their offices are referred to as Practices. Now, while this would not sound good to the ears of a person in need of diagnosis/repair/surgery/etc; without the continual practice of medicine we would not have the life expectancy that we have as humans... not to mention how horrible it would be to go and visit a doctor.
To me, while we often seek to have best overall practices, it is more important to remember to aim for the definition of acquiring skills and proficiency in what we are doing at this time and on this project, taking into account that the same skills and proficiency may not be of benefit on the next project, challenging us to grow our skills.
Sunday, July 12, 2009
Thursday, July 9, 2009
Continued Success... Requirements
I first heard of Richard St. John by Simon Godfrey when he posted a comment on one of my earlier blog posts. I have since decided to continue to explore the world of TED myself, since this is where the link was originally posted.
It was during this morning's visit to the web site that I found another podcast from Richard entitled Success is a Continuous Journey. A 3 minute 58 second talk about how it is vital to continue to have:
Passion
Work
Focus
Push
Ideas
Improve
Serve
Persist
The 8 Secrets of Success need not end when we reach a level where we feel comfortable. There should never be a level we reach where we feel this apathy toward growth. The same is true in every endeavor in our lives.
For example, I like to garden. I like to plant life in the soil and watch it grow. However if I feel that I have done enough, do not check water or weeds, what will happen to my garden? Will the healthy plants be choked out by the weeds? Will the plants die for lack of water?
How about relationships? Do they not need tending the same way? What happens when the passion fails here? Or when the desire to meet any of the "8 Secrets to Success" burns out? Does the relationship survive?
The same is true for a career in software testing. The "other half" of the relationship continues to need the "8 Secrets" in order to continue to prosper. It is very important to keep these close to heart in all aspects of life... for balance, for health, for success.
It was during this morning's visit to the web site that I found another podcast from Richard entitled Success is a Continuous Journey. A 3 minute 58 second talk about how it is vital to continue to have:
Passion
Work
Focus
Push
Ideas
Improve
Serve
Persist
The 8 Secrets of Success need not end when we reach a level where we feel comfortable. There should never be a level we reach where we feel this apathy toward growth. The same is true in every endeavor in our lives.
For example, I like to garden. I like to plant life in the soil and watch it grow. However if I feel that I have done enough, do not check water or weeds, what will happen to my garden? Will the healthy plants be choked out by the weeds? Will the plants die for lack of water?
How about relationships? Do they not need tending the same way? What happens when the passion fails here? Or when the desire to meet any of the "8 Secrets to Success" burns out? Does the relationship survive?
The same is true for a career in software testing. The "other half" of the relationship continues to need the "8 Secrets" in order to continue to prosper. It is very important to keep these close to heart in all aspects of life... for balance, for health, for success.
Tuesday, June 23, 2009
Walk through testing....
Do you walk? What is the purpose of your walk?
Excersizing?
Getting from point A to point B?
Stretching out between test sessions?
Getting to that extra peice of pie before someone else does?
I walk for several reasons every day. In the early morning, I walk my dog. This walk has two purposes. 1. To train my 5 month old German Shepherd to walk correctly on a leash. 2. To excersize.
I walk to and fro in the house in order to get things in order and prepare for the day.
I walk to and from my car in order to get to work, or to run errands.
I walk to and from different offices in order to get information when necessary, or to go to meetings when they are scheduled.
I walk in the back trails to see what latest wild flowers are in bloom, and maybe to cut a few for an at home display.
The purpose of my walk/journey is what determines the pace that I walk. It determines the energy that I expel. The plan and the purpose determines the journey.
The same is true for testing. What is the purpose of my testing? What has changed in the product/application/system? What is the timeline allowance for my testing? What are the stakeholder expectations?
Just like you determine how fast and how far you intend on walking, using the purpose of your walk as a guide, so also you determine your testing strategy.... And, yes, there is always that unexpected car-breakdown that causes you to have to push it all into overdrive for a little while, but doesn't that add color to the whole story of your life? What fun would be missed out on if there were no "stories" to tell :)
Excersizing?
Getting from point A to point B?
Stretching out between test sessions?
Getting to that extra peice of pie before someone else does?
I walk for several reasons every day. In the early morning, I walk my dog. This walk has two purposes. 1. To train my 5 month old German Shepherd to walk correctly on a leash. 2. To excersize.
I walk to and fro in the house in order to get things in order and prepare for the day.
I walk to and from my car in order to get to work, or to run errands.
I walk to and from different offices in order to get information when necessary, or to go to meetings when they are scheduled.
I walk in the back trails to see what latest wild flowers are in bloom, and maybe to cut a few for an at home display.
The purpose of my walk/journey is what determines the pace that I walk. It determines the energy that I expel. The plan and the purpose determines the journey.
The same is true for testing. What is the purpose of my testing? What has changed in the product/application/system? What is the timeline allowance for my testing? What are the stakeholder expectations?
Just like you determine how fast and how far you intend on walking, using the purpose of your walk as a guide, so also you determine your testing strategy.... And, yes, there is always that unexpected car-breakdown that causes you to have to push it all into overdrive for a little while, but doesn't that add color to the whole story of your life? What fun would be missed out on if there were no "stories" to tell :)
Sunday, June 21, 2009
"Adaptive Toolbox" for Testing
During a recent look into decision making processes, I came in contact with what is referred to as bounded rationality. This study led me to find the book "Bounded Rationality: The Adaptive Toolbox".
The book is put together with papers submitted by several contributors. The fascinating thing about the papers is how much they line up with decisions that software testers make every day on the job.
The "adaptive toolbox" of bounded rationality "provides heuristics, and these are composed of building blocks. I describe three functions these building blocks have: they give a search direction, stop search, and make a decision." Sound familiar?
How am I going to test this application/product/system?
When do I stop testing?
Are we 'done'?
One of the focus points of the concept of bounded rationality is the use of a simple heuristic versus attempts to optimize (optimization is impossible in testing... and just about everything else).
"First, contrary to conventional wisdom, limitations of knowledge and computational capability need not be a disadvantage. The heuristic tools of humans, animals, and institutions can be simple, but nevertheless effective in a given environment.... Simplicity, by contrast, can enable fast, frugal, and accurate decisions."
I find this book is well worth having on hand for thinking about my own "Adaptive Toolbox" for Testing.
The book is put together with papers submitted by several contributors. The fascinating thing about the papers is how much they line up with decisions that software testers make every day on the job.
The "adaptive toolbox" of bounded rationality "provides heuristics, and these are composed of building blocks. I describe three functions these building blocks have: they give a search direction, stop search, and make a decision." Sound familiar?
How am I going to test this application/product/system?
When do I stop testing?
Are we 'done'?
One of the focus points of the concept of bounded rationality is the use of a simple heuristic versus attempts to optimize (optimization is impossible in testing... and just about everything else).
"First, contrary to conventional wisdom, limitations of knowledge and computational capability need not be a disadvantage. The heuristic tools of humans, animals, and institutions can be simple, but nevertheless effective in a given environment.... Simplicity, by contrast, can enable fast, frugal, and accurate decisions."
I find this book is well worth having on hand for thinking about my own "Adaptive Toolbox" for Testing.
Tuesday, June 16, 2009
How do you respond to Change?
"It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change." (Author Unknown)
Matt Heusser's latest blog entry The Boutique Tester points out some very interesting possibilities for the future of software testing.
Rosie Sherry over at the Software Testing Club has started a Flash Mob Testing group.
James Bach's latest blog entry is about remote testers.
Response to change is a common thread between these three test leaders. Let me further explain.
The recent economic changes have forced businesses and customers alike to begin to quantify every dime they spend, while the demand for value has not decreased. Technology has evolved to where Virtual teams are more and more common, and this same technology continues to evolve.
Change is a constant fact of life. Everything from age to weather proves this to be the case... visibly. How we face changes determines how we progress and where we end up. We do not have to give all the power of change over to someone else. If we don't look towards the future and define our role, someone else will determine it for us. Personally, I prefer the freedom to creatively define my role, based on the knowledge of my own strengths and weaknesses in order to give the best value I can to the stakeholders.
Software testers are always in the midst of changes, this challenge is one reason I love testing, it eliminates the possibility of boredom. Testing is not a nine to five job, it is an adventure. It requires constant forward thinking. My personal favorite statement from the Agile Manifesto is "Responding to change over following a plan". It goes beyond software development and is a life lesson.
I challenge you to think about the word "Change" today. How do you feel when you hear the word? What do you think about? How do you respond to it?
I challenge you to read the blogs linked here and think about the ideas expressed in them. What do you think about the future of software testing? Have you begun to define your role for the future? Or will you wait for someone else to do so?
Matt Heusser's latest blog entry The Boutique Tester points out some very interesting possibilities for the future of software testing.
Rosie Sherry over at the Software Testing Club has started a Flash Mob Testing group.
James Bach's latest blog entry is about remote testers.
Response to change is a common thread between these three test leaders. Let me further explain.
The recent economic changes have forced businesses and customers alike to begin to quantify every dime they spend, while the demand for value has not decreased. Technology has evolved to where Virtual teams are more and more common, and this same technology continues to evolve.
Change is a constant fact of life. Everything from age to weather proves this to be the case... visibly. How we face changes determines how we progress and where we end up. We do not have to give all the power of change over to someone else. If we don't look towards the future and define our role, someone else will determine it for us. Personally, I prefer the freedom to creatively define my role, based on the knowledge of my own strengths and weaknesses in order to give the best value I can to the stakeholders.
Software testers are always in the midst of changes, this challenge is one reason I love testing, it eliminates the possibility of boredom. Testing is not a nine to five job, it is an adventure. It requires constant forward thinking. My personal favorite statement from the Agile Manifesto is "Responding to change over following a plan". It goes beyond software development and is a life lesson.
I challenge you to think about the word "Change" today. How do you feel when you hear the word? What do you think about? How do you respond to it?
I challenge you to read the blogs linked here and think about the ideas expressed in them. What do you think about the future of software testing? Have you begun to define your role for the future? Or will you wait for someone else to do so?
Thursday, June 4, 2009
Certifiable Testers....
How do you know you are a certifiable tester?
Ha ha ha... you think I am talking about certification, that is why you clicked on the link to this blog to begin with. Think again. In fact, just think while I tell you a story...
A few months ago I was asked if I would like to join a new team. Because of the normal business protocols of not saying anything at all about it, I will not be able to divulge any of the facts, but I will tell you one thing.... After a few "OMG's" and nearly jumping out of my seat to hug my manager (not a good idea), I cried and said, "now I know what Miss America feels like when she gets the crown!"
To me, the biggest thing that a tester can bring to the table and offer the stakeholders of any project she... or he... is on, is passion. Passion to test, passion to learn, passion to communicate, passion to see a project through to success. Without this passion, there is not much to offer.
The general public would find this response to be a bit much. After all, isn't a job a job? Aren't we just trying to earn a living and get by? Working for the weekend? Writing test cases, demanding we be heard?
I think not. Wherever your passion lies, there is where you should be. Are you hoping to be a programmer? A manager? A better tester? Don't wait for opportunities to become better, make those opportunities happen. After the 40 +/- work week is over study your desire, learn it, make it your own. Passion for something is not just a desire, it is a habit. A habitual need to become what you feel you want to be, or to find your own niche in the place where you are.
Dictionary.com has the word "certifiable" defined in the number 4 reference as "uncontrollable". Do you have an "uncontrollable" desire to be your best? If so, then you are passionate about what you do. If so, you are a certifiable tester.... Kudos to you!
Ha ha ha... you think I am talking about certification, that is why you clicked on the link to this blog to begin with. Think again. In fact, just think while I tell you a story...
A few months ago I was asked if I would like to join a new team. Because of the normal business protocols of not saying anything at all about it, I will not be able to divulge any of the facts, but I will tell you one thing.... After a few "OMG's" and nearly jumping out of my seat to hug my manager (not a good idea), I cried and said, "now I know what Miss America feels like when she gets the crown!"
To me, the biggest thing that a tester can bring to the table and offer the stakeholders of any project she... or he... is on, is passion. Passion to test, passion to learn, passion to communicate, passion to see a project through to success. Without this passion, there is not much to offer.
The general public would find this response to be a bit much. After all, isn't a job a job? Aren't we just trying to earn a living and get by? Working for the weekend? Writing test cases, demanding we be heard?
I think not. Wherever your passion lies, there is where you should be. Are you hoping to be a programmer? A manager? A better tester? Don't wait for opportunities to become better, make those opportunities happen. After the 40 +/- work week is over study your desire, learn it, make it your own. Passion for something is not just a desire, it is a habit. A habitual need to become what you feel you want to be, or to find your own niche in the place where you are.
Dictionary.com has the word "certifiable" defined in the number 4 reference as "uncontrollable". Do you have an "uncontrollable" desire to be your best? If so, then you are passionate about what you do. If so, you are a certifiable tester.... Kudos to you!
Thursday, May 28, 2009
Question Everything.... On Purpose
THIS FINISHED PRODUCT IS NOT TESTED ON ANIMALS.
What does that mean? Talk about ambiguous. I have several questions for the maker of the body wash this statement, in all caps, was written on:
1. Was the unfinished product tested on animals?
2. What does "on animals" mean? A microscope on an animals back? Was an animal washed in the "unfinished" product?
3. Will my dog be allergic to the "finished" product?
4. If I cannot wash my "animal" with the product, is it safe for me to wash myself with it?
5. What type of "testing" are you talking about?
6. Does "is not" mean "never was"?
7. Who or what did you test the "finished product" on? And, did they or it live?
Now, wasn't that a fun two-minute examination of documentation? Find something that is "simply accepted" to ask questions about today. Question everything... and smile while you do it because you know how much it irks others ;-)
What does that mean? Talk about ambiguous. I have several questions for the maker of the body wash this statement, in all caps, was written on:
1. Was the unfinished product tested on animals?
2. What does "on animals" mean? A microscope on an animals back? Was an animal washed in the "unfinished" product?
3. Will my dog be allergic to the "finished" product?
4. If I cannot wash my "animal" with the product, is it safe for me to wash myself with it?
5. What type of "testing" are you talking about?
6. Does "is not" mean "never was"?
7. Who or what did you test the "finished product" on? And, did they or it live?
Now, wasn't that a fun two-minute examination of documentation? Find something that is "simply accepted" to ask questions about today. Question everything... and smile while you do it because you know how much it irks others ;-)
Subscribe to:
Posts (Atom)
