Showing posts with label community. Show all posts
Showing posts with label community. Show all posts

Tuesday, October 15, 2024

Scaling Tech Work While Maintaining Quality: Why Community is the Key with Katherine Payson (a PNSQC Live Blog)

If someone had told me ten years ago I'd be an active member of the "gig economy" I would have thought they were crazy (and maybe looked at them quizzically because I wouldn't entirely understand what that actually meant. in 2024? Oh, I understand it, way more than I may have ever wanted to (LOL!). Rather than. looking at this as a bad thing, I'm going to "Shift Out" (as Jon Bach suggested in the last talk) and consider some aspects of the gig economy that are helping to build and scale work and, dare we say it, quality initiatives. 

Katherine Payson offers some interesting perspectives:

- The gig economy generates $204 billion globally
- many companies are leveraging and taking advantage of this, including international companies hiring all over the world for specific needs (I know, I did exactly this during 2024)
- In 2023, the anticipated growth rate for gig work was expected to be 17%
- By 2027 the United States is expected to have more gig workers than traditional full-time employees

This brings up an interesting question... with more people involved in gig work, and not necessarily tied to or beholden to a company for any meaningful reasons, how do these initiatives scale, and how do quality and integrity apply?

Strong Community is the approach that Katherine is using and experiencing over at Cobalt, a company that specializes in "pentesting-as-a-service". Cobalt has grown its pool of freelance tech workers to over 400 in three years. That's a lot of people in non-traditional employment roles. So what does that mean? How is trust maintained? How is quality maintained? Ultimately, as Katherine says, it comes down to effective "Community Building".

Today, many businesses are looking for specialized skills, frequently beyond what traditional full-time employees and employment can do. Yes, AI is part of this shift but there is still a significant need for human expertise. As Cobalt points out, cybersecurity, software development, and other technical fields definitely still require human employees with a very human element to them. What this means is that there is a large rise in freelance professionals actively offering niche talents on a flexible, on-demand basis (likely also on an as-needed basis both for the companies and the gig workers themselves). Again, the bigger question is "Why should a gig worker really care about what a company wants or needs?"

Community can be fostered directly when everyone is in the same town, working on the same street, going to the same office. When Cobalt first began scaling, they relied on a traditional trust model that worked well for a smaller, more centralized team. As the number of freelancers grew, however, this model began to show its limitations. Without a more robust system in place, it would be impossible to ensure consistent quality across a distributed workforce.


Tools can go a certain distance when it comes to helping manage quality and production integrity but more to the point, developing actual communities within organizations is another method for helping develop quality initiatives that resonate with people from all involvements in their organizations.

Cobalt prides itself as a company that is able to maintain quality at scale. It claims to create a culture where freelancers feel connected, supported, and motivated to deliver their best work. So how does Cobalt do that?

Collaboration and Communication: Freelancers can work independently, but they don't work in isolation. Cobalt believes in open communication, where freelancers can collaborate with one another, share knowledge, and learn from each other’s experiences.

Mentorship and Professional Development: Cobalt invests in the professional growth of freelancers. Mentorship opportunities, training programs, and access to industry resources help their freelance community continuously hone their skills.

Recognition and Incentives: High-performing freelancers are recognized and rewarded for their contributions. This helps retain top talent and encourages others to aim for top-quality work.

Feedback Loop: Freelancers receive regular feedback on their work, helping them improve and keep quality high across the board.

As the gig economy continues to grow, maintaining quality at scale will become increasingly important everywhere. Cobalt aims to embrace the strengths of their freelance workforce, not just as individual contributors but as part of a larger community. Scaling with freelancers is not just about hiring more people—it’s about building a culture of collaboration, growth, and trust. To ensure quality remains front and center, companies need to invest in their communities every bit as much as much as they do in their tools and processes.

Tuesday, October 9, 2018

Talking About Quality - a #PNSQC Live Blog


Kathleen Iberle is covering a topic dear to my heart at the moment. As I'm going through an acquisition digestion (the second one, my little company was acquired and that acquiring company has recently been acquired) I am discovering that words we are used to and the way that we defined quality is not necessarily exactly in line with the new acquiring company. Please note, that's not a criticism, it's a reality and I'm sure lots of organizations face the same thing.

In many ways, there are lots of conversations we could be having and at times there are implicit requirements that we are not even aware of the fact that we require. I consider that an outside dependency where, if I don't know I need to do something, I can't do it until I get the knowledge that needs to be given to me so I can act on it. There's a flip side to this as well. That is the implicit requirement where there's something I do all the time, so much that I don't even think about it, but someone else has to replicate what I am doing. If I can't communicate to them the fact that there is a step they need to do because of me literally jumping through it so fast that I don't notate it, can I really be mad when someone doesn't know how to do that step?

Many of us are familiar with the idea of SMART Goals, i.e. Specific, Measurable, Achievable, Relevant and Time-based.  This philosophy also helps us communicate requirements and needs for products. Taking the time to make sure that our goals and our stories take into account whether or not they add up to the SMART goal model is a good investment in time.

An interesting distinction that Kathleen is making is the differentiation between a defect and technical debt. A defect is a failure of quality outside of the organization (i.e. the customer sees the issues). Technical debt is a failure of quality internal to the team (which may become a defect if it gets out in the wild).

An approach that hearkens back to older waterfall testing models (think the classic V model) is the idea of each phase of development and testing having a specific gate at each point in the process. Those gates can either be ignored (or have them only used at the very end of the process) or they are given too large an amount of attention out of cope or context for the phase in question. Breaking up stories into smaller atomic elements can help improve this process because the time from initial code to delivery might (can) be very short. using terms like "Acceptance Test", "Definition of Done", "Spike", "Standard Practice", etc. can help us nail down what we are looking at and when. I have often used the term "Consistency" when looking at possible issues or trouble areas.

Spikes are valuable opportunities to gain information and to also determine if there is an objective way to determine the quality of an element or a process. They are also great ways to be able to determine if we might be able to tool up or gain skills that we don't have or need more abilities with to be effective.


Friday, August 17, 2018

The Testing Show - Conferences and Conferring with Anna Royzman, Claire Moss and Mike Lyles

I have been terrible with my shameless self-promotion as of late, but I think it's time I switch that up a bit. Remember my comment about that "grind" earlier in the week? Here's the end result and yes, I always feel better about it after it's all said and done because I enjoy seeing the end product and most importantly sharing it with everyone out there.



I have a little favor to ask as well if you are so inclined. Do you enjoy listening to The Testing Show? If you do, could I ask you to go to Apple Podcasts and write us a review? Reviews help people find the podcast and make it more likely to appear in the feed listings. Seriously, we all would really appreciate it. We work hard to bring these out and I'd love nothing better than to have more people be able to find it.



In any event, we hope you enjoy this month's episode. To set things up, here's the lead in for the show:

August is a busy time of year for software testing conferences (not to mention conferences in other industries). This month, we decided that, with everyone heading off to conferences hither and yon that we would dedicate a show to the topic, and we have done exactly that. Anna Royzman (Test Masters Academy), Claire Moss (DevOpsDays) and Mike Lyles (Software Test Professionals) join us as guests in their capacity as conference organizers, speakers and attendees (not necessarily in that order) to riff on Conferences and Conferring with Matthew Heusser, Michael Larsen, and Perez Ababa. Want to know where to go, what format to take part in or if you want to try your hand at speaking/presenting? We’ve got something for all those bases!

The Testing Show - Conferences and Conferring with Anna Royzman, Claire Moss and Mike Lyles: The Testing Show team discusses the QA conference season with Anna Royzman, Claire Moss and Mike Lyles. Tune in to learn more!


Wednesday, August 23, 2017

Regarding Comments and Interaction on TESTHEAD

As I've been going through the site to determine changes I want to make regarding Accessibility and Inclusive Design, I've been doing a review of past posts (with more than 1,000, this is taking awhile, but I'm getting there). In the process, I've also noticed a recent uptick in comments. At first, I was excited, but quickly saw that most of them tended to be the same:


nice blog has been shared by you. before i read this blog i didn't have any knowledge about this but now i got some knowledge. so keep on sharing such kind of an interesting blogs.

This would then be followed by a link to some other site, usually offering training of some kind.

At first, I tended to approach this with a bit of a buzzsaw approach, just deleting them out of hand, but during CAST, I talked to a friend and colleague and described my frustration with this approach. They suggested something I hadn't considered. It may be SPAM. It probably is SPAM if it is linking to a commercial link, but there is a possibility that this is also a new student fulfilling a class assignment to find a technical blog, read a post and comment on it.

Fact is, I don't know, but the better, possibly more naive part of me wants to believe that some of this traffic might be legitimate, so I'm going to make a few requests.

1. If you read something that you appreciate, let me know specifically what you like about the post. That at least gives me an indication that you have read it.

2. Ask me a question about the post. This may be a mild psych thing with me, and I may regret admitting this down the road, but I'm the type of person that, if you ask me a question in social media or via blog posts, I feel compelled to answer. My answer may be "I don't know" or "I'd have to point you to [x]" but I will answer :).

3. If you are posting a link to a site that supports or substantiates what I'm saying, or disproves what I'm saying, that's fair game. Posting a link to your training site without at least explaining why you are doing so is just rude. If you are saying "Hey, I like the pattern matching examples you gave in your post. I'm currently attending a training academy that also covers this, and you might find this useful (link to a specific example that corresponds with the blog post)", seriously, I'm fine with that.

Nonsensical praise like what's posted above tells me that you haven't even read the blog post, you want to get your link on as many of my page as possible, and will guarantee that I will go through and mow such comments out of my feed aggressively. Also, the time I have to spend chopping out bunches of bogus comment posts limits the time and attention I can spend writing new stuff.

For those who have posted informative and inquisitive comments, I thank you and appreciate the fact that you do so. For those who want to do so, but aren't sure how I promise, I'm a rather wordy fellow who is happy to answer questions and do not mind sharing links of a genuinely informative nature. Let's make this a place where we can communicate ideas and not a jumble of SPAM comments that I have to consistently prune.

Monday, June 13, 2016

The Testing Show Is YOUR Show

Edited: Date changed, see below.

TL;DNR: We have a new podcast at The Testing Show. We need show ideas, questions, your involvement! We are having a Tweetup using hashtag #TestingShowChat on Wednesday, June 22, 2016 from 11:00 a.m. - noon Eastern USA timezone. Join us!!!

And now on to more of the show... so to speak.

For the past several months, a fairly large percentage of my time has been spent on an endeavor that I enjoy. That endeavor has been producing and editing "The Testing Show". Put simply, the Testing Show is a podcast hosted and paid for by Qualitest Group. A few years ago, Matt Heusser and I partnered on a podcast hosted by Software Test Professionals called "This Week in Software Testing" (TWiST). It ran for two and a half years, we produced over 130 episodes, and at the time, we felt like we had said all we really wanted to say, or could say. We took a hiatus from podcast production that lasted longer than either of us thought it would.

Towards the end of 2015, Matt and I, along with Justin Rohrman and Perze Ababa, discussed the idea of creating another software testing podcast, reminiscent of the old TWiST, but updated and focusing on newer topics and changes that have happened in the testing word since we stopped producing TWiST. The net result of those efforts is The Testing Show.

Twice a month, we bring you news on an issue happening in the world of testing, or something we think is interesting going on in the broader world and how software testing effects the stories we talk about. In previous episodes, we've covered software systems that erroneously released felons, automated trucking, the challenges of accurate Super Bowl predictions, and software updates causing a satellite to fall out of orbit and burn up in earth's atmosphere... hey, who said testing wasn't fun :)?

We've had a great group of guests come and join us on the show to talk about topics related to their areas of expertise, ranging from Test Management (both process and people), being a Trusted Resource, Testing in Scrum, visits to QA or the Highway and the Reinventing Testers workshop, Automation & Tooling, and Measurement & Metrics.

At the end of each episode, I ask listeners to send us their feedback about the shows they have heard, what they would like to hear, and topics we could cover. It's in this aspect that I want to reach out to our listeners, both current and potential, and see if we can do more.

In our minds, we discuss topics that we think would be interesting to our listeners. Comments on Twitter and other social media sites have been positive, and we thank you all for that. We'd like to see if we can do better, both in the way of helping make a show that you would love to listen to, and also make a show that you would love to share.

As producer of the show, I do my best to make each fortnightly episode the best quality it can be. We often talk for an hour plus, but we edit the show to be roughly thirty minutes, give or take a few. We create show notes with complete transcripts of all the conversation presented, as well as references to what we cover and jumping off points where our listeners can learn more. As we do this, we realize that, amongst ourselves and each other, that we have a limited view as to what's most important to you, our listeners. We can make guesses, but we don't know everything you know, we haven't walked everywhere you have walked, and you have ideas and questions we may never think to ask. We'd like to engage with you directly, and get some opportunities to know what you would like to hear on the show, who you would like to hear from... and if one of the people you would like to hear from happens to be "you", hey, we can talk :).

On Wednesday, June 22, 2016 from 11:00 a.m. - noon Eastern, the cast of The Testing Show will be hosting a live event on Twitter. We will answer questions about the show, discuss things we've talked about in previous shows, but more to the point, we want to know things that you would like to hear us discuss in future podcasts. If that interests you, and you'd like to give us some feedback on what we are talking about, or what we could be talking about, we hope you'll join us. Use the hashtag #TestingShowChat to play along with us. If you can't participate at that time, you can always send email to us at thetestingshow@qualitestgroup.com, and we will do follow up in future shows.

Another way that you can help us get the word out is to leave reviews of The Testing Show on iTunes. If you like what you hear, leave us a review. More reviews means better placement in search engines, and more chances of people discovering the show. Share the show with your friends and encourage them to listen as well. We aim to make The Testing Show the best podcast we possibly can, but ultimately, the show belongs to you, our listeners, and our success resides with you. We'd love if you would join us, and help us make your show the best we can make it.

Monday, January 4, 2016

New Year, New Weekend Testing Americas, Come Join Us!

Normally, these announcements would go up on the Weekend Testing website, but the site is down at the time of this posting, so I am taking matters into my own hands and posting it here until that gets resolved.

With that out the way... Happy New Year, everyone! Here's wishing you all a  happy and healthy and productive 2016, and what better way to get into the groove than with your friends at Weekend Testing Americas (well, sure, you can join a session of any of the other Weekend Testing Chapters, but why not come to our first ;) ). Without further ado, here's what's happening, and when/where:


WTA-68:  Mobile Website Testing
Date:  1/9/16
Time:  1pm EST/10am PST - 3pm EST/12noon PST (check your own time zone for start and end times)
Facilitator:  Jean Ann Harrison


As websites are being overhauled for viewing on mobile devices, are we checking a normally viewed website viewed on a device?  What should you consider important to tests?  Can we automate all these tests?  Yes, and we can talk about what tests can and should be automated and those that can be done faster manually.

For this weekend testing session, we're going to focus on the type of user who uses the Weather Channel website on  mobile devices.

This means we'll be using the browser on the device and not downloading any apps.

1.  What is the first thing any user expects to be able to view?
2.  What kind of view is the user expecting?   Fill the screen?  Scrolling?
3.  Is the font readable? Or does the user need to do something to make the website readable?
4.  Can the user view the videos?  Can the user pause the video and rotate the device and continue viewing the video?
5.  Is the website easy to access the various pages?  Think about the size of fingers or is a stylus needed?
6.  Is it easy to find the latest news?  How to navigate to the news page?
7.  How is the response time?  How is the painting of different pages?
8.  Is there a balance of content and ads?

Logistics:

You may RSVP to the event by sending a request to "weekendtestersamericas" on Skype and letting us know you wish to take part in the session (if you have not initiated a Contact Request, please do that and mention in the body of your message that you would like to participate in this Saturday's session.

On Saturday, January 9, 2016, please be online and ready to connect to the session about twenty minutes before the start of the session. We are willing to add latecomers, but it gets distracting if we have to reiterate everything that happened in the earlier part of the session, so we generally limit new attendees fifteen minutes after the start of the session. We may add more people at that point, but will likely not go back and review what was covered beforehand.

Also, if this sounds like a great way to spend a Saturday to you, perhaps share this message with a number of your friends and encourage them to participate as well.

We look forward to seeing you there.

Regards,
Your Weekend Testing Americas Facilitation Team
(Albert Gareev, Jean Ann Harrison, Michael Larsen and Justin Rohrman)

Friday, August 21, 2015

Call For Interest: BASTUC

Today's post has a local flavor, and it's something I've been mulling over since I got back from the CAST conference in Grand Rapids. Conferences are often expensive, they require travel, time commitment off work and away from family, and a need to negotiate flights, hotels, transportation, etc. These are indeed headaches, but the return on that hassle is often great interactions, learning new things and getting answers to questions I have from sources I might not have initially considered. Plus, I managed to make a new set of great friends each time I go.

For the past few years, we have also had a Saturday event happen before CAST, which has gone by a couple of different names (Test Retreat, Test Coach Camp, etc.) and this has been a much smaller affair. The costs are nominal, usually just enough to cover rental of a space and some snack foods during the day (attendees are encouraged to get breakfast before arriving and go as small groups for lunch). What I find great about the process is the model used for facilitation. Test Retreat/Test Coach Camp is run as an "un-conference"or an Open Space Conference. The topics are voted for democratically, and those people who want to be part of a particular topic participate, and those who don't, don't. Some sessions may have nearly all of the attendees, and some sessions may have two or three people. In both cases that is perfect, because the person speaking is sharing their experience and the people in need of hearing that message get to do so.

One of the challenges I have faced with being one of the leaders of the Bay Area Software Testers meetup is that we want to encourage more people to speak, but there are often limits to opportunities for those potential speakers to get in that space. We have done lightning talks and we are embarking on quarterly Lean Coffee events, but my personal goal is to do something that will help encourage more software testers, and in particular those in the Bay Area to come together, develop talks, practice speaking, conduct workshops, and engage with the broader testing community that's right here.

This is why I'm proposing that we do our own Open Space Conference, the Bay Area Software Testers Un-Conference (BASTUC) . One day, one place, and as many software testers as want to participate. Agenda? You set it! Topics? You decide! Speakers? In this case, I encourage everyone who would attend to come with at least one topic they would like to talk about, even if it's formative or just to say "I have so many thoughts going on in my head about THIS THING, and if I don't get together with some other people and discuss it, my head's going to explode!" Well, OK, we hope not literally, but we want to encourage testers to feel comfortable coming out and discussing the things that matter to them. Chances are, they matter to other people too.

For the record, I have not told Josh and Curtis about this. This is a blind side, and frankly, it's just an idea. I want to see if there would be support for it, and who would participate. If you want to play along, please leave a reply, and we'll take the next steps if this is something that appeals to enough people (and seriously, in my mind, if we get ten people interested, that's enough to move forward on this).

Also, the name is open to discussion, but I had to call it something ;).

Friday, June 5, 2015

The Value of Mise en Place

I have to give credit to this idea to a number of sources, as they have all come together in the past few days and weeks to stand as a reminder of something that I think we all do, but don't realize it, and actually utilizing the power of this idea can be profound.

First off, what in the world is "mise en place"? It's a term that comes rom the culinary world. Mise en place is French for "putting in place", or to set up for work. Professional chef's use this approach to organize the ingredients they will use during a regular workday or shift. I have a friend who has trained many years and has turned into an amazing chef, and I've witnessed him doing this. He's a whirlwind of motion, but that motion is very close quartered. You might think that he is chaotic or frantic, but if you really pay attention, his movements are actually quite sparse, and all that he needs is right where he needs them, when he needs them. I asked him if this was something that came naturally to him, and he said "not on your life! It's taken me years to get this down, but because I do it every day, and because I do my best to stay in it every day, it helps me tremendously."

The second example of mise en place I witness on a regular basis is with my daughter and her art skills. She has spent the better part of the past four years dedicating several hours each day drawing, often late into the evening. She has a sprawling setup that, again, looks chaotic and messy on the surface. If you were to sit down with her, though, and see what she actually does, she gathers the tools she needs, and from the time she puts herself into "go" mode, up to the point where she either completes her project or chooses to take a break, it seems as though she barely moves. She's gotten her system down so well that I honestly could not, from her body language, tell you what she is doing. I've told her I'd really love to record her at 10x speed just to see if I can comprehend how she puts together her work. For her, it's automatic, but it's automatic because she has spent close to half a decade polishing her skills.

Lately, I've been practicing the art of Native American beading, specifically items that use gourd stitch (a method of wrapping cylindrical items with beads and a net of thread passing through them). This is one of those processes that, try as hard as I might, I can't cram or speed up the process. Not without putting in time and practice. Experienced bead workers are much faster than I am, but that's OK. The process teaches me patience. It's "medicine" in the Native American tradition, that of a rhythmic task done over and over, in some cases tens of thousands of times for a large enough item. Through this process , I too am discovering how to set up my environment to allow me a minimum of movement, an efficiency of motion, and the option to let my mind wander and think. In the process, I wring out fresh efficiencies, make new discoveries, and get that much better and faster each day I practice.

As a software tester, I know the value of practice, but sometimes I lose sight of the tools that I should have at my beck and call. While testing should be free and unencumbered, there is no question that there are a few tools that can be immensely valuable. As such, I've realized that I also have a small collection of mise en place items that I use regularly. What are they?

- My Test Heuristics Cheat Sheet Coffee Cup (just a glance and an idea can be formed)
- A mindmap of James Bach's Heuristic Test Strategy Model I made a few years ago
- A handful of rapid access browser tools (Firebug, FireEyes, WAVE, Color Contrast Analyzer)
- A nicely appointed command line environment (screen, tmux, vim extensions, etc.)
- The Pomodairo app (used to keep me in the zone for a set period of time, but I can control just how much)
- My graduated notes system (Stickies, Notes, Socialtext, Blog) that allows me to really see what items I learn will really stand the test of time.

I haven't included coding or testing tools, but if you catch me on a given day, those will include some kind of Selenium environment, either my companies or my own sandboxes to get used to using other bindings), JMeter, Metasploit, Kali Linux, and a few other items I'll play around with and, as time goes on, aim to add to my full time mise en place.

A suggestion that I've found very helpful is attributed to Avdi Grim (who may have borrowed it from someone else, but he's the one I heard say it). There comes a time when you realize that there is far too much out there to learn proficiently and effectively to be good at everything. By necessity, we have to pick and choose, and our actions set all that in motion. We get good at what we put our time into, and sifting through the goals that are nice, the goals that are important, and the goals that are essential is necessary work. Determining the tools that will help us get there is also necessary. It's better to be good at a handful of things we use often than to spend large amounts of time learning esoteric things we will use very rarely. Of course, growth comes from stretching into areas we don't know, but finding the core areas that are essential, and working hard to get good in those areas, whatever they may be, makes the journey much more pleasant, if not truly any easier.

Wednesday, April 29, 2015

#CAST2015: Full Program is Posted



It's that time of year again. The time when the #CAST2015 hash tag starts to get a lot of play. For those who stumbled here from another location, #CAST2015 refers to the Conference for the Association for Software Testing, which has been an event that, for my not being directly involved in its planning or execution, has taken up a fair number of cycles of my reality. 

The full program was announced today, and it is available to view here.

To paraphrase the Conference Committee (or more accurately, just steal it whole cloth):

The Association for Software Testing is pleased to announce its tenth annual conference, CAST 2015 “Moving Testing Forward,”to be held in Grand Rapids, Michigan, August 3-5.Since our first CAST we  have seen dramatic changes in the nature of communications and the nature of delivery, from PC to client/server to the web and web services. Deployment is different; monitoring is different, builds and test tooling are different. We have a variety of new models and methods for our testing. CAST is where we talk about how they actually work out in practice, based on experience. At our tenth CAST, in 2015 speakers will be presenting stories, workshops and tutorials regarding their experiences surrounding how to advance software testing.

Join us this summer for our tenth annual conference in downtown Grand Rapids at the beautiful Grand Plaza Hotel August 3-5, as we explore “Moving Testing Forward.”

As President of the Association for Software Testing, you can bet I will be addressing a whole lot of CAST stuff over that the official web site, but right now, I'm actually stepping back a little bit and I'm talking totally off the cuff, not as the President of AST (though this will certainly be seen by some as "official pronouncements" anyway, so whatever).

First, I want to say that I am impressed with the variety and variation we have in the program this year. CAST is a diverse conference to begin with, but we made a specific focus this year to invite people who had not presented before to really give it a go this year. I am happy to say that there are several speakers who will be giving their first conference talks at CAST this year. I'm also proud that AST partnered with Speak Easy and arranged to work with them to help develop talks for the conference. Speak Easy has made it its mission to help encourage women to speak at conferences, and we are delighted to say that four talks that were mentored by SpeakEasy were picked for the conference.  CAST has prided itself on being a place where different voices get heard, and not specifically catering to the "rock stars" of our industry. We've had a good balance, I think between male and female speakers, male and female keynotes, and a diverse group of participants from different countries and backgrounds. Compared to many conferences I've been to, I'll dare say I think CAST really is one that deserves high marks for diversity. Can we do better? Most certainly, but this year's lineup makes me feel like we are in the vanguard. 

I'll borrow a couple of posts from Lisa Crispin to help make this point even more ;):







Another area I want to talk about is the two hour workshop that will be offered on Tuesday, August 4, 2015 called "Black Box Accessibility Testing: A Heuristic Approach". This workshop will be given by Albert Gareev, with some solid peanut gallery support from yours truly. I'm sure some of you are looking at the title and thinking to yourself "Wait a minute, that sounds a lot like the talks Michael has been delivering this year. Are they at all related?" The answer is, of course, yes. Albert and I have been working for quite some time to help develop both design and testing approaches that help bring Accessibility to light and get some focus and attention. We've both written and presented extensively on these topics, and this year, we have melded minds to help present and deliver a solid workshop of testing skills and techniques that anyone can walk away with and be effective. So why is Albert listed as the speaker and not me? First and foremost reason, the workshop is primarily Albert's research, practice and learnings, so he very much deserves the credit for presenting the workshop. Do I have a hand in what's being presented? Sure, and I'll be spending a fair amount of time helping hammer out the paper that will be available at the conference (yes, we are writing the paper together :) ).

For those who want to attend a conference that will be first rate with regard to content, diverse speakers, unique and original voices, and talk about topics that are relevant to your everyday work, and not retreads of stuff you've heard many times before, I want to personally encourage you to sign up and attend #CAST2015 with us in Grand Rapids, Michigan. It's going to be a great time, and I hope to see you there as we work to "Move Testing Forward"! 

 

Friday, April 3, 2015

On Community, or "Building Your Perfect Beast"

This is going to come across as perhaps a bit scatter-shot, because it contains thoughts that address a lot of things that I am involved in. Each of these could be addressed in a number of different places, and in time will very likely be addressed there, but for right now, today, I am going to separate my various public personas and address this as just me, right now, In my own sphere. What you are reading right now has both nothing to do and everything to do with the Association for Software Testing, the Miagi-do School of Software Testing, Weekend Testing Americas, the Bay Area Software Testing Meetup group, and the freelance entity that is TESTHEAD. For right now, I am addressing this as me and only me. The remarks that follow are not necessarily representative of any of those other initiatives and the other people involved in them.

One of the key messages I received loud and clear about the world of software testing and those who are involved in it is that there is a bit of an identity crisis happening. The world of software development is changing. Long standing biases, beliefs and processes are being disrupted regularly. Things that worked for years are not working so well any longer. Business models are being upended. The rules of the game and the very game itself is being re-written, and many people are waiting to be shown the way.

One of the things I have witnessed time and time again is that there is no end of people happy to consume materials created. I'm very much one of those people, and I enjoy doing so. However, at some point, there comes to be a space where there is a limit to what can be consumed and a void as to what is there. Something is lacking, and a need that is not being fulfilled. It's very easy to ask that someone fill that need, and complain when that person or group does not do so. I remember very well being called to task about this very thing. Back in 2010, I lamented that no one had brought Weekend testing to the Americas, that I had to attend sessions hosted in India, Europe and Australia, often either late at night or early in the morning for me. Joe Strazzere set me straight very quickly when he said (I'm paraphrasing):

"Perhaps it's because no one in the USA values it enough to make it happen. YOU obviously don't value it enough either. If you did, you would have already made it happen!"

That was a slap, but it was an astute and accurate slap. I was lamenting the fact that something I wanted to consume wasn't readily available for me in a way that I wanted to have it. I was waiting for someone else to create it, so I could come along and feed at the counter. Instead, I realized someone had to prepare the food, and since I wanted to eat it, I might as well prepare it, too. The rest, as they say, is history, and to be continued.

I want to make a suggestion to those out there who see a need, an empty space, an unfulfilled yearning for something that you have identified... is there any reason why you are not doing something to bring it to life? Are you waiting for someone else to give you permission? Are you afraid your idea may be laughed at or criticized? If you are a software tester, are you suffering from the malady that you see a problem for every solution? If so, I want to assure you that I understand completely, as I have been there and find myself in that position frequently. Perhaps you feel that you are alone in your frustration, that you are the only one who finds it frustrating that something you care about is not being addressed. While I was at STP-CON, and during Kate Falanga's session, we discussed the three layers of engagement and change/influence. The first layer is ourselves, the second is our team or organization, and the third is the broader community. There's a very good chance that any void you are seeing, any initiative that you hope to see championed, has many who likewise want to see a champion emerge.

My advice to all out there is to stop waiting for someone else to Build the Perfect Beast, and instead, start building your own. Once you start, it's a good bet others will want to get involved as well. No one wanted to do Weekend Testing in the Americas until I was willing to throw my hat in the ring. In short order, others decided they wanted to get involved as well. Some have come and gone, but we are still here and many have helped us solidify what we do. Our Beast is not yet perfect, but it's getting there, and we've learned much along the way. Same goes for every other organization I am involved in. Major movements do not happen by timidly waiting for someone else to take the lead, and they don't come about by asking for permission to do them, either. If you see a need that is not being met, try to create something that will meet that need, even if you have to do it alone at first. My guess is, over time, others will see what you are doing and want to be part of it, too. Do be warned, though, the desire to create is addicting, and you could find yourself a bit over-extended. On the other hand, you may be having too much fun to care :).

Thursday, January 22, 2015

Do You Want to Move Testing Forward?



The Association for Software Testing (AST) is holding its tenth annual conference this year. The Conference for the Association for Software Testing (CAST) will be held in downtown Grand Rapids, Michigan on August 3-5, 2015. Ten years is a cause for celebration in my book, and we are throwing a party. I say "we" because I am part of the Board of Directors and the President of AST, and therefore this conference is a big part of what 2015 will be shaping up to be for me.

The theme of the conference this year is “Moving Testing Forward”, and to that effect, I want to reach out and encourage my fellow software testers, programmers, quality advocates, or whatever area you see yourself, to put in a proposal for this year’s conference.

My belief is that the best way to move testing forward is to do so with more voices, and CAST is well known for being the conference where new and unique voices are heard. Several great speakers have developed over the years, and CAST has been quoted as being where many of them first had the opportunity to present. We want to encourage that approach further, so I am sending out a personal call to those software testers who might still be on the fence.

- Maybe you are a relative newcomer.
- Maybe you have not spoken in front of a large group before.
- Maybe you work in an industry and an environment where you think “oh, nobody would be interested in hearing what I have to say”.

Let me assure you, that last one is categorically false. In my opinion, the best talks and presentations are not built around theories or tools. They are built around real world experiences, the good, the bad, the occasionally ugly, and the often unintentionally hilarious.

I had the pleasure of having dinner last night with a couple of friends, both involved in various levels of software delivery, including software testing, and the stories we were sharing, and frequently laughing about, came from our core experiences, what we have witnessed, and what we have learned from those experiences. As I listened and participated with my friends, I mentally ticked off six or seven talk ideas and said “wow, these stories, and the lessons learned from them, would be so great if we could get them out to more people”. I have a pretty good feeling that several of these conversations will become talks at CAST, but the main point I want to encourage is that “your real world experiences make for great talks!

The Call for Participation for CAST 2015 ends on January 31, 2015. That’s a little under ten days from now. I’d like to encourage all of you, if you are able, to propose a talk for CAST. How are you moving testing forward? There’s a very good bet that what you are doing (or perhaps wish you were doing, or perhaps not doing) will be of great value to your fellow software testers. We encourage people from all arenas, all experiences, and all backgrounds to come share in each others ideas and approaches. There will be a lot of fun things happening at CAST 2015. We want you to be part of it :).

Wednesday, January 21, 2015

Experience is Earned, Expertise is Granted

This title is meant to be a little provocative, and some may disagree with it, but I've been thinking about this topic quite a bit recently. First of all, I want to say thank you to Ryan Arsenault and the folks over at uTest for showcasing me in their first "Ask the Expert" blog entry. The questions I was asked centered around career choices for testers and ways that we can succeed, or at least do better than we are now.

I cannot help it, part of me feels very strange using the word "expert" to describe myself at anything. I'm happy to use words like experienced, educated, practiced or even proficient, but "expert" carries a strange weight to it. It's so subjective, and it feels like, once you've been branded one, that there's only one way to go from there, and that's down. Moreover, I don't really believe there is such a thing as an "expert", because that implies that that person has learned all there is to learn and has mastered all there is to master... and that's just fundamentally wrong on so many levels.

I've come to realize that we all own our experiences, and that we all have opportunities to learn from our successes and our mistakes (oh, how much I have learned from my mistakes). This is why I have no problems talking about my experiences or my observations. They are mine, and as such, are certainly open to interpretation, or debate, or scrutiny, or even outright ridicule at times, but they are wholly mine. Expertise, however, is a judgment call. I personally have very little trust in people who proclaim themselves to be "experts" at anything. However, I place a lot of credence on other people who tell me that someone is an expert. Why? because they are witnesses to the skill, acumen and judgment being displayed, and they can then decide if the term "expert" makes sense.

It also often comes down to "expert compared to who?" I have many interests, and things that I spend a lot of time getting into. When I tell people I was a competitive snowboarder for several years, it conjures up an image in their minds; I must be an expert snowboarder. They may even watch me ride, and come to that conclusion because of the technique I can muster and the terrain I can ride on. Yet put me alongside other riders I used to compete with, and any questions of my so called "expert" level goes right out the window. That doesn't take away from what I have learned, the events I've participated in and the medals I won, but to use those hallmarks to say I am an "expert" is, in my mind, misleading. Still, to others who have never raced, or are newcomers to the sport, to them I am an expert, insomuch as I can show or teach them things that they do not know.

Again, I thank uTest for giving me an opportunity to share my experiences, and I am honored to be part of their "Expert" panel. I don't know if I deserve the moniker, but they seem to think so, and so do their readers, and ultimately, I guess that just means it's up to me from here on out to either prove them right, or prove them wrong. Here's hoping my actions and efforts do more to strengthen the belief in the former, rather than proving the latter ;).

Tuesday, January 20, 2015

Take Two: A Survey on “The 2015 State of Testing”

So let me set the stage here….


Joel Montvelisky wanted to write a post about the advances that have taken place in the tester-verse in the last 5-10 years. While he was trying to put this post together, he came to the conclusion that there really isn’t a centralized set of information or trends as to what is happening in the testing world.

What does a tester do when they can’t find that information? They take it upon themselves to make their own. Trust me, I understand this logic completely ;).

Thus, Joel reach out to Lalit Bhamare (who edits Tea Time with Testers) to create and conduct a State of Testing Survey. The purpose? To provide a “ snapshot” of what the “ reality” of the testing world is, and see if we can follow various  trends as they shift year by year.

For those feeling that this post is a dose of “deja vu”, well… yes, it is! The above couple of paragraphs are pretty much word for word what I wrote towards the end of 2013, when the last version of the survey was posted. Joel, Lalit and others who were asked to contribute to it are now bringing forward the 2015 State of Testing survey. I had a small hand in reviewing and helping shape this second go around for the survey.

Also, just like in December of 2013, for this survey to be effective, many people need to participate. With that in mind, I’m doing my part once again to help spread the word and encourage everyone to participate



This survey will be going live roughly 00:00 Thursday, January 22, 2015 (Pacific Time). Right now, there’s a countdown saying when it will go live, so if you go there right now, you’ll see the countdown. Come back when it tells you it’s done, or subscribe to get the official go-live message. Like last time, I am anticipating the survey will be up for about ten days.

So here’s what I am asking… again ;):

  1. Go to the link and subscribe so that they can contact you when the survey goes live.
  2. Participate in the survey and give you honest feedback.
  3. Make a point to tell as many testers as you can to likewise participate in the survey.


For those who would like to see what the end of 2013 survey looked like, at least as far as the survey responders said, the link to the results are on the page as well. Also, a disclaimer; this survey is, like all things, subjective and reflective of the respondents as a whole. It may or may not reflect your own reality, but then, if you don’t participate, it definitely will not reflect your reality, or even a statistical sliver of it. If you want to give your opinion or have your voice heard, well, now’s your chance :).

Thursday, January 1, 2015

In Through the Side Door: Advice from an Unconventional Career

First off, Happy New Year to all of my friends and readers out there. I wish you all a great 2015 with the hope that what you strive to do and accomplish will be met.

About two years ago, I was given the opportunity to do a talk for a conference that would be happening in India called ThinkTest. My friend Smita Mishra extended an invitation to me to participate, and while I could not actually travel to India at that time, we decided to try something unorthodox. Why not video-tape my talk, and we would whittle it down to a presentation length and make it available to those who wanted to view it? Since I found myself in a hotel room near Chicago for an extra day, I decided to turn the room into a makeshift film studio and talk about my career as a software tester, its ups and downs, and other things that helped make it a reality.

Sadly, due to an automobile accident that incapacitated Smita for awhile, the conference had to be canceled. The talk project was, of course, put on hold, and then, over time, other initiatives took center stage, and I forgot about the talk and the recordings... that is, until a couple of months ago. Lalit Bhamare of Tea Time With Testers, asked me if we could use the material for his new project, TV for Testers. I said "sure", and he then proceeded to gather the clips I had recorded and delivered to Smita into the talk that is presented here.



In Through The Side Door

First, I feel it only appropriate to say... this is a long talk! I had originally recorded it with the idea that we would cherry pick the best parts and make a shorter presentation (something around forty minutes) but through correspondence with Lalit, he asked if it would be OK to present the entire talk, in its (mostly) unfiltered form. He felt that there was a lot of insights I offered that would be of value to those who, likewise, came to their careers from peripheral avenues, and the asides and segues, in his opinion, actually added to the value of the talk. So, again, that's what we decided to do. Lalit posted the talk on TV for Testers today, and I am now saying to those who would like to check it out, please do so.

Again, my thanks to Smita for asking me to put this together, and my thanks to Lalit for deciding he wanted to have it be seen. If you take the time to watch it, I also thank you for doing exactly that. To borrow from and paraphrase the recording artist Seal, "I hope you enjoy the presentation; it was the best material I had at the time" :).

Friday, December 12, 2014

Time is an Asterisk

It is that time again. It's the end of another year, and it's the time that I do my typical retrospective on the year that was, what I wrote, what I learned, what I did and what I didn't do. I did a little search for my "Retrospective" tag and smiled, realizing that this is the fifth entry in this series, and an (almost) fifth year of writing this blog. I think that's somewhat noteworthy, as I have very few endeavors that I can point to that have survived for five years, much less thrived. Outside of my marriage and family, and a couple of jobs, this may well be the single longest running entity I've ever managed. No, that's not a sign I'm looking to end this, in fact I'm just getting warmed up. Also, yes, the title is, once again, a nod to the Talking Heads song 'Once in a Lifetime". I'm not sure how many more years I'll be able to keep this streak going, but it worked again for 2014.

The year started with a lot of promise, and in some ways, a need to recuperate. Last year, I took on a daunting challenge of writing 99 action plans for what a software tester can do to become a better software tester. I have the contents of what could be a pretty cool book, but it needs editing, curating and a lot of revision. If there's anything I discovered about myself in 2014, it's the fact that huge looming projects can easily get derailed because I see and feel that they are huge and looming. I did the same thing with an idea to approach technical testing with Noah Sussman's guidance. In some ways, the sheer size and order of magnitude of these projects spooked me, and they got pushed to the back of my focus. 

At the end of the year, I realized I was perhaps too ambitious, and needed to step back a bit and rethink my approach. The saving grace for both of these projects is that they have the potential to turn into an interesting collaboration with my youngest daughter. Because of Google's "Made with Code" events, she has decided she wants to learn how to code. This brings back both of these initiatives, and several others, but now it puts it in a much clearer focus. The ideas I had are interesting, but unfocused. Helping my daughter learn how to code and text, that's a focus. I anticipate those earlier initiatives will get some fresh air and the embers will be stirred and blown back to life. It no longer just about me and my musings, now I have to put up or shut up ;).

This year has been an interesting transition, in that I have been receiving a lot of requests to write for other publications. I am grateful to sites like Smartbear, Zephyr, Techwell and IT Knowledge Exchange, among others, in that they have given me a platform to write about my experiences and pay me for them, too. Of course, that creates an odd tension. Do I hold back and publish for those who will pay me? That's great, but what about the articles that don't fit what they want to publish? What about the things that really only interest me and the readers here? Am I short changing my audience by holding back from this blog? I had to give this some serious thought and see what made sense to do, and ultimately, I decided that I needed to come back and say "what is TESTHEAD ultimately about?" It's really about the education of a software tester, and part of that includes learnings that come from unexpected places. My experiences have a value, and people enjoy reading them. Even more surprising is just how many people still visit my blog even when I haven't posted anything in awhile. What also fascinates me is to see what posts consistently show up as perennial favorites. As of today, my top ten posts are:
  • Testing as a Service? A Post-POST Post (workshop review)
  • Read Articles, Blogs, Forum Posts: 99 Ways Workshop (how-to guide)
  • Introvert? Extrovert? Or Both? (exploring diversity)
  • Learning to Tell Different Stories (exploring diversity)
  • Exercise 5: More Variables And Printing: Learn Ruby the Hard Way (how-to guide)
  • Inflicting Help (lessons from home)
  • BOOK CLUB: How We Test Software at Microsoft (5/16) (book review)
  • Onboarding and Not Getting Mau Mau'd (interpersonal relationships)
  • When Things Just Aren't What They Seem (interpersonal relationships)
  • I Used To Be a Staffer… (volunteering and leading)
What this shows me is that there is no clear theme as to what posts are most appreciated. It's not like there's a "type" of post that specifically gets more traffic than others. The one telltale sign I do see, though, is that of these top ten reads, most of them have to do with my own personal takes on things. Not some authoritative commentary, but just my fallible opinion of why things seem to be the way they are. Also, it seems the areas where I try something and it doesn't work out well, or an area where I am stepping in with guarded enthusiasm are where you all tend to come back to or tell others about. It means my goofy optimism and occasional cluelessness is appreciated and entertaining. I think I can mine that vein for a very long time ;).

This year saw me bring the testing message to a few different venues, some of which were not testing related. I spoke at the ALM Forum 2014 in Seattle, WA, Developer 2014 in Burlingame, CA, I shared the stage with Harrison Lovell at CAST 2014 in New York City, and went to be a participant and correspondent at EuroSTAR 2014 in Dublin, Ireland. During all of those events, I had a chance to meet many new people, start new friendships, discover new opportunities, and generally expand my world just a bit larger than it was before.

2014 was a year of transitions for me. It was a year that saw my eldest child move from High School to college. It was a year where  I lost several close friends. It was a year where I stepped down as the Chair of the Education Special Interest Group and relinquished my role as Treasurer within the Association for Software Testing, and accepted the role as President of the organization. It was a year that saw a Meetup group grow and flourish in San Francisco, then drift a little bit, and then have a hostile takeover attempt take place, to which the core community fought back. It reminded me of an amazing connection I have with many people, and how, when it looked like we might have to walk away, they stood together and said "Oh hell no you won't!" Weekend Testing Americas turned four years old, and has a healthy core of interested facilitators and participants who eagerly ask us "when is the next session?" BTW, December being so jam packed with other events related to families and other groups, we are taking December off, but we will be back in January, and we have a lot of cool new ideas to explore.

Most of all, I have to give my thanks and gratitude for this little forum, what it's become, and how it continues to surprise me, both with what I post here, and with how people react to it. Seriously, to whoever is reading this, whenever you read it, the fact that you took the time to come to my blog, to read something I wrote, to leave me a comment or share a link on a social media site, that you engage with me year after year, it's touching and humbling. Were it not for you, I'd have no reason to do this. Also, so many of the opportunities that come my way start here. Thank you for following up, for asking questions, for holding me accountable and for keeping me honest. It makes writing this blog a whole lot more fun because of that.

As the title says, Time is an Asterisk. It's not just a line to continue a theme (though it does that quite well ;)), it also reminds me that, truthfully, I don't know what next years letter will look like, or what forces are going to shape the next year, or what the flavor of the posts that come will contain, though I can probably offer some guesses. I have a lot of books I want to review. I have a lot of ideas I want to test out with my daughter to see if they work or not. I have a lot of goals I want to see myself obtain. Which ones I will actually cover, and which ones will be written about here, that remains to be seen, but I will do my best to make sure it's something interesting and unique to my own experiences. That I can pretty much guarantee. The rest is a wildcard ;).

Thursday, December 11, 2014

Book Review: Zero to One

As a birthday/Christmas present, a  friend sent me Peter Thiel’s “Zero to One” in a four CD audio format. Peter reads through and presents nearly four hours of audio that goes much faster than the elapsed time would indicate. On the audio production aspects and delivery, it does very well. Having said that, how about the book as a whole?

Zero to One is a book about being an entrepreneur. For many of us, we may stop right there and think “ehh, I’m not an entrepreneur, so this book isn’t for me”. I would encourage anyone with that attitude to not think that way. Regardless of whether or not we work for a company, or we are the founder of a company, or we do freelance work in various capacities, all of us are entrepreneurs. In the curation of our own careers, absolutely we are. To that end, we want to create, to do something interesting, and maybe, dare we say it, change the world.

Most businesses we will see tend to copy someone else in some capacity. They are content to copy what has been successful for others. This is what Peter refers to as "One to N” improvement. It’s incremental, it’s a shaving of time, it’s an improved efficiency, it’s streamlining of process. It may keep you afloat, but it will not rocket you ahead. For that, you need a different approach, a true sense of innovation, a mindset that will bring you from Zero to One.

Thiel presents many anecdotes from the past thirty years in Silicon Valley, with many familiar stories, ups and downs, and memories, oh the memories (having been at Cisco Systems in the 1990s, and with several smaller companies through the ensuing fourteen years, Thiel’s stories are not just memorable, they are my history, and some of the stories hit a little too close to home ;) ).

The book is structured around seven questions that any company (and any individual) should be ready and willing to ask themselves before they commit to a venture or creating what they believe will be a “killer startup”. Those questions are:

Zero to One:  Can you create something new and revolutionary,  rather than copy the work of others and improve upon it?

Timing: Is NOW the time to start your business? If so, why? If not, why?

Market Share:  Are you starting as a big player in a small or underserved market?

People: Do you have the right people to help you meet your vision?

Channel: Can you create and effectively sell your product?

Defensibility: Can you hold your market position 10 and 20 years from now?

Secrets: Have you found a unique opportunity or niche others don’t know about?

Additionally, Thiel encourages that any product that will qualify as a Zero to One opportunity will not just compete with other options, but it will offer a 10X level of improvement over what has come before. If it doesn’t, then competition may overtake and erode anything you may offer. Harsh, but perfectly understandable.

Thiel addresses topics like success and failure, of disruption and collaboration, of replacement and complementarism, and of the fact that any real good technology, no matter how good, needs to be sold and marketed. Engineers believe that if their products is as good as they think it is, it will sell itself. History shows time and time again that that is not the case, and Thiel comes down hard on the side of sales being a driver, and that sales must be shepherded.

Bottom Line: Zero to One makes the case that true entrepreneurship needs to start from the idea of doing something unique, and being willing to look at the seven questions realistically and determinedly. If you cannot answer all seven of the questions with a YES, your odds of success are greatly diminished. Even if all seven can be answered with yes, there are no guarantees. This book is not a tell all guide as to how to be an entrepreneur, but it does give some concrete suggestions as to how to approach that goal. It’s a what and a why book, not a how book, at least not a "formula" how book. It does, however offer a lot of suggestions that the future entrepreneur, company worker, or freelance creator could learn a lot from. If you get the book, read it twice. If you get the audio version, listen to it three times. I think you’ll find the time well spent.

Saturday, December 6, 2014

Don't Know What You've Got Until Someone Tries to Take It

The past three days have been, shall we say, emotional, frustrating,  and wonderful, all at the same time. Most of all it has shown me that a group of vocal people can make a difference, but more on that in a bit.

First, some perspective. Last year, Curtis Stuehrenberg and I, along with Josh Meier, decided it was high time there was a software testing Meetup group in San Francisco. May not sound all that revolutionary, and wait, weren't their plenty of software testing groups already? Well, yes, if your main focus was on a specific tool. The Selenium Meetup group has been a de-facto testing group for years, and it's where a lot of software testers go to participate and share in testing topics from time to time, but what we noticed was missing was a focus on the "ilities" of software testing, as well as the areas that go beyond the programming aspects of software (or "paradev" aspects, to borrow from Alister Scott). Thus, we decided to inaugurate the Bay Area Software Testers group, or BAST, as we colloquially refer to it, with the following goals in mind:

The Bay Area Software Test Association originally formed as an impromptu attempt to provide software testers and quality engineers from San Francisco and the East Bay a place to meet and network without having to brave the Silicon Valley traffic snarl. Currently we meet on a monthly basis, providing a chance to hear people talk about general topics and socialize/network/schmooze some of the more interesting people on any software development team .... the testers!

We enjoyed several months of great talks, great conversations, and great activities, and then the summer and fall time frame saw less activity, due to scheduling challenges all of us were dealing with, and just a general challenge to get everyone on the same page. Sometime in this time frame, my Meetup account had been hacked, and I stopped receiving updates. Sad thing is, so much else was going on that I didn't get a feeling for what was happening until just a few days ago. A post to Twitter, though, definitely got my attention:


My first reaction was confusion, then bewilderment, then anger. How could someone hijack our group? Well, we discovered how quickly enough. In the interim as we were looking to transition out of the previous payment and registration (which Curtis had held) and to our new payment model (which Josh and SalesForce had offered to help us with) a member of the group jumped in and made the payment for the next year. In the process, they set themselves up as the organizer, effectively blocking us from being able to administer our own group. What followed was a conversation between Curtis, the person who shall remain nameless, and the folks at Meetup. We were, of course, frustrated that this new entity took over the group from us. We were doubly frustrated when they wouldn't give it back, and we were triply frustrated, and then enraged, when the group started to get spammed with commercial training dates posing as Meetup events. 

To add to the frustration, Meetup gave us the standard policy line of "sorry, it's not up to us, you need to work this out with the new organizer, as they have paid for the group". It was at this point that Curtis, Josh and I, as well as many other people, went on the offensive and started to look for other options. Would we abandon BAST? Make a new group? Drop Meetup altogether and go to another service (Eventbrite perhaps?). Several people took to the interwebs and started calling out the individual who had hijacked the group, and Eventbrite responded to us publicly and said that, if Meetup couldn't help us, they'd be happy to help us establish a new home.

This story, I am happy to say, has a happy ending. Due to the pressure and the vocal comments from several members of our broader community (many of which aren't even in San Francisco), Eventbrite willing to help us make a new home, and our own members posting to the BAST forum that they would not stand for their group being hijacked, and would therefore leave (myself being one who posted a similar comment), Meetup came back to us, allowed us to reinstate Curtis, Josh and myself as organizers, and we were able to deal with the person who hijacked the group and ban them from further participation.

Several lessons came out of this experience, but none more poignant than the fact that we realized we had a great thing, and that it could be take away from us far easier than we ever imagined. Second to that was the fact that we have a great community that cares about what we have created and were wiling to fight on our behalf, not just to say how sorry they were that this was happening, but actually step in and help us resolve it. Third is that people vote with their feet, and if you abuse their trust, you can lose their support very quickly. Fourth, it showed me that we can't take this group for granted. It needs to be cared for and it needs to be nurtured. To that end, for those who left BAST because of this recent mutiny, and for those who were unhappy with the change of events and chose to abandon ship, we want to let you know that everything is back to normal (perhaps even better than normal) and that Josh, Curtis and I are looking forward to making 2015 an active and involved year of discussion and get togethers. Perhaps we let time and momentum take over, but this recent upheaval showed us all how much this group mattered to us, and we are not going to let such a thing happen again. If you left us, please come back. If you want to help us develop events for 2015, we'd love to hear from you. Most of all, we look forward to getting together to socialize/network/schmooze with some of the more interesting people on any software development team .... the testers ;)!

Monday, December 1, 2014

A Yankee Let Loose In Eire: Some Less "Testy" Reflections

As it has probably been abundantly clear, I spent most of last week in Ireland, and the remainder of the work week getting there and back. Some of the situations I witnessed were humorous, sometimes frustrating, often educational, and also very eye opening.

Let's start with the actual travel. As is routinely the case, we are recommended to get to the airports three hours ahead of time when any international travel is involved. I heeded that call, and was, of course, in and out of security in less than twenty minutes. Having the freedom to therefore relax and just wait for my flight, I did exactly that. As a little bit of housekeeping, I went through and got everything together I could for the flight, and made sure my adapter was working. I reminded myself that last time, I brought a power strip with me to help make things easier, and the net result was the blowing of the fuse of the hotel room when I was in Malmö. I learned this time, one device at a time, and also, I greatly reduced my packing footprint. Just my MacBookPro, my iPhone, their power cords, and the converter to handle UK/Ireland monster plugs. through judicious packing, I managed to get everything I needed into a single bag I could carry on my back. It was thick, but it met requirements to get under the seat, so I was golden.

I am  grateful that trans-continental and transoceanic flights now have power outlets readily available in most seat rows, if not for each and every seat. I finally had the ability to keep power to my devices for the entire trip, which was wonderful. Keeping the devices actually plugged in? That's another story. I think with the frequency of use of these receptacles, it's near impossible to keep an adapter plugged in without it dropping of at some point. I quickly became adept at rigging up various jigs to hold the adapter plugs and such in place so they wouldn't disconnect mid flight.

My two hour layover in Washington, D.C. turned into a five hour layover because the oven in our trans-Atlantic flight was having problems. I'm sure some of you might be thinking "an oven caused that much trouble?" Actually, yes. Without an oven, a Trans-Atlantic flight cannot heat food, and going seven hours without food makes for a cranky set of passengers, so we were all shuttled of the plane and onto another plane at another terminal, along with its requisite checks (yes, the over worked this time :) ). One fantastic bonus was the fact that I had no seat mates for this flight. Not that I am not one who likes conversation with my fellow travelers, but the fact I could actually lie down across three seats, stretch out, and get some actual sleep? Awesome!!!

Out flight landed in Dublin at just a little after 12:00 noon. A quick step through Customs and Immigration including why I was in Dublin ("a software testing conference"... "a what?!" "yes, a software testing conference". I'm now three for three on having to explain that ;) ), and a trot over to get on the double decker green air bus, and I was whisked away to the Dublin Convention Center. I kid you not, I walked in, got my badge, walked up to the third level auditorium, sat down, opened my MacBook, and the official conference program and opening keynote started, right then and there. Sure, I'd have liked to have checked into my hotel first, and maybe changed clothes, but in a pinch, this was fine.

The half day program went quickly (my full running commentary of the day one of EuroSTAR can be seen here) and at the closing of the official session, we were treated to a drum corps that got our attention and then led us downstairs for the evening reception. As there was a dinner being held at Trinity College, but I didn't realize it until it was too late that we had to do a separate registration for that, I was happy to go out and explore Poet's Corner with Michael Bolton, Zeger Van Hese, Jokin Aspiazu, Ruud Cox and several other testers, including helpers in The Test Lab. We settled on The Bachelor Inn, which was a nice pub with good food and drink (and even something for a tee-totaler like myself :) ). As is always the case, the conversation was wonderful, and it is so hard to resist the temptation to hang out all night at these events. Alas, I was missing eight hours from my day, and I knew if I didn't make at least an effort to get some sleep, I would be struggling the next day.

I stayed at a little place called the Maldron Pearse, which was about a half a mile from the Convention center, across the Samuel Beckett bridge, and inside an area of Dublin that was an interesting mix of old and new. Many fresh new buildings stood next to those that looked like they were built in the early 1800s (or earlier). the Maldron Pearse is an older hotel, but undergoing some modernization. For the first time in awhile, I was hit with what it would cost to have WiFi service as a separate payment, and so I agreed to do so the first night, but not thereafter (worked out to being close to $20 a day!). Another factor that took a little getting used to is the latitude. At this time of year, sunrise wasn't until 8:00 a.m. and sunset happened just before 4:00 p.m. Also, though it was chilly in the mornings and the later evenings, it never felt frigid. I was able to make do with regular street clothes and a light snowboard jacket most days (it mostly stayed in the 40s F).

Day two covered a lot of ground. It would be the one full day end to end, so I made sure I was actively engaged in each session. My comments of day two can be seen here.  Additionally I took some time to check out the Test Lab and see some of what they constructed and how they were encouraging participants to get involved. Outside of that, I will confess to walking over to chat with some friends over at SmartBear, but I spent very little time in the expo itself. If there was any one thing I was able to take away from the conference (and this may come down as blasphemy to some) it's that the tools and the peripheral software rarely solves the real issues facing a company or an initiative. there are so many issues that are more important to focus on up front that, frankly, if your biggest problem is that you don't have the right CRM solution or you need a different test management suite, I'll be frank, you're probably doing awesome.

For me, the bigger view was the fact that, even in Europe, the problems tend to be universal. They are issues with communication, with culture, with hiring, with getting a disparate group to mesh. In fact, if there was any one takeaway that I could sum up from this conference, it would be the fact that we are focusing a lot of attention on "physical diversity" (which is great, do not get me wrong, and I'm happy to see that happening), but we are still failing at recognizing the "emotional diversity" that our teams carry. We can do everything right on the hiring front as far as the gender, ethnic background, and sexual orientation, and yet we can still build teams that are remarkably homogeneous, because we tend to hire people like us, all external aspects considered and factored out. Getting a truly diverse team means you have to go into harder areas to quantify, such as emotional connection, communication styles, verbal and written expression, analytical and creative thinking, and being willing to be fluid with roles and responsibilities. Seriously, good luck getting a software tool to help you with that.

One of my favorite aspects of any conference is the ability to meet people I've never met before, but have had some communication with through other mediums. Software testing has taken to social media like few other disciplines I have seen. Through blogs, Twitter, Facebook, Quora and other initiatives I participate in, there are so many software testers that I "know" but hadn't met in person. This event really drove home how many people "knew" me, by reputation, by prose, by initiatives I have been part of. I was able to meet someone in person for the first time and realize they knew a tremendous amount about me, about how I think, and about how I communicate. It was a thrilling feeling, and at time, I will confess, a little unsettling. Granted, I opened up myself for that by having a blog and a presence in social media, but I never quite get used to the feeling when I am talking to someone and looking to explain how I feel about an issue, and them answering that they already know how I feel about it, they'd read my comments on it just last month. Still, I really appreciate that so many people actually tune in to what I have to say, it's really humbling.

Our evening entertainment for Wednesday was an awards dinner and reception at Croke Park, which is the home to the Gaelic Athletic Association and what are the two national sports (outside of football) for the Irish; Hurling and Gaelic Football. Before this evening, I had no idea how big a deal these two games were in Ireland, and seeing the history, the names, and the highlight reels certainly drilled that point home. Croke Park Stadium felt huge to me. I cannot say whether or not it was the size of our American Football stadiums back in the states, but it certainly felt like it. Having had a wonderful night of conversation with friends old and new, a very filling traditional irish dinner, and some deserved awards (knowing that Rickard Edgren won the best paper award put it at the top of my list for items to review when I got home), the buses brought us back to the convention center, and we all made our way back to the comforts of our rooms, to sleep and prepare for another day.

For my final full day in Dublin, we took part in Day Three of the conference (all of which from my perspective can be read about here), and several talks that, again, deal with the real issues that teams face. Again, I will emphasize, the problems with software and products that ultimately fail are less to do with technology and tools, and more to do with people and interactions. Unless we get that part right, ultimately what we do on the product front will be less effective than it can be. Additionally, we all need to realize that the problems on the people front are the hardest to solve, and take the most time, talent and energy. I appreciated very much Shmuel Gershon stepping in to do a last minute keynote (which he did a fantastic job with) and Zeger Van Hese's closing keynote about the interconnectedness of everything we do. I also have to thank Zeger for giving me a term that has become very looming in my reality (Tsundoku), and a fighting desire to do something about it :).

After the closing keynote, we had a session that was about programming for testers. While I have had some experience with programming, I often appreciate these workshops because I like to see how they go from zero to sixty in however long it takes, and what we walk away with in the process. For me, I walked away with a free IDE I'd never used called Geany, and some quick and dirty tips as to how to get people who had never programmed up with some quick wins and the desire to keep going. My intention is to use the same ideas as I pair program with my daughter in the coming weeks. Geany seems a good tool to do what I am hoping to.

Our final night together had a bunch of us making our way over to St. James Gate, with a tour of the Guinness Storehouse, and a museum dedicated to what is quite possibly the most iconic of Irish products. The tour was a great deal of fun, with a lot of history, some insights into a nearly 300 year old company, and what they have done to remain both profitable and relevant. Some good lessons overall in the tenacity of vision, and the willingness to play the long game (they have as one of their fist exhibits a document that is a 9,000 year lease for the St. James Gate property. Now that is long term thinking!). After a lesson in how to "pull the perfect pint from a nitrogen tap" and some breathtaking views from the top of the storehouse in the Gravity Bar, we went to get some dinner and continue the conversations in Crown Alley at one of the beter known and packed full pubs, where I was able to get an Irish translation of an American Thanksgiving dinner (which was quite enjoyable, I have to say :) ). A little walking around, and a little more conversation, then came the realization that there would be an early morning cab ride to the airport, some more waiting, and a long stretch to get home. I took my leave and got a couple of hours of shuteye, then packed up, got into a cab and made my way to the Dublin Airport.

A quick note on people in the States who complain about how much things cost. I found myself regularly doing the mental conversion of typical meals, costs for cabs, general purchases for items, etc. and I can honestly say that Ireland (or at least Dublin) has a higher cost of living than I do in my home town. I could chalk it up to being in touristy areas, but overall, I was still surprised at the costs of many items that I get for much less back home. Traveling to other parts of the world always opens ones eyes, and lets them understand the differences, even in little things.

The flight home I knew was going to be long. I'd have a seven hour layover in Toronto, as well as an almost seven hour flight from Dublin to Toronto, and a six and a half hour flight from Toronto to San Francisco. Interestingly, with my battle plan in force (reading through my collection of e-books and taking notes) coupled with the time it took to go through Immigration and customs in Canada (which to my surprise, meant I had no visit with customs in the U.S. when I arrived back home), those seven hours went much faster than I anticipated. The flight from Toronto to San Francisco, honestly, I slept most of the way. I landed just a little after 11:20 p.m. and by the time I walked into my house at two minutes to midnight (cue Iron Maiden in the background ;) ), I had spent twenty seven hours traveling door to door. Needless to say, I spent most of the weekend recuperating and getting myself back onto Pacific Standard Time. Today, I feel like I'm mostly back to normal.

To the organizers of EuroSTAR, I wish to say thank you for inviting me to your conference, and for giving me a free conference pass as "The Green Tester". It was an interesting situation to be a Yankee abroad, and to realize that I was one of the few people from the U.S. at this event. To hear so many different accents, so many different stories and situations, and to feel a part of a slightly bigger world, I am grateful for the experience. Additionally, to be a delegate without any other obligations, without having to speak, work a booth, do some background work, or other involvement that I have done the past five years, it was a terrific experience to just be at liberty to seek out and find answers to my own questions. In many ways, I did just that. For several questions, I didn't find answers, but I did find new avenues to explore and consider. I'd say that makes for a successful week :).