• About
  • Giving Back

aclairefication

~ using my evil powers for good

Category Archives: Lean Coffee

Organizing meetups

03 Friday Mar 2017

Posted by claire in Approaches, Context, Experiences, Experiments, Lean Coffee, Protip, Retrospective, Social media, Soft Skills, Software Testing Club Atlanta, Speaking, Training, Unconference, Volunteering

≈ Leave a Comment

Announcing Ministry of Test Atlanta

Last fall was the last of our Software Testing Atlanta Conference (STAC) events. An attendee at my Intentional Learning Workshop chatted with me afterward. I mentioned that I have been a local meetup organizer and have struggled with how much control to retain. My attendee urged me to give the meetup back to the community and I have been pondering that ever since.

I’ve been the primary organizer of the Software Testing Club Atlanta meetup since we began as an affiliate of the UK-based Software Testing Club in October 2013. My charter has always been to serve and develop the local testing community including connecting it with the global virtual community. Not everyone agreed about including digital attendees, but I am willing to experience the friction of a virtual meeting to help people to attend who otherwise would not have a chance. Inclusion matters to me.

I also prefer small groups and experiential events/activities that Justin talks about. I have never had a goal of increasing the size of our meetup beyond what a single facilitator could manage in a workshop.

STAC was just a bigger extension of the meetup for me. I always wanted to reach more people in the local community, so putting together a conference focused on my geographic region was a great chance to bring new local voices to the fore. I never wanted it to be a big formal event, so I’m working on an ATL software testing unconference for the fall: shortSTAC. More on that to come!

This has been an awesome ride over the last 3 years, but we’re re-branding and branching out into our very own Meetup now known as Ministry of Test Atlanta!

Please join us to keep up with our events!

 

As part of our reboot, I wanted to share some thoughts on what challenges a meetup organizer confronts every month and why monthly events are so difficult to sustain!

Meetups are tough for reasons

 

1. Location, location, location!

People interested in testing are spread out across ATL and traffic suuuuuucks. Plus, I have no budget, so someone has to be willing to host for free or sponsor the venue fee $$. I don’t want to hold the meetup only in one part of the city since that alienates interested test enthusiasts. Proximity to public transit is something I’m not sure matters, but it would make the meetup more accessible to more testers.

Over the past 3 years, we’ve had completely different crowds depending on which part of the city we chose. I preferred to rotate locations to give everyone some opportunity to attend, even though that introduced uncertainty that probably negatively affected attendance… It’s impossible to make the “right” choice for everyone who *might* attend…

Anyway, I work at VersionOne now and that means I can host, so that’s one variable taken care of!

2. Scheduling

We hold meetings on weeknights assuming that people are more likely to do work-related things on workdays – and would be more reluctant to give up their weekend fun time to work-ish things. Getting all of the stars aligned to schedule these meetups monthly *and* give enough time for people to RSVP and then work out the logistics of showing up… Timing is hard.

Since we tend to meet after work, providing food and drink encourages people to attend, but that’s not free… and I have no budget.

3. Funding

Food and drink cost $$ – someone has to be willing to sponsor the foodz, and drink

Possible sources of funding:

  • donations from individual attendees
  • local sponsors (probably companies)
    • I’ll have to check on company budget to see whether I can do pizza & sodas every time but I know I can do it sometimes.
  • the Association for Software Testing
  • Software Testing Club/Ministry of Test
  • or even the Agile Alliance.

4. Content

Not everyone wants to present or run a workshop or host a round table or … yeah. People will show up but may not want to provide content. I have to find a willing volunteer to do it for free or someone to sponsor a fee $$.

We infrequently have presentations. Most of our events are workshops or rountables or some sort of interactive experience. My go-to is Lean Coffee since it lowers the barrier to getting groups together and provides value to attendees every time.

I’m definitely interested in scheduling joint events with other Atlanta meetups in the future.

5. Publicity

How do people find out about meetings? I do the social media management, but I have no budget so … mostly word of mouth otherwise? Maybe chat rooms?

  • Software Testing Club
  • Twitter
  • Facebook
  • Google Plus
  • LinkedIn

6. Audience

I assume that most of the people who want to come to a testing meetup are testers, but not all test enthusiasts are testers. We’ve had development-types show up, so I want to keep it open and inclusive.

7. Viewpoint advocated

I refuse to insist people agree with me. I won’t call it a context-driven testing meetup or an agile testing [PDF] meetup because I want to welcome people who subscribe to other philosophies of testing. That said, I also don’t want vendor talks (and yes I work for a vendor now). This group is for engaging with ideas focusing on and around testing, not for mind-clubbing or selling or exchanging business cards. Active participation is expected and encouraged.

8. Volunteers

Organizing: While I have always had a core group of enthusiastic participants, I’ve never had a formal organizing committee. Being a one-woman-show most of the time is pretty exhausting, y’all. The meetup consumed lots of my free time. I made my professional hobby the primary thing I did for fun outside of the office for years. Um… not a sustainable model. I do not recommend it. At the same time, working with others means compromise, so consider carefully the tradeoffs and find allies who believe in your mission.

Presenting: Members of my core group have all helped out with content for the meetup – for which I am eternally grateful! I’ve also encouraged other local aspiring presenters to practice on us. Occasionally, someone I know from the wider testing community is in town and joins us to share their wit and wisdom. I resisted presenting at my own event for a long long time… until I needed content LOL

Est testing parfait?

19 Tuesday Nov 2013

Posted by claire in #testchat, Agile2013, AgileConnection, Experiments, Exploratory Testing, Hackathon, ISST, Lean Coffee, Podcast, Retrospective, Skype Test Chat, Social media, Software Testing Club Atlanta, Speaking, Tea-time With Testers, Techwell, Test Retreat, Testing Circus, TWiST, Volunteering, Weekend Testing

≈ Leave a Comment

I heard that Gerry Weinberg has an exercise called “Mary had a little lamb,” in which you analyze each word in the sentence to elicit implicit meaning that might be important. This sounded interesting enough to try, so when the opportunity came to propose a topic at Test Retreat 2013 I went for it. My topic “Is testing for me?” didn’t end up formally scheduled but made a nice interstitial topic to discuss with those milling about in the main room.

I chopped the sentence into separate words and wrote them top-to-bottom on a large sticky note. Then, instead of giving some sort of prepared remarks, I elicited brainstorming from the gathered participants. Having received interesting feedback on my professional and personal strengths at Agile2013 that had left me questioning how best to use my evil powers for good, I wanted to hear how others were thinking about the testing field and how it fit them.

The resulting scrawled notes ended up a mindmap, the path of least resistance for me. I won’t say the discussion solved all my problems, but it did give me some direction for future exploration – exploration that might also be helpful to a newbie wondering whether to pursue a career in testing.

Is testing for me?Which brings me to some interesting recent events:

  • the first ISST webinar by Ben Kelly
  • Our second meetup for Software Testing Club Atlanta
  • Randomly running across a new tester on Twitter
  • This testing blog post I read recently

I started composing a list of things I’d recommend to people just starting out as testers to help them to evaluate whether to continue. I wanted to encourage them to jump right in but also think big, not waiting them to wait 5 years to reach out to the wider world of testing (like I did).

Here’s my current list. I blogged about various experiments I tried, so you can read for yourself to see what it’s like to select what’s a good starting point for you.

  • First things first: Whatever you try, frequent retros
  • Social media, especially Twitter
  • Try exploratory testing
  • Weekend Testing
  • Chatting with other testers online
  • Books, Podcasts, Blogs, maybe even writing for some ezines or websites?
  • Meetups, local events, Lean Coffee, conferences – attend (in person or virtually), live-tweet a conference, volunteer, speak (lightning talk, whole session, workshop, tutorial)
  • Open Source, Hackathons, innovation days, etc
  • uTest/Applause? I’ve heard of this but not tried it. Seems like a lower barrier to entry/way to get started?
  • And, last but not least, who do you want to be?

No matter how many times I think I’ve found all the meaning in my testing career, suddenly I realize there are more layers… but like a parfait, not an onion.

Donkey: Oh, you both have LAYERS. Oh. You know, not everybody like onions. What about cake? Everybody loves cake!
Shrek: I don’t care what everyone else likes! Ogres are not like cakes.
Donkey: You know what ELSE everybody likes? Parfaits! Have you ever met a person, you say, “Let’s get some parfait,” they say, “Hell no, I don’t like no parfait”? Parfaits are delicious!
Shrek: NO! You dense, irritating, miniature beast of burden! Ogres are like onions! End of story! Bye-bye! See ya later.
Donkey: Parfait’s gotta be the most delicious thing on the whole damn planet! – Shrek

Thanks for the inspiration to write, EmJayKay80 and Niyi!

STC ATL Lean Coffee #1

11 Monday Nov 2013

Posted by claire in Agile2013, Approaches, Experiences, Experiments, Lean Coffee, Software Testing Club Atlanta, Speaking, Volunteering

≈ Leave a Comment

STCATLMeetup1-DotVotingOver the last few years, I have been getting to know other software testers here in Atlanta. Frequently, beginning this new acquaintance is such a positive experience that the other tester urges finding others similar to us to meet more regularly. This is such a common outcome that I am no longer surprised when first conversations end this way.

I don’t have much experience with the particulars of sifting through a large tech community for people interested in hanging out during their personal time to chat about testing software. However, when others insist on giving you a boost, it’s harder to say no.

I have demurred all these requests until now. Eventually it seemed silly to continue to turn down the genuine offers of resources, energy, and enthusiasm. I almost felt bad about denying people the community they so clearly craved. So here we are.

I love meeting new people and engaging them in conversations. However, I realize not everyone is comfortable doing that. I’ve noticed that having a structure to interactions can reduce the social barriers for those who might otherwise hang back.

At Agile2013, I noticed that Lean Coffee was an easy way to get to know a group of strangers, so I thought it would be a good place to start for the newly formed Software Test Club Atlanta.

I have participated in several Lean Coffee events run by different facilitators. I liked the simple style and frequent feedback so much that it was the first thing I brought back with me to work after Agile2013. The format proved fruitful for an internal meeting and so it seemed like a good idea for starting this local meetup.

Another good idea for starting something new is affiliating with established allies. Since one of my benefactors was part of the Software Testing Club community, I thought co-branding made a lot of sense. I led the idea of extending their brand to the United States since doing so would bring more people together worldwide than I could on my own. I wanted our nascent local group to be connected to the larger world of testing enthusiasts from the beginning. That would support the new members’ sense that each of them is not alone, the connection that drove creating this group in the first place. This is really a community building itself. I just happen to be in the center of it.

I love helping people to connect deeply with one another, so it seems only natural to put in the effort of providing the means for others to come together. Now that I work in social media, setting up channels for others to find us and join in the discussion was my first step. I want to be discoverable so that other local testers who feel the need for connection won’t have to wait so long for me to happen along.

I really appreciate that local businesses are supporting our efforts to make time to tackle difficult questions in testing and to share what we’ve learned through our professional and personal experiences. So you will definitely hear me being vocal about thanking them. I wouldn’t choose to do this alone and I’m encouraged that others think this is a cause worth the investment. I’m confident that we’re building a strong community of thoughtful and curious folks who give each other’s ideas a chance.

At our first meeting, I facilitated the Lean Coffee format since I didn’t want anyone to feel put on the spot to take over something they hadn’t experienced. Since we had 15 other in-person attendees and 3 online folks, this was a much larger group than normal. Although I recognized that groups of this size would normally split, I thought keeping everyone together would be better for cohesiveness.

We did use a simple personal kanban board. Each person had a chance to contribute topics. Due to the size of the group, each person had 3 dots to vote on which topics had priority. We established a 5 minute interval between votes to continue. Then, I added a “mercy kill” rule that after 10 minutes we had to move on to the next topic. I wanted everyone to experience the variety of Lean Coffee and knew that our topics were so complex that they could easily take over the entire time we had to meet. Those topics we still wanted to pursue went into our future meeting backlog.

As a result, we covered all of the topics that had received a vote. When items in the To Do column had an equal number of votes, I picked one to be the next to proceed to the In Progress column. Any topics we had covered sufficiently went into our Done column.

While this execution wasn’t a strict interpretation of Lean Coffee, it was a perfect adaptation to our purposes. The conversations continued after we had officially ended and people are looking forward to getting together again next month. We had lots of leftover pizza and beer, possibly because we were too engaged in the interaction to step away to enjoy the refreshments. All in all, it was a great investment of my time and I look forward to doing this again and again.

Please join us again this coming Thursday for another rousing Lean Coffee! We will have a WebEx available for virtual attendees, so tweet us to let us know you want to join in. See you then! Or on Twitter, Software Testing Club, Facebook, Google+, LinkedIn, etc

Software Testing Club Atlanta’s 1st Lean Coffee topics

  • 7 dots:
    • (1st) Who should “own” test automation? dev/test?
  • 5 dots:
    • (4th) Testing in SAFe
  • 3 dots:
    • (2nd) ATDD and/or BDD
    • (2nd) Specification by Example – getting started
    • (3rd) Exploratory testing
    • (5th) Testing in Kanban – its own column? encourages handoffs?
    • (6th) Test Manager Role on Agile Team
    • (7th) How to integrate off-shore testers w/agile teams
    • (8th) Hiring GREAT people – finding testers
    • Logic Flow Analysis and test coverage
  • 2 dots:
    • (3rd) What is breakdown of time/resources for: exploratory/scripted/automated testing (rough %)
    • (9th) Test/programmer pairing – success stories? Does it work?
    • (10th) Testing Meetups near us and around
    • Creating User Acceptance Testing
  • 1 dot:
    • Let’s get speakers! Topics?
    • What do you use to test multiple browsers?
  • No votes:
    • When to Automate?
    • What avenues do people use to find out about testing methods/tools?
    • LAWST Workshop in Atlanta?
    • Developers don’t test (?!!) (What?!!)
    • Test metrics
    • Whole team testing – good idea? How to get it working?
    • Gov’t shutdown & testing

Software Testing Club Atlanta

09 Wednesday Oct 2013

Posted by claire in Experiences, Experiments, Lean Coffee, Social media, Software Testing Club Atlanta, Speaking

≈ 1 Comment

STC-300As you may have noticed from my tweets, LinkedIn posts, Facebook posts, or chattering in person, I’m finally caving in to the peer pressure and organizing a local Atlanta, GA, USA tester meetup. Kind tester friends over at Software Testing Club have offered us help promoting and we are co-branding as Software Testing Club Atlanta. Please join us for our first Meetup on Tuesday, October 15, 2013 from 6 to 9 PM EDT. (Note: This meetup is not taking place in the UK, so sorry to all the usual STC attendees! We’re trying something new here. Also, the generated calendar appointment appears to be UK time rather than using the location’s local time. We’re meeting in the evening!)

Software Testing Club is crossing the pond to the United States! Our first Atlanta, GA meetup will be in space loaned by a tester friend, so we’re heading up to Alpharetta (center of gravity for the interested parties).

For our first meetup, our format will be a Lean Coffee, so bring your interests and ideas for discussion. We’ll explore this format and get to know each other over pizza and beer. (So I guess we could call it Lean Beer if you like…)

Illustrated guide to Lean Coffee
Lean Coffee Template

RSVP

Depending on how it goes, we will consider other formats in the future. Bring your great ideas!

Sick and Tired

03 Thursday Oct 2013

Posted by claire in Experiments, Lean Coffee, Speaking, STARWest 2013, Training

≈ 1 Comment

Brain_Drain
On the first full day of STARWest 2013, I ended up at home with my sick son. (Stomach bug. Boo.) Fortunately, most of the excitement had passed by morning and the day turned out to be blessedly restful, which was essential for this sleepy mom keeping vigil.

We rolled out of bed and sat on the couch watching a cartoon in companionable silence while I poked about on Twitter to find information on the morning’s Lean Coffee to attempt virtual attendance. Since it turned out to be a Google Hangout, my son became much more interested in paying attention, selecting various digital accessories for me – much to the amusement of the other attendees. (Son’s first Lean Coffee? Check. Wearing a digital monocle? Check. Winning at parenting? Check!)

As with any remote conferencing system I’ve ever used, the setup and logistics had their challenges, but I was happy to be included in the event in this small way. The one topic that I could clearly hear concerned sharing conference learnings after returning home.

The classic: presentation to the team.

Many people have blogged about writing – or presenting – a great trip report. Usually these start out with advice for writing your conference attendance proposal to include some language about teaching what you learn, perhaps at the prompting of your boss. At the conference, you take great notes, perhaps even writing up your report during a layover on the way home. Upon your return to the real world, still on a conference high, you set out the conquer your problems with the grand visions of a better work life only to confront business as usual… which you will somehow overcome in a single hour or two of lecturing? It’s a rude awakening. Somehow the top-down decision that the team will learn – from you. right now. – isn’t quite working out. So how do you overcome the resistance to change and really bring home useful lessons?

The subtle: solo experiments as exemplars.

A tactic I prefer is coming home with a list of things to try “on Monday” when I’m back in the office. I think of this as a series of small experiments. Matt suggests keeping these experiments isolated to your day-to-day work in order to improve results without running into the dreaded inertia of the system. As they say, big wheels turn slowly. I can certainly see his argument there since past attempts to suggest alternate approaches that radically changed others’ tasks haven’t really worked out for me. I feel a lot of ownership of my experiments and the experiences have opened up my thinking to additional new techniques, approaches, and strategies. Is your pen mightier than the the sword? Will your report really sway your audience? I certainly have tried this option in the past, but teams may find that approach tired, just one more meeting to attend.

How to bring conference learning back to the team? #leancoffee #starwest @mheusser does experiments solo. @g33klady is doing a presentation

— Claire Moss (@aclairefication) October 2, 2013

The novel: long and drawn out denouement.

The new shiny approach that I’m currently tackling is making connections among different presentations and topics to connect them in ways that seem particularly relevant to my work team’s context. My current experiment is a series of smaller presentations, complete with food and succinct snippets (the TL;DR) in emails that will link to blog posts (the deets). Gradual exposure seems better than bombarding a team with new information in a one-time brain dump. I just hope no one gets sick of my weekly missives!

I’m putting together Lunch-n-Learn presentations and weekly email/blogs to distribute. Less info dump, more learning #leancoffee #starwest

— Claire Moss (@aclairefication) October 2, 2013

As the conference delegates adjourned to attend the regular sessions, I remained sitting with my son. It might have been the exhaustion talking, but when he asked me for my mobile phone I gave in. Within minutes, he found an odd interaction (bug?) in the mobile Hangouts app and shortly afterward froze Angry Birds with a feathered missile in mid-arc. Natural born tester, I tell ya. Making his momma so proud it was easy to forget the sickness and fatigue.

Update from this morning’s Lean Coffee!

Going to use #LeanCoffee as the way to share what I’ve learned at #starwest with my team

— Hilary aka H-Bomb (@g33klady) October 3, 2013

 

Image source

♣ Subscribe

  • Entries (RSS)
  • Comments (RSS)

♣ Archives

  • October 2019
  • September 2019
  • August 2019
  • March 2019
  • February 2019
  • November 2018
  • August 2018
  • June 2018
  • May 2018
  • March 2017
  • August 2016
  • May 2016
  • March 2015
  • February 2015
  • February 2014
  • January 2014
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • May 2013
  • April 2013
  • February 2013
  • December 2012
  • November 2012
  • October 2012
  • August 2012
  • July 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011

♣ Categories

  • #testchat
  • Acceptance Criteria
  • Agile
  • Agile Testing Days USA
  • Agile2013
  • Agile2018
  • AgileConnection
  • Approaches
  • Automation
  • Better Software
  • CAST 2011
  • CAST 2012
  • CAST 2013
  • CAST2016
  • Certification
  • Change Agent
  • Coaching
  • Context
  • DeliverAgile2018
  • Design
  • Developer Experience
  • DevNexus2019
  • DevOps
  • Events
  • Experiences
  • Experiments
  • Exploratory Testing
  • Hackathon
  • ISST
  • ISTQB
  • Lean Coffee
  • Metrics
  • Mob Programming
  • Personas
  • Podcast
  • Protip
  • Publications
  • Retrospective
  • Scrum
  • Skype Test Chat
  • Social media
  • Soft Skills
  • Software Testing Club Atlanta
  • Speaking
  • SpringOne2019
  • STAREast 2011
  • STAREast 2012
  • STARWest 2011
  • STARWest 2013
  • Tea-time With Testers
  • Techwell
  • Test Retreat
  • TestCoachCamp 2012
  • Tester Merit Badges
  • Testing Circus
  • Testing Games
  • Testing Humor
  • Training
  • TWiST
  • Uncategorized
  • Unconference
  • User Experience
  • User Stories
  • Visualization
  • Volunteering
  • Weekend Testing

♣ Meta

  • Log in

Proudly powered by WordPress Theme: Chateau by Ignacio Ricci.