• About
  • Giving Back

aclairefication

~ using my evil powers for good

Category Archives: Soft Skills

Work Horde, Play Horde

02 Monday Sep 2019

Posted by claire in Coaching, DeliverAgile2018, Events, Experiences, Experiments, Mob Programming, Protip, Publications, Soft Skills, Speaking

≈ Leave a Comment

I recently hosted a Magic-the-Gathering-themed tween party for 8 players.

Yes, you read that correctly. 8 players in a format I later learned is called Free-for-All (a.k.a. Circle). Little did I know that most MTG games were smaller, with an “epic” game being maybe 6 players… 🤦

While my husband did some excellent turn-based coaching for the new players – about half of the assembled – I noticed something essential was wrong. The kids were disengaged from the game unless it was their turn to play. Considering they’ve been rabid Pokémon fans, I couldn’t understand how they could completely check-out from a “grown up” monster beatdown game…

Then it dawned on me: the turn rotation was too long. The kids had enough time between turns to be restless from the sugaring-up and general high energy of being together outside of school.

This distraction is the same issue that I’ve seen with attempts at mob programming!

For any reasonably sized team (let’s assume <= “2 pizzas”) trying to mob program, short turns are essential. In fact, I’m not sure that group size figures into the turn duration calculation – short turns are just better!

How long is too long? For me, 15 minutes! Bias yourself to less than 10 minutes, preferably 2-5 minute turns. I’m aware that at-a-glance this feels absurd, but let me explain.

The basics of mob programming are 3+ people programming together at a single computer with 1 person directing the current activity, 1 person hands-on executing the current activity, and 1 person observing/commenting/contributing from the “mob” crowd seated around the computer. (In some descriptions, the “mob” may also be considered as part of directing the activity, but 1 person makes the decision about what to do/try next, so I prefer to differentiate between these roles.) Unlike strong-style paired programming, these roles are insufficient to be mob programming: for a mob, you must also have rotation!

As “circus performers” (a.k.a. mob programming facilitators) for Bryan & Bill’s Three-Ring Design Circus at deliver:Agile 2018, my pair Tim Ottinger and I instituted a 5 minute rotation schedule for our mob of conference session attendees (read: strangers). Our task was test-driven development (TDD) and refactoring of a sample programming project.

Short rotations encouraged:

  • low barrier-to-entry experimentation with TDD and mobbing
  • selecting and trying an idea quickly
  • refining communication patterns
  • collective ownership of goals
  • fast feedback

Tim and I were a bit more merciful with our 5 minute rotations in that we encouraged participants to continue the execution of the previous driver where another “circus performer” insisted on a fresh start (read: deleting code) when TDD automation wasn’t passing/green at the end of a 2 minute rotation (the hard-core strategy of one of our other performers). So much excitement!

In the workplace, over the years, I have participated in pseudo-mobs wherein a single programmer or a pair of programmers consult another team member on particularly challenging aspect of a programming problem. Often, this results in another programming team member chiming in with insight or advice and now we have an amorphous gathering around a single programming work station where the work is being implemented. This is even more likely when the consulted team member is also paired programming (i.e. 2+ pairs collaborating on a complex issue in the code).

While pseudo-mobs definitely help with resolving an issue, we miss out on some of the benefits of the mob structure:

  • explicit statements of intent through navigator-driver pattern
  • everyone having hands-on time implementing a solution
  • everyone directly participating in the decision-making and experimentation
  • single piece flow / avoiding merge conflicts (since only 1 unit of work in-progress)
  • novice or new team members developing shared understanding and receiving training opportunities from the explicit exchange of multiple points of view and potential solutions

Now back to the Magic game! Upon reflection, how would I have changed the game play to optimize for faster turns/better rotation?

The common wisdom seems to be smaller groups for quicker decision-making and turn progression, e.g. 2 player (1v1) games or team play (e.g. 2-headed giant, emperor).

I could also imagine a simplification of rules for younger/newer players to lower the barrier to entry…

  • Maybe removing the complexity of the “advanced topics”
  • Constructing “beginner” decks without cards that have complex abilities/rules
  • Visible structure or cues, e.g. instructional playmats for easy reference along the way

Upon further investigation, I discovered a co-operative format for MTG: Horde Magic!

All the players form a group working to defeat an automated “horde” deck. The team members all take their turn together to attack and block. (This reminds me a lot of the mob programming format with a product team assembled to “defeat” a difficult software problem.)

In Horde Magic, if some aspect of game-play isn’t fun or isn’t working well within the rules, the team members come to a consensus as to what works best for them. (The mob can iterate on their working agreements as they work through the problem in order to work more effectively together.)

Given what I know so far, I’m looking forward to trying some new things, both at work and at play. Having a good mobbing experience takes a bit of planning and some skillful facilitation, but it’s the game for everyone!

Attending to networks

06 Tuesday Aug 2019

Posted by claire in Approaches, Change Agent, Coaching, Context, Experiments, Soft Skills

≈ Leave a Comment

Martin Grandjean [CC BY-SA 3.0 (https://creativecommons.org/licenses/by-sa/3.0)]

I have been following Esther Derby with interest for years. I find her wise counsel refreshing and I admire her ability to connect deeply with attendees at conferences and training sessions. You can imagine my excitement upon finding her new book 7 Rules for Positive, Productive Change in my mailbox!

I sat down that evening and applied my customary approach to getting the lay of the land: starting with the index and moving backward to the table of contents. I had one major problem: I kept getting caught on helpful diagrams and interesting anecdotes. Still, I managed to charter a line of inquiry that led me to deep-dive in several parts of the book: networks of relationships in organizations and how they influence the success of change. I didn’t realize how long I’d been at reading up on Rule 4 until I looked up to see it was past midnight!

I love the idea of change by attraction. Change that people want to be part of is the kind of change I want to be an agent of. As I’ve previously written, I have sometimes seen an attitude of “not invented here” that corresponds to the “It won’t work here” argument that Esther’s approach debunks. Experimentation within the walls produces examples of what can work in this context.

I agree with a heuristic approach to figuring things out, so I wondered about the “rules” part of this book’s title. Happily, Esther recognizes that these rules are for “learning and problem-solving, especially when a bit of trial and error is involved… when there isn’t an obvious path.” Accordingly, I found helpful heuristics to guide my questioning when trying to understand how to help others with change.

In particular, I’ve become quite curious about the informal networks that quickly spread ideas, the people “whose opinions are trusted and respected and whom people go to for advice.” I couldn’t help geeking out about the graph theory aspects of the organizational network analysis (ONA), but strategies to “reshape the network to make it more useful both for sharing information about the teams and for sharing ideas and expertise” really got my attention. So I ordered a spare copy of this book to share with my local network.

I’m already thinking up different experiments that I might try to increase information sharing and connectedness of communities, both at work and among professional contacts. Now that my initial investigation has been fruitful, I’ve switched to working my way methodically through each page of the 7 Rules for Change and it’s helping me to sort out and prioritize those potential interventions. Providing more serendipity and more informal opportunities to connect with each other matters to me – and I’m so glad to have Esther’s insights to help guide my exploration. As she says, “Heuristics point a way, and methods and models guide action.”

Minimum Viable Product Manager

29 Wednesday Aug 2018

Posted by claire in Agile, Agile2018, Approaches, Context, Experiments, Metrics, Protip, Retrospective, Scrum, Soft Skills, Training, User Stories

≈ Leave a Comment

At Agile2018, I attended Richard Seroter’s Product Ownership Explained session, where I heard about bad and good product owners. Product ownership/management has many facets including

  • advocating processes and tools
  • style of leadership
  • customer interactions
  • relationship with engineers
  • approach to continuous improvement
  • product lifecycle perspective
  • sourcing backlog items
  • decomposing work
  • running through a sprint
  • meeting involvement
  • approach to roadmap
  • outbound communication

Now I’ve been working alongside many customer proxy team members (e.g. business analyst, product owner, product manager) over the years. I’ve learned how to create testable, executable, deliverable user stories in a real-world setting. I wasn’t going into this talk blind. I just haven’t always focused on the Product role.

This time, I looked at the role with the mindset of what it would take for me to check all the boxes in the “good” list. As each slide appeared, my list of TODOs lengthened. I started to feel overwhelmed by the number of things I wanted to improve…

“How you doin’, honey?” “Do I have to answer?!?”

I walked out of that talk thinking I’m not sure I want to sign up for this epic journey. The vision of the idyllic end state was more daunting than inspiring. How could I possibly succeed at this enormous task? Would I want to sign up for that? My initial reaction was no! How could I take on all the technical debt of stretching into a new role like Product? How long would the roadmap to “good” take?

Analysis

When I evaluate things off the cuff, I often consider good-bad-indifferent. Maybe knowing what “good” and “bad” look like wasn’t helping me. I knew I didn’t want to be merely “indifferent”… maybe what I really wanted to know was this:

What does a minimum viable product manager look like?

One of my big takeaways from Problem Solving Leadership (PSL) with the late, great Jerry Weinberg was limiting work in process (WIP) or “one thing at a time” (as close to single piece flow as possible) improves effectiveness. If I take that approach to a PO/PM role, I’m afraid that I would completely fail. So I will reduce the practices to as few as I possibly can without completely losing the value of the role. I want only the *critical* path skills or capabilities! Everything else can be delegated or collectively owned or done without. So what can I discard?

In this thought experiment, I’m proposing finding the least possible investment in each essential aspect of the PO/PM role that would move from bad past merely indifferent to viable (but only just!). I needed to reduce my expectations! If I allow minimum viable to rest somewhere in my default scale, then it fits between indifferent and good. That means I deliberately do *not* attempt to inject all of the good practices at once. So let’s revisit the axes of expertise and the lists of behaviors that are good and bad…

What’s the least I could do?

Decomposition

Advocating processes and tools

Good: contextual & explanatory & collaborative (fitting process to team + pragmatic tool choices + only important consistency + explains process value + feedback leading to evolving)
Minimum viable: pragmatic minimalism (choose a simple process & let practices earn their way back in as value is explained + choose an available tool + allow consistency to emerge + request feedback)
Indifferent: status quo (follow existing process/ceremony w/o questioning + let others choose tools + don’t justify)
Bad: dogmatism (one practice fits all + adhere to ceremony + prescribed toolchain + standardization + trust process + don’t justify)

Style of leadership

Minimum viable: leads by example (models behaviors for others without trying to modify their behaviors) + doesn’t worry about respect + consultative decisions + experiments/loosely decides + sometimes available to the team but not constantly + flexible + defaults to already available metrics

Customer interactions

Minimum viable: meets with customers at least once + builds casual relationship with a key customer + gets second-hand reports on Production pain + occasional customer visit + default information sources

For me, this one slides a bit too far toward indifferent… I’m not sure how little I could care about customers and still get away with being acceptable at PO/PM…

Relationship with engineers

Minimum viable: physically co-locates when convenient + T-shaped when it comes to the technical domain (i.e. aware but not trying to develop that skill as an individual contributor) + attends standup + shares business/customer/user information at least at the beginning of every epic + champion for the product & trusts everyone on the team to protect their own time

Approach to continuous improvement

Minimum viable: default timebox + takes on at most 1 action item from retrospective, just like everyone else + plans on an ad hoc/as needed basis (pull system) allowing engineers to manage the flow of work to match their productivity + prioritizes necessary work to deliver value regardless of what it’s called (bug, chore, enhancement, etc)

Product lifecycle perspective

Minimum viable: tweaks customer onboarding in a small way to improve each time + cares about whole cross-functional team (agile, DevOps, etc) + asks questions about impact of changes + allows lack of value in an existing feature to bubble up over time

Sourcing backlog items

Minimum viable: occasionally talks to customers + cares about whole cross-functional team (including Support) + backlog is open to whole team to add items that can be prioritized + intake system emerges + tactical prioritization

I do have twinges about the lack of strategy here, so I guess I’m looking at this part of minimum viable Product *Owner* (i.e. the mid-range focus that Richard points out in his 10th slide).

Decomposing work

Minimum viable: progressive elaboration (i.e. I need to know details when it’s near term work and not before) + thin vertical slices and willing to leave “viable” to the next slice in order to get a tracer bullet sooner + trusts the team to monitor the duration of their work & to self-organize to remove dependencies (including modifying story slicing)

Running through a sprint

Minimum viable: doesn’t worry about timeboxes (kanban/flow/continuous/whatever) + focus on outcome of each piece of work (explores delivered value) + releases after acceptance (maybe this is just continuous delivery instead of continuous deployment, depends on business context)

Meeting involvement

Minimum viable: collaborates with team members to plan as needed (small things more often) + participates in retrospectives + ongoing self-study of PO/PM

Approach to roadmap

Minimum viable: priorities segmented by theme + roadmap includes past delivery/recent accomplishments + adjusts communication as needed/updates for new info + flexible timeline in a living document + published roadmap accessible to all stakeholders on self-serve basis

Outbound communication

Minimum viable: allows org to self-serve info + shares priorities with manager & customers + environment for continuous self-demo/trying features + transparency

What are the minimum viable versions of the tools of a product owner?

  • Backlog – list of ideas not fleshed out until it’s time to run them
  • Sprint planning – ad hoc meetings in a pull system initiated by the need for work definition to execute
  • Roadmap – technical vision of system capabilities + compelling story of the product value proposition
  • Prototyping, wireframing – whiteboard pictures + text-based descriptions
  • Team collaboration – a big TODO list that everyone can access
  • Surveying/user testing – chat program that both team & user can access
  • Analytics – NPS score informally collected from customer conversation
  • Product visioning – I think this goes in with Roadmap for me?

So I’ll agree that the PO/PM role is critical and necessary. I would like for creative problem solvers to fill the role – and to be fulfilled by the role! In order for that to be viable, for people to grow into a Product role, there needs to be education on how to begin – and it can’t be spring-fully-formed-from-the-head-of-Zeus! Christening someone PO/PM doesn’t endow them with sudden wisdom and insight. Skill takes time to develop.

Set realistic expectations for beginners. Help teams to welcome people to grow in the role by offering both challenge and support from all the team members. As with any team need, the agile team has collective ownership to solve the problem, not relying on a single point of failure in the role specialist. Having a beginner PO/PM is an excellent time to reinforce that!

Don't worry, people. I so got this!

If I were a Product Manger, I would definitely prefer to be a full-featured representative of that specialization! However, I encourage you to revisit Richard’s presentation and do your own decomposition of the Product role. What is absolutely essential? What can you do without?

What is *your* minimum viable Product Manager?

Agile Testing Days USA links

27 Wednesday Jun 2018

Posted by claire in Agile, Agile Testing Days USA, Approaches, Coaching, Context, Experiences, Experiments, Exploratory Testing, Podcast, Publications, Soft Skills, Speaking, Training

≈ Leave a Comment

Refactoring Test Collaboration from Claire Moss

Here are some resources we’re using in my Agile Testing Days USA workshop Refactoring Test Collaboration

Slides

Abstract

Collective ownership for testing starts with understanding testing. Rework your team dynamics to evolve past duplication and improve performance through whole team testing. Take home practical patterns for improving your team’s collaboration on testing. Because teams who own testing have more confidence in the customer value of their results.

As the Pragmatic Programmers say, “refactoring is an activity that needs to be undertaken slowly, deliberately, and carefully,” so how do we begin? In this session, we will experience the complex interactions of an agile team focused on demonstrating customer value by answering a series a questions:

  • Where do testers get their ideas?
  • How are you planning to accomplish this proposed testing, tester?
  • Why not automate all the things?
  • Who is going to do this manual testing and how does it work?
  • How do we know whether we’re testing the right things?

Build your own list of TODOs from these various practical collaboration approaches and begin deduping your team’s testing for a better first day back at the office.

Key-Learning

  • Approaches to handle objections to executing the testing work
  • Ways to mentor test helpers, including pairing
  • Investing in testing the team believes in
  • Understand how other team members have been testing the work so far
  • Advising on opportunities to inject test thinking into all of the team activities, from story writing through to unit testing, to make the system more testable

Resources

Refactoring

Collaboration + failing at collaboration

WHOSE testing skills + Exploratory testing + Elisabeth Hendrickson’s Test Heuristics Cheat Sheet [PDF] + book Explore It!

Agile Manifesto

Walking Skeletons, Butterflies, & Islands + my blog post elaborating on the conference

Big Visible Testing + my blog post elaborating on the presentation

Testing pyramid + critique of the testing pyramid/alternatives

Extreme programming lifecycle

eBook: Katrina Clokie’s A Practical Guide to Testing in DevOps + Role mapping

Westrum model + organizational culture & safety

Linda Rising’s change patterns & books on Fearless Change

Deployment pipeline

High Performance Practices [PDF] + book Accelerate

Continuous Testing

Empathy-Driven Development + empathy practices

Many interactive aspects of my workshop were inspired by Sharon Bowman’s book Training From the Back of the Room

facilitation book Collaboration Explained

metrics book Measuring and managing performance in organizations

book Testing Extreme Programming + some follow-up thoughts

Soon to come! Claire Moss on Let’s Talk About Tests, Baby podcast

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

Coaching and Coffee

24 Tuesday May 2016

Posted by claire in Approaches, Coaching, Experiences, Experiments, Protip, Soft Skills, Training

≈ Leave a Comment

coffee-coachOne morning, my office had a fancy coffee machine delivered. The machine was fancy enough that we had training sessions to learn how to use it. The machine’s controls involved a few pre-programmed settings for common usage scenarios. Not being a coffee drinker, I didn’t appreciate the intricacies of preparing a morning cup, so while I was interested in the training it was not particularly relevant for me. I just wanted to know where to get the hot water to brew my tea.

Then, we had a local barista Joseph Yancey join us for a morning of coffee coaching. It was his day off, but he loves the artistic aspects of preparing coffee and wanted to share that with coffee lovers. The coffee machine was still somewhat intimidating to me since I didn’t know how to judge the results of the preparation process. Out of curiosity, I hung around to listen to what the barista had to say.

Co-workers arrived at the office and were ready to start their day. They joined us in the break room and gathered around our visitor. Instead of expounding about the principles of great coffee and the brews and mixtures he preferred, Joseph focused on helping individuals to achieve their goals.

As each person explained the kind of outcome they were looking for, he was very patient in coaching. He noticed the intimidation of trying something out of the ordinary and reinforced the idea that no one should be concerned about failing to produce exactly what they hoped for. Instead, he emphasized making better and better approximations of the desired result to accomplish incremental progress. This created a safe space for individuals to develop new skills.

Each person explained what they wanted and he told them how to refine their techniques. He showed them motions with his gestures and posture as a model but he didn’t take over. Each pair of hands became surer by trying for themselves the motions and mixing. He paired with each participant and brought attention to key moments and opportunities during the process without talking down to anyone. Rather than doing it for them, as he expertly would during his day job, he coached them into greater competence and self-reliance.

I noticed his consummate skill in interpersonal interactions and asked him about it. He said that his love for his craft motivated him to help others to greater mastery. When I mentioned that I wasn’t in his core demographic (as a tea drinker), he was willing to tackle that problem as well, teaching me how to judge the heat of the water produced by an electronic kettle so that I could pair it with the various mixtures with more demanding brewing precision. Even I, an edge case, benefited from Joseph’s enthusiasm and understanding.

Now that’s a coaching experience to start your day off right.

Perception and Certainty

27 Friday Feb 2015

Posted by claire in Approaches, Context, Design, Experiences, Experiments, Soft Skills, Testing Humor, Training

≈ Leave a Comment

A funny thing happened today at work. I found out that some of my colleagues literally see things differently. Many of us found ourselves surprised by what others perceived to be true about something as simple as an image. We were swept up in #dressgate: a raging internet controversy about a photo of a dress and its colors.

I’m on Team Blue and Black. However, I wanted to see how the other half lives. I tried various ways to see white and gold: viewing the image on different devices, changing screen brightness, angling the screen, walking around in different ambient light. The various experiments all produced the same results. Trusting my perceptions, I could not give any credence to the perspective that the dress was a different pair of colors, despite seeing many online posts to that effect.

I mentioned this to my team at work, only to discover that there were others who had no idea anyone disagreed with them. As a member of Team White and Gold, my team’s designer was surprised to hear there was a Team Blue and Black – as surprised as I was. 🙂 I couldn’t help wondering whether she was expecting a covert camera to emerge as part of some elaborate prank.

Fortunately, working with designers means having deeper organizational knowledge about colors. By the time lunch rolled around, another colleague had created an online tool for experimentation with the image to see for ourselves how image manipulation would change perception. Another designer mentioned that he had sampled the original image to identify the colors and then created swatches of the colors perceived by others to overlay the image in order to show both positions contrasted with each other, explaining about the impact of shadows and subtle colorblindness.

Designers FTW!

Designers FTW!

Then, he suggested another avenue of investigation: flash blindness. In flash blindness, a bright light bleaches (oversaturates) the retinal pigment resulting in sudden vision loss that doesn’t immediately return to normal, but it usually wears off gradually. So my team devised an experiment to expose our designer’s eyes to a bright white lightsource: a blank page on a screen. When she quickly switched from the bright white background to the original dress image, she was able to see blue and black coloration. However, after a few moments, when she glanced at the dress image again, her retinas had recovered and she saw the original white and gold pigments. This was consistent with reports from other online posters who mentioned scrolling down the page and then being able to see different colors. This transient state seemed to be a source of great consternation and some panic.

While this was a fun way to spend our lunch hour, it was also a great opportunity to practice some of the problem-solving skills I learned at last year’s Problem Solving Leadership workshop:

  • Experimenting to gather information – Although I was not able to see the white and gold version of the dress without manipulating the image, I learned new ways that didn’t work.
  • Perceptions, What’s true for you – I felt quite certain about the stability my own perceptions after looking at them from various angles
  • Watch how other people are behaving – While I thought it was quite surprising that many others had such completely different perceptions, I did not assume they were wrong just because I couldn’t observe the same things.
  • Be cautious about not noticing – I gave others the benefit of the doubt knowing that I can bias myself to ignore information sometimes.
  • How to take in info – I looked for a variety of sources of information about the disparate points of view to obtain a balanced set of data.
  • Resisting information – I paid attention to reports of heated arguments between people from the different viewpoints, noticing the emotion involved in what seemed like a purely factual question.
  • Motives (test interpretation, seek intent) – I asked two observers from Team White and Gold questions since they could see what I could not
  • Reading minds – I tired not to assume that anyone was punking me or simply being ornery but instead was open to the possibility of being wrong.
  • Style vs intent (make more congruent) – Rather than trying to convince anyone of my point of view, I listened to their experiences and observed their learning process.
  • Social structures – It was interesting to see that even within the design group there were opposing assessments of the information. I also saw how team members collaborated rather than confronted each other when trying to understand where each was coming from.
  • How do you get people to recognize what you saw? – I waited for an opportunity for them to experience it directly and shared the information that I had so the other team members could judge for themselves, now that they had more to work data
  • Show you care by speaking up – I could have ignored people who didn’t agree with me, dismissing their viewpoint as simply wrong. However, engaging in dialogue was a great team-building experience and helped to establish more common understanding.
  • Reactions – By giving myself a charter of observing others’ behavior, thought processes, and evidence, I was better able to empathize with what was a shocking experience from their point of view.
  • Eyes open! Use your senses – I took suggestions from the designers about resources for assessing color perception and did not assume that I could gather unbiased information. In the end, I know more about myself than I did when this silly discussion started.
  • Learn from others – I certainly know more about color, perception, troubleshooting, experimentation, and these particular colleagues than I did before I posted the question “What color is this dress?” so I call today a win. 🙂
  • Aaaaand I couldn’t help trolling just a little bit by “wearing the colors” today…

Blue-Black or White-Gold?

Blue-Black or White-Gold?

 

Potty training

29 Wednesday Jan 2014

Posted by claire in Experiences, Experiments, Protip, Soft Skills, Software Testing Club Atlanta, Testing Games, Training

≈ 1 Comment

STC ATL Dec 2013 MeetupMy first experience with testing games was back at my first testing conference when Michael Bolton gave me a testing challenge at lunch: a rubber ball. I didn’t know what I was getting into, but I knew I loved games. And that is a key aspect of how games help us to learn: getting past our resistance by promising us fun. Since software testing is a complex mental activity, exercising our minds is an important part of improving our work.

After attending several testing conferences, I can safely say one of my favorite aspects of these gatherings is evenings filed with testing games. (That is, games for testers, not testing video games.) Whether you’re rolling the dice (more, spoilers), deducing when a pen is not a pen, building a tower of pyramids, or shouting out “Set!” as you casually wander past, testers love a challenge.

So it was no surprise that John had his game bag already on the table when I arrived for the STC ATL holiday meetup. What I didn’t expect was Disruptus, a new-to-me game. He explained for a few minutes and then we jumped right in to playing. Almost immediately, I flipped over a card with an image of a toilet and the improve card:

Add or change 1 or more elements depicted in the card to improve the object or idea.

TMI

Skip this TMI stuff!

Since we are currently potty training at our house, this was a particularly relevant subject for me. I started rattling off ideas as they came to mind. John stopped me and said that I wasn’t coming up with new ideas but instead listing things that had already been done. While I agreed, I found that saying each of the knowns out loud helped me to clear my head for the next idea to come along.

Ideas that sprang to mind:

You know, for kids

    • toilet seat lock for babies just learning to walk
    • toddler height toilet
    • step stool for standing toilet training (boys)
    • separate lightweight plastic toddler toilet – could be portable
    • folding travel toilet seat for toddler on-the-go
    • built-in potty seat for toddler years that is easily removed for cleaning
    • moveable toddler handled seat for better balance
    • splash guard for boys potty training
    • tiny plastic urinal – I’d seen one once at a kids consignment sale
    • toilet target for potty training boys
    • soft-close lid that doesn’t slam down on little fingers
    • tie-in to children’s book/video for better motivating child (i.e. matches picture) – with audio/musical accompaniment for better motivating child
    • toilet with book rack attachment – also good for adults!
    • tie-in to popular children’s character for better motivating child
    • And of course Pinterest is awash in toilet training ideas…

Adult toilets

    • Dune’s Fremen stillsuit (okay, so that’s not real…)
    • water-conserving toilets – high efficiency, multi-flush options
    • recycling water from washing hands for next flush
    • elevated tank to use gravity for flushing
    • recently read an article about posture and advantage of raising feet using step-stool
    • bidet attachment that I saw at a co-working space
    • soft seat vs. hard seat
    • toilet scent spray that a friend mentioned to me & has ridiculous commercial
    • elongated seat
    • elevated seat for elderly with limited range of motion – vs. seat riser/handles
    • foot pedal to raise/lower the lid without using hands
    • putting the seat back down in the first place
    • self-cleaning – or at least those tablet attachments
    • germ resistant surface
    • I’d once seen a toilet with an automated toilet-seat-cover replacement system
    • I’d seen more exotic toilet options in a local farmer’s market store
    • a friend explained the composting toilet to me
    • chemical toilet/waterless toilet for big events like outdoor concerts
    • urinals – I’d seen a public outdoor urinal in Amsterdam that was just two large crosspieces for minimal privacy
    • device allowing women to stand for urination – thanks, Twitter!
    • chamberpots
    • outhouses
Things I’d never heard of
    • Glow-in-the-dark toilet seat – this would be a big hit with the kids!
    • Squat toilets
    • proximity sensor
    • toilet seat warmer – including power saving mode!
    • electric lifting seats for the elderly
    • female urinal
    • sound cloaking
    • toilet slippers
    • pretty much anything shown in Cars 2 when Mater visits the restroom

Motivation

Of course, it wasn’t until much later (esprit d’escalier) that the thing I really wanted to improve came to mind: I hate toilet auto-flush algorithms. As a happy user of toilet seat covers in public restrooms, I always feel concern about whether I’ll have to contend with a particularly sensitive hands-free toilet. Despite my years of experience, I have not yet mastered the art of evading the motion sensor while placing the toilet seat cover.

I would love to rewrite the algorithm to some set pattern of motions that would distinguish between someone leaning toward the seat to place a liner – and so avoid germs – and someone leaving the stall having completed her errand. Even clap-on, clap-off would be preferable to spray in the face from an unexpected flush.

Protip : My husband takes a 2 foot length of toilet paper and blindfolds the sensor. Manual flush never felt so good.

Training through play

So now that you made it past TMI, let’s get back to the notion of testing games for training testers. Do testing games help testers learn how to test? Many testers are making an argument for this.

John Stevenson is one of them. He uses Disruptus to encourage disruptive thinking that leads to innovation – in testing. Create, Improve, Transform, Disrupt: these 4 approaches are important when designing and executing tests. Finding new ways to remix our tests helps us to focus on things that matter but to approach them in a new way, extending our coverage of various paths and potential usage patterns. My experience with only a few turns of this game left me invigorated and encouraged to try new things at work.

How have you used games to learn about testing?

Sketching for fun and profit

17 Friday Jan 2014

Posted by claire in Agile2013, Approaches, Experiences, Experiments, Soft Skills, Speaking, Training, User Experience, Visualization

≈ 1 Comment

Have at you

As I recently wrote in Better Software magazine, I tend toward visualizing information. While this does not mean I skimp on words – as anyone who has been near me for 15 minutes can attest – it does mean that I think more clearly when I have a whiteboard in front of me and a chisel tip marker in my hand.

Ode to whiteboards

“@aclairefication: No sticky notes. No whiteboards. #FiveWordTechHorrors” this happened to me last week.

— James Grenning (@jwgrenning) December 11, 2013

 

One Christmas gifts my husband installed a wall of whiteboards in our home for the children to draw and scribble. The children loved it and happily covered it with unintelligible childhood graffiti. As it turned out, this blank wall was a greater gift to me. When I was preparing to present at conferences in 2013, I was feeling quite blocked in writing proposals and producing presentation materials until I relaxed and just let myself have time with my home whiteboard.

I hadn’t realized how much I missed having a large expanse to fill with thoughts as they came spilling out. At my first testing job, my XP development team installed a wall of whiteboard for just this sort of thing, removing barriers to collaboration by having enough space for any conversation the team needed to have. Of course, some corners were dominated by persistent big visible charts but those lasted only as long as they were needed. Yes, I was spoiled.

I decided to keep my presentations simple and sketched the images I wanted to have in my slides on this wall. It turns out taking well lit pictures of whiteboards without glare is sufficiently difficult that there are apps for that. Go figure!

Takeaways

I also realized that I would be in a fix at the conference if I didn’t have a whiteboard handy, so I scoured the internet looking for portable options. It just so happened that one of my favorite nerdy websites was advertising a foldable pocket whiteboard. One look and I was in love. I was able to easily take notes in any way I saw fit and at a scale that pleased me, not being limited to eight and a half by eleven or whatever dimensions a digital application considered adequate.

In my day-long tutorial preceding CAST 2013, on a team with people I’d never met, I wasn’t sure how to begin solving the problem, but the casualness of a portable whiteboard that could be unfolded, scribbled on, wiped away, and stowed out of the way was definitely an asset to establishing good communication from the beginning.

It also came in handy when I was able to snag a table at one of the Agile2013 social events to catch up with a speaker whose talk I had missed. He liked it so much, he bought three. Subsequently, another friend from the conference asked whether that would be a good speaker gift and I heartily assented. Now I’m wondering whether this company pays for referrals. 🙂

Drawing pictures at work? Really!

At Agile2013, in his presentation Sketch you can!, Jeremy Kriegel explained using graphic facilitation to craft meetings that better involve attendees. People can focus on visuals easily and suggest improvements. This sketching is a combination of note taking and wire framing, which is something user experience (UX) folks do routinely as part of their work. He describes trading quality of the drawing for speed in order to keep the focus on communication, then enhancing the drawing later. The focus is on the need people are trying to satisfy and understanding the context of that need.

By sharing in a concrete way, you can validate precise language and discover where meeting participants are not agreeing. The result is a public record of the conversation that can be shared. (I’ve been known to take many many pictures of whiteboards in my day.) However, the communication is more important than the deliverable, which helped to free me of my concerns about how much artistic talent I have. I felt comfortable improvising and the sketching was a sort of performance, although in the class we were not standing up in front of a group.

Earlier today, I was having a conversation with a colleague at a whiteboard and sketching the interacting parts of the problem we are testing was very helpful for focusing the conversation and revealing areas that we needed to investigate. I’m definitely a fan of drawing pictures at work and I appreciate Jeremy’s encouragement.

Sketchy people

Periodically, I rediscover Gaping Void and wallow in the talent and inspiration of these images. My most recent visit followed a tweet to his blog on new year inspiration:

I guess my “mountain” was drawing cartoons (like the cartoon at the top rightfully indicates), although it took me DECADES to find that out. – Hugh MacLeod

However, I was so drawn to his live sketching videos that I decided to give it a whirl. Not sure where to begin, I snagged a photo of my 95-year-old grandmother off a family member’s Facebook and took a shot at digital sketching. I’m pretty pleased with the result. It’s not my best effort and I’m not worried about that because it was so much fun to try.

Gma

When I’m so busy that I don’t have time to blog or read a book or play a board game, I still have time to sketch something out, however crudely drawn the result might be. I know I won’t turn into an Andrea Zuill overnight, so I keep at it a little at a time.

I’m finding that sketching on digital photos or enhancing existing images (so far no original memes!) is much much easier than starting from nothing, so that’s kind of my thing at the moment, but I’m finding the courage to stretch a bit more into original composition. We’ll see if anything comes of it. For now, it gives me something creative to do that personalizes my slides a bit more.

How do you use sketching for fun or profit?

Testing For Humans? Try Empathy

11 Friday Oct 2013

Posted by claire in Context, Experiences, Experiments, Personas, Skype Test Chat, Soft Skills, Test Retreat, User Experience, User Stories

≈ 1 Comment

sympathy-empathy
Two months ago, Matt Heusser organized Test Retreat and I attended, along with 27 other testers open to new ideas and wanting to change the world. Sound a little ambitious? Let’s find out!

My first blog post in this series is about Michael Larsen‘s Testing For Humans, which he was unable to live blog due to presenting. 🙂 However, Michael did post Alessandra Moreira‘s notes in his live blog of the event.

Fortunately, I was able to live-tweet the talk that he described as:

Testing for Humans: It’s Sticky, Messy and Very Satisfying

Abstract: Software development is a beautiful thing. We often create amazing ideas and features that would be wonderful… if only those pesky humans that end up using, abusing, and mis-understanding our brilliant code weren’t part of the equation. Unfortunately, we’re all in the business of developing software for people (yes, even when it’s machine to machine communication, it serves human beings somewhere. What are some ways that we can approach testing software outside of the theoretical ideals, and actually come to grips with the fact that real human beings will be using these products? How can we really represent them, test for and on behalf of them, and actually bring in a feature that will not just make them happy, but represent the way they really and actually work, think and act?

Expected Deliverables: An excellent debate, some solid strategies we can all take home, and some “really good” practices that will be helpful in a variety of contexts.

My take-aways were:

    • People are imperfect so ideal users aren’t enough for testing.
    • By definition, a composite of many people (e.g. user persona) is a model.
    • Too many user descriptions based on small differences is overwhelming, not practical for testing.

On Wednesday night of this week, I joined Christin Wiedemann‘s regularly scheduled Skype test chat with some other lovely wonderful tester folks and we focused on empathy in testing. We wrestled our way to some working definitions of empathy and sympathy, which was much better than shallow agreement though it took a bit of time to establish. We agreed that testers need to observe, focus on, and understand users in order to serve them better. We find that empathy for our users and passion for our testing work go hand-in-hand since we care about helping people by producing good software.

Then we struggled with whether empathy is an innate trait of a person testing or whether empathy is a learnable skill that testers can develop through deliberate practice. (Go watch the video behind that link and come back to me.) We concluded that knowing what others are thinking and feeling, getting inside their skins, in the context of using the software is essential to good testing, though this might require a bit of perseverance. This can go a long way toward avoiding thinking we have enough information just because it’s all we know right now.

As I mentioned in the chat, I’ve found that user experience (UX) design is an amazing ally for testers. One tool that helped me to develop more empathy for my users is user personas. (Later, I found that forming user personas of my product teammates helped me to develop empathy for them as well.)

I immediately took to (end) user personas as a natural progression from user stories. After all, user stories are focused on value to and outcomes for a particular group of users. Describing those users more specifically in a user persona dovetailed nicely. Rather than some sterile requirements that never name the user, identifying a role – or, even better, a rich symbol such as a named primary persona – focuses the product team’s efforts on serving someone by helping us to understand the purpose of the work we do.

We also discussed interviewing users, visits to users, and experiential exercises as techniques to help us call upon empathy when we are testing. In my work history, I’ve been fortunate to hear about my UX team’s great work in a collaborative design workshop, to contribute to designing ad hoc personas for my product, to participate in a UX-led contextual inquiry, and to log actual usability sessions led by my product team’s UX designer. (Yes, my fast fingers came in handy. Yuk yuk.) My innovation days team developed a usability logging product that evolved from an existing solution I tested/used in those usability sessions, so I was a natural fit to test it. I’m curious about empathy maps but haven’t tried them myself yet.

It’s fair to say I’m a UX-infected tester. More than fair. I identify with the curiosity I see in the UX profession and I admire the courage to kill their darlings (carefully crafted designs) when evidence shows it is time to move on. After all, we’re not building this product to marvel at our own cleverness but instead to serve humans.

Image credit

← Older posts

♣ 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.