• About
  • Giving Back

aclairefication

~ using my evil powers for good

Category Archives: Context

Story Time!

16 Monday Sep 2013

Posted by claire in Acceptance Criteria, Agile2013, Approaches, Context, Experiences, Experiments, Metrics, Personas, Publications, Retrospective, Speaking, Training

≈ Leave a Comment

Agile2013-ClaireMossAs Agile2013 considers itself a best in class kind of conference “designed to provide all Agile Team Members, Developers, Managers and Executives with proven, practical knowledge”, the track committees select from a large pool of applicants and prefer vetted content that has worked its way up from local meetings to conferences. I have only one talk that fits this criteria since I presented Big Visible Testing as an emerging topic at CAST 2012. I developed several versions of this talk subsequent to that event and doing so had given me confidence that I would be able to provide valuable information in the time allotted and still leave enough time for attendees to ask questions and to give feedback on what information resonated with them.

I worked to carefully craft this proposal for the experience reports track, knowing that if I were selected that I would have a formal IEEE-style paper to write. Fortunately, my talk made the cut and I began the writing process with my intrepid “shepherd” Nanette Brown. I wasn’t sure where to begin with writing a formal paper, but Nanette encouraged me to simply begin to tell the story and worry about the formatting later. This proved to be wise advice since telling a compelling story is the most important task. Harkening back to my high school and early college papers, I found myself wading through different but largely similar drafts of my story. I experimented with choosing a different starting point for the paper that I ultimately discarded, but it had served its purpose in breaking through my writer’s block. Focusing on how the story would be valuable to my readers helped to hone in on sequencing and language selection. Once I had the prose sorted out, I began to shape the layout according to the publication standards and decided to include photographs from my presentation – the story is about big visible charts after all!

Investing sufficient time in the formal paper made preparing the presentation more about strong simple visuals. I have discovered my own interest in information visualization so prototyping different slide possibilities and testing them out with colleagues was (mostly) fun. I’m still not quitting my day job to go into slide deck production. Sorry to disappoint!

Performance anxiety

Despite all of this preparation, I couldn’t sit still at dinner the night before my presentation and barely slept that night. I woke before the sunrise and tried to school my mind to be calm, cool, and collected while the butterflies in my stomach were trying to escape. This was definitely the most challenging work of presenting!

As a first time speaker, I didn’t know what to expect, so I set my talk’s acceptance criteria as a rather low bar:

    1. Someone shows up
    2. No one hates it enough to leave a red card as feedback

When I walked into my room in the conference center, a lone Agile2013 attendee was waiting for me. Having him ready to go encouraged me to say hello to each of the people who came to my presentation, which in turn changed the people in the room from a terrifying Audience into many friends, both new and old. I think I managed not to speed through my slides despite my tendency to chatter when I’m nervous. I couldn’t stay trapped behind my podium and walked around to interact with my slides and to involve my audience more in the conversation. Sadly, I can’t share my energy with you since I forgot to record it. Oh well. Next time!

The vanity metrics

  • At 10 minutes into the presentation, 50 people had come to hear me speak and at 60 minutes I had somehow gained another 7 to end at 57 people. Thanks so much for your kind attention! I hope I made it worth your while…
  • 43 people stopped to give me the simple good-indifferent-bad feedback of the color-coded cards (which I liked as a simple vote about a presentation) and I received 37 green cards and 6 yellow – with no red cards! Whoo hoo!

Words of Encouragement

Two people kindly wrote out specific feedback for me and I want to share that with you in detail, hoping to elicit some late feedback from attendees who might like to share at this point (Agree or disagree, I want to hear from you!)

Feedback Card #1:
– Best session so far!
– Great presenter – great information – great facilitator
– Would like to see future sessions by this speaker

Feedback Card #2:
Great Talk – speaker very endearing, Her passion for the subject matter is obvious.
A fresh perspective of how Developers and Testers should interact.
Should find ways to engage the audience

Someone else got a kick out of my saying, “I’m serious about my stickies.” and left their notes behind on the table after leaving. So thanks for sharing that. 🙂

One friend spoke to me afterward with some helpful feedback about word choice and non-native English speakers. When I was writing my talk, I was trying to focus on people who would be likely audience members, but I had not considered that aspect of the Agile2013 crowd. Since I was simply speaking off the cuff, I ended up using some words that would have fit in at our dinner table growing up but that would make for tougher translation. And yet, I got some wonderful feedback from Hiroyuki Ito about the “kaizen” he said I made. I can’t read it directly, but Google Translate assures me it’s good stuff. 🙂

uneasy truce

Finally, I discovered that my relationship with a linear slide deck is not a comfortable one. I wanted to be flexible in referencing each of the slides and having to sequence them hampered my ability to respond easily with visuals when discussing questions or improvising during my talk. I haven’t experimented with other presentation options, but I hope there’s an easy solution out there.

Image Credit

Big Visible Testing (Full Length) from Claire Moss

Always On

12 Thursday Sep 2013

Posted by claire in Approaches, Context, Experiences, Experiments, Exploratory Testing

≈ 2 Comments

FountainOfRings

So there we were, Josh Gibbs and I, enjoying our lunch break on a lovely sunny day at Centennial Olympic Park. As an Atlanta native, I was living here when the olympics came through town and have a brick in the park. We took a little stroll to visit it and then settled down by the fountain to enjoy the Fountain of Rings show that happened to be scheduled at that time.

As we sat there absorbing the novel touristy experience, trying to identify the musical strains that blared from the speakers, we started to analyze it. We couldn’t help ourselves. That instinct to see beyond the surface, to reverse engineer the system through a verbal exchange, was too powerful for us to just be in the moment. This is why we can’t have nice things.

However, as we gazed upon these new and shifting patterns of water jets set to music, we noticed a flaw in the system. One water jet was misbehaving. At first, it seemed like some sort of counterpoint to the carefully orchestrated flow, perhaps a harmony in the song that I couldn’t properly detect. As the songs changed and that jet continued to spray, it became clear that it was out of turn.

So we started looking for rules we could test to explain the behavior systematically. We speculated that the jet was always on, but when the song ended the water completely died away. We proposed that this little jet was always spraying water, always turned on but only as long as any water was emerging from the fountain. When some jets were performing but the jets around it were not active, this jet bubbled closer to the ground, but as the jets around it reached for the sky the broken jet struggled and failed to follow suit. So that rule seemed to hold.

We considered the historical context of this fountain. Constructed for the 1996 olympics, the initial design had to be created with technology available at that time. So what kind of controls were determining where the water flowed, how long the water flowed (to produce the varying effects from a water ball to a towering jet), how hard the pressure was (to provide a jet of a particular height), how quickly the pattern could change, and so on? Had the original system been maintained all this time? How would you upgrade a system like that? Was there a fixed playlist with predetermined songs and water choreography or could someone provide new inputs? If you could submit a new sequence, was it possible to hack the fountain? And if so, what was the risk involved (likelihood, impact)?

(This just in: The playlist changes and, yes, the computerized fountain accepts new inputs! “The computerized Fountain can be programmed with special announcements as well as a variety of water displays including low-pressure, walk-through “water curtains”, fog and misting.” )

I think we left with more questions than we answered, but it was still a fruitful conversation. It was a nice little trip down memory lane and forced me to confront the reality that testing is a way of life, a path that I am always on.

My stupid human trick

05 Thursday Sep 2013

Posted by claire in Approaches, CAST 2013, Context, Experiences, Experiments, Soft Skills, Testing Humor, Volunteering

≈ Leave a Comment

https://twitter.com/aclairefication/status/1011641593374347264

When I was growing up, my family and I would watch shows like America’s Funniest Home Videos that often involved montages of people showing off their ridiculous talents – sometimes inadvertently!

One of my earliest experiences in my testing career was participating in a planning meeting. The whole product development team migrated to the corner of our open workspace where a large board-room-style table sat lonely on most days. We all pulled up chairs, but I was one of the attendees who also pulled up a laptop. I started typing up the details of what I was hearing and began asking questions, like I do. The most exciting moment of that planning meeting was the developers noticing that I was still furiously typing their responses to the previous question while moving on to another. Apparently typing one thing and saying another was my amazing stupid human trick. My keyboarding teacher would be so proud.

To this day, my fast fingers continue to amaze, as many physically present and online lurking CAST 2013 attendees can attest. So what’s the secret to my Twitter dominance? The Micro Machines Man John Moschitta, Jr. described his rapid speech delivery as just allowing the words to flow in through his eyes and out through his mouth, so my analogue is in through my eyes and ears and out through my fingers – though I’ll allow the 140 character constraint does require some synthesis along the way.

(So, yes, Claire, we’re all very impressed with your speedy typing, but is it really all that important? Is there a point behind your stupid human trick?)

I find that content generation is a valued skill, even when it’s just providing information from someone else via social media. Helping others to feel present and included is part of my hospitality charism and I want to bring that to bear in the context-driven testing community. I started out as an online lurker and eventually became a participant, but now I have the opportunity to be an amplifier. I like to think of myself as an information radiator, bringing valuable information to light. Now what will you radiate?

The following graph of Agile2018 tweets is even funnier when you realize I was also @agilealliance (not just @aclairefication) #top2 LOL

#Agile2018 via NodeXL https://t.co/FICKe7qFLH@agilealliance@aclairefication@t_magennis@johannarothman@domprice@miquelrodriguez@cainc@emibreton@christophlucian@franklinminty

Top hashtags:#agile2018#agile#womeninagile#devops#metrics#leancoffee

— SMR Foundation (@smr_foundation) August 11, 2018

Live testing – End-to-End Agile Tutorial – CAST 2013

26 Monday Aug 2013

Posted by claire in CAST 2013, Context, Experiments, Exploratory Testing

≈ Leave a Comment

Shelfari: Book reviews on your book blog

Big Visible Testing Full Length

19 Monday Aug 2013

Posted by claire in Agile, Agile2013, Approaches, Context, Experiences, Experiments, Personas, Publications, Speaking, Training, User Experience

≈ 2 Comments

Here are the slides from my full length Big Visible Testing talk, presented at Agile2013 in Nashville, TN on August 6, 2013.

Big Visible Testing (Full Length) from Claire Moss

My experience report paper will be published by the Agile Alliance under the conferences archive as part of the proceedings of the Agile2013 conference. You can also download the PDF here: ClaireMoss-BigVisibleTesting-Agile2013

During the year and a half of experimentation that included the big visible charts that are included in this slide deck, I read over the following resources, only some of which would easily fit into the IEEE format. This is the full bibliography of my research, as far as I have been able to track down my sources. (At the time, I wasn’t expecting to cite them for anyone else, so I probably didn’t bookmark everything I read.) I hope the following links will prove helpful to you in developing your own big visible charts. Let me know how it goes! And please share any sources that you find helpful. I’m always looking for new inspiration.

REFERENCES

My first dev team was an XP dev team that dogfooded our own digital signage product to display success/failure for the thousands of unit tests in the suite (i.e. single flag for whole suite red/green).
Other eXtreme Programming big visible charts

Extreme Feedback Devices summary – I loved this team’s “feel-around” approach to feedback!

  • code smell
  • auditory
  • scrolling marquee
  • code flow
  • lights

Alistair Cockburn coined information radiator
Alistair Cockburn’s burn charts (burn up vs burn down)
Information radiator flash card
More information radiator stuff

Lisa Crispin’s whole team approach includes Big Visible Charts
Energized Work site map backlog
More from Lisa Crispin’s tour of Energized Work

Heatmaps (from code analysis)

Paul Holland’s Exploratory Testing charter Kanban board
Lanette Creamer and Matt Barcomb gave a presentation that included ET charter management in big visible charts; podcast preview of their session

Visualizing above the product team
Including faces of people/profiles in the big visible charts
I can’t remember whether I’d see this one at the time or not… it might have been something I discovered after my time on the team mentioned in my presentation: Visual management for agile teams

New inspiration

Although the above resources were all I knew at the time I began my experiments, as I prepared my IEEE paper for the Agile2013 conference proceedings, I was tracking down my sources and came across these other relevant pages & posts that have given me some great ideas of things to try next!

Gojko Adzic’s visualizing quality

Michael Bolton’s mind-maps

I like this greyhound chasing the rabbit decoy visualization Alistair made
Alistair’s projects (radiating)
Alistair’s collaboration cards

Lego representation of bugs

Other cool extreme feedback devices:

  • bat signal (as a Batman nerd, I heartily approve!)
  • bear lamp
  • traffic light

Clothesline wallboard contest entry – as an avid crafter, I adore this one!
Wallboard contest results

After some discussion in my session about suggesting solutions for distributed teams, I was looking for some digital implementations of big visible charts, but I don’t know how these would work out for you.

Atlassian on information radiators for extreme feedback (with broken image links – sad!)
Atlassian on information radiators
Greenhopper (Jira plugin) wallboard
More on Jira Wallboard

What I Did For My Summer Vacation – Part 1

31 Wednesday Jul 2013

Posted by claire in Acceptance Criteria, Agile, Approaches, Context, Experiences, Experiments, Retrospective, Soft Skills, Testing Humor, User Stories

≈ Leave a Comment

With the First Day of School quickly approaching, it’s time for:

What I Did For My Summer Vacation – Part 1

Exploring Requirements

I get really excited about hanging out with people, especially friends, especially a combination of new and old friends. So it was with great happiness that I set about organizing a geek gal weekend.

Our first conversations centered around budget (fixed), deadline (fixed), and features (flex). We started talking over the various activities that different destinations could provide to entertain us. Then, I paused the conversation to bring the focus back to value: when we looked back on this weekend, how did we want to remember it? how would we feel about the way we spent that time together? would features even feature in these stories we would tell? Instead of features, we realized that functions (what the product was going to accomplish) and attributes (characteristics desired by the clients) mattered more. (Why yes I was reading Weinberg this morning. How could you tell?)

Vintage gold lamé (see that gaw-jus totally 80s animal-print metallic finish? oh yeah.)

Vintage gold lamé (see that gaw-jus totally 80s animal-print metallic finish? oh yeah.)

We wanted to relish the simplicity of being together, whether wearing goofy vintage clothes (gold lamé for the win!), cooking our own meals together, telling silly stories, or engaging in feminine activities with a geek spin (magnetic nail polish was not as simple as expected) that would be low-key and more about togetherness than busyness. We wanted to craft something lasting (collaborative artwork – packing the craft supplies was a must not a want!) and reinforce durable friendships that appreciated our differences.

With this clear focus in mind, suddenly the locale was much less important than inclusivity to maximize togetherness.

Planned For Sand

So we made an informal backlog of tasks to tackle researching options (beach vs mountains), reviewing results, and prioritizing options (beach!) before presenting our findings to the group for dot voting. (Typical agilists, I’m tellin’ ya.) Fortunately, we found a viable approach and went forward with making arrangements to execute this solution (road trip!), adjusting as we went to accommodate discovered needs.

How did it all turn out? Stay tuned for scintillating tales of laughter and danger in What I Did On My Summer Vacation – Part 2!

Ash-ceptance Criteria

29 Monday Apr 2013

Posted by claire in Acceptance Criteria, Approaches, Context, Testing Humor, User Stories

≈ Leave a Comment

Ash-2Weapons
Someone asked me for examples of testable acceptance criteria… Alright. Who wants some?

User story:
As Ash, I want to defend myself against deadites (undead creatures) so that I can retrieve pages from the Book of the Dead.

Acceptance criteria:
– defend from a distance
– defend at close range

Two distinct pieces of value, huh? Clearly, we need a story split here!

User story:
As Ash, I want to repurpose the stump of my right arm into a fearsome weapon so that I can defend myself against undead creatures at close range.

Acceptance criteria:
– portable
– well supported, weight-balanced
– hands-free operation
– use available materials
– holds up under stress
– close-range fighting

Technical implementation:
– leather harness
– chainsaw mounted on handcuff
– chainsaw pull operated via bracket on harness

User story:
As Ash, I want another weapon for my left hand so that I can defend myself against undead creatures at a distance.

Acceptance criteria:
– portable
– easy storage
– one-handed operation
– uses available materials
– distance fighting

Technical implementation:
– sawed-off shotgun
– uses right-hand-mounted chainsaw to saw off shotgun (story dependency or taking advantage of existing features?)
– convenient back holster

Bonus feature/discovered value:
– clever shorthand terminology: “Boomstick”

By now, the distinction between testable user story acceptance criteria focused on user value and the resulting technical implementation should be painfully clear. Groovy?

Tonight’s episode is brought to you by: the beauty of claymation, the number 2, and the words Klaatu… verata… n… Necktie. Nectar. Nickel. Noodle.

Image source

Short cuts

28 Thursday Feb 2013

Posted by claire in Approaches, Context, Experiences, Experiments, Social media

≈ Leave a Comment

Pinterest Mobile App
For more than a year now, I’ve been shopping around for a hairdresser who could provide the ideal haircut. The first two attempts were incomplete, poor likenesses of the beauty I had in mind. I had a clear vision of the intended result, but I lacked the vocabulary to communicate that vision to professionals who could implement the solution. I had fallen victim to one of the classic blunders! (No, it’s not never go in against a Sicilian when death is on the line.) I knew it when I saw it but I couldn’t articulate it. So frustrating!

So I turned to the internet for solace. I perused numerous galleries of smiling women with hair of various lengths, shapes, and hues. In order to find the images I needed for my initial point-and-grunt interface – a printout of images pasted into a document for my first two appointments – I had to first identify the search terms that would produce optimal matches. I quickly cycled through searches from the generic “short haircuts” to the slightly more specific “bob hairstyles,” feeding my learning back into my process. As I progressed toward an exemplar of the captivating coiffure, I began to build a jargon file – and a Pinterest board.

Natural language is ambiguous and context dependent, so any requirements described in natural language are rarely complete. … This is especially problematic when something seems obvious but we need domain expertise or knowledge of a particular jargon to understand it fully. – Gojko Adzic

Stylist jargon:
  • short haircuts
  • cropped hair
  • bob hairstyles
  • asymmetrical bob
  • graduated bob
  • stacked bob
  • angled bob
  • long bob
  • layered bob
  • inverted bob
  • severely angled stacked bob

I don’t know whether those terms produce crystal clear images in your head, but I could see that these terms had a wide range of interpretations even among fashionistas.

An example would be handy right about now

I have heard it said that social media is a time suck, with Pinterest often held up as the mother of time sucks. However, I disagree. For my purposes, Pinterest was a fabulous tool for collecting all these visual bookmarks in one place, building a virtual gallery of hairstyle models as a communication tool.

When I booked my appointment online, I had included only a link to the first image I had found that was a rough approximation, leading her to ask upon my arrival whether I was the one who had sent her the Rihanna photo. (Of course not! That was Nicki Minaj!) That early draft of my request submitted in advance had given her time to mull over the idea.

I am pleased to say the result was exactly what I had hoped for and I will be visiting the Madam LV Salon again. Ultimately, being able to show this gallery to my hair craftswoman convinced her that my request was not a lark, that I had done my homework, and that my Pinterest board was in fact a specification by example.

Seize the Initiative

15 Thursday Nov 2012

Posted by claire in Agile, Context, Experiences, Experiments, Retrospective, Soft Skills

≈ 1 Comment

Antistress Autoreverse

So last year I joined the YMCA. My employer works in this space and they supplement our memberships … on the condition that we attend with a minimal frequency. Nothing to understand your customers quite like becoming their customer! However, working out isn’t really my thing. The “race to nowhere” has no appeal for me. But I went anyway, determined to learn something. Despite my stubbornness on that point, the inertia of years of study was hard to overcome. I needed backup.

Joining the coach approach program was explicitly about wanting to make improvements. The Y coaches promote “adopting healthy habits and changing the way [the participants] live their daily lives.” I knew I wanted to make a change, but I also knew that I didn’t want it badly enough to go it alone quite yet. Having never had a personal coach, I wasn’t quite sure what to expect. What I encountered resonated with my recent experience learning about the role of ScrumMaster.

In particular the sprint activity of retrospective is “an opportunity to learn how to improve.” Defining success in this particular context was the first step. My ScrumMaster watched the process and guided it, making it okay to talk about uncomfortable topics, but it was up to me to do the work. The first big step was being able to establish a safe environment to talk with a more experienced and professional person about a potentially sensitive topic.

In the case of my workout routine, this was my minimal compliance rather than wholehearted adoption of lifestyle change. My Coach Approach coach helped me to develop a vision for the future that would be better than the past. We focused on setting goals while recognizing that the plan had to fit into my work/life balance with the loose structure of frequent check-ins rather than plugging my height, weight, and weight loss goal into a one-size-fits-all spreadsheet.

I was surprised to find that discussion about my health could be fun when my counselor was so friendly and supportive. I would have expected an intervention to be really uncomfortable. Retros can be that way sometimes. But they can also be a welcome change of pace. Roughly every 2 weeks – after we catch up on socializing and the excitement we’ve had since our last chat – my coach and I looked at the artifacts of my progress, paying attention to the time line of events going on in the background and how that influenced the results. Keeping this cadence allowed us to build a healthy relationship that encouraged risk-taking and speaking from the heart. So when my coach suggested adding a weights routine to my cardio, I felt fine with scoffing openly and she felt fine with reminding me of my goals, not allowing my emotions to derail the discussion but remaining fully present and focused.

As our meetings progressed, she offered appreciation of the progress I made, while encouraging me to try new approaches that could yield better results. Even when I felt like I was backsliding, she found a way to put more emphasis on understanding what I had accomplished and focused on encouraging me to keep going. We talked about what parts of the routine were working well, what lessons I learned (like when I hated the treadmill but loved the AMT – hey, participation in individual exercises is optional!), what I could do differently next time, and what might need more scrutiny. We tried to analyze the problems and propose solutions to the boredom, considering a variety of alternatives. It was honest but not accusatory. (Hey, eveybody gets bored with the routine.)

So I’ll admit she’s done me some good. I agree with another participant who said, “My personality is better, my production has gone up, my mental clarity has improved, and my energy level has increased dramatically.” Granted, I just have a lot of energy in general, so I wasn’t likely to sit back and passively take it in – well, as passive as you can be while sweating profusely. I started to recognize my excuses as just excuses, feeling more empowered to modify the situation, learning to manage that impulse to excuse myself from the hard work of changing. Accepting that I actually knew something about working out and lifting weights and could be responsible for designing more of the workout and analyzing my progress on the path to wellness? Yeah, last week was weird.

One ScrumMaster wrote, “At the end of a successful project, everybody says, ‘Gee, I wish we could do it again.’ Using this definition, was the project a success?” Well, I can’t say that I’ve enjoyed every moment of it, but figuring out that I could test software and sweat profusely at the same time? Priceless! But seriously folks, having my coach express sincere and significant appreciation for the care and work I put into making progress sent the message that she cared about and me personally, not just reducing the failure rate of some anonymous gym member. And that’s where the magic happens.

(Special thanks to my dev James who pointed out that coach approach is workout retro!)
Image source

Big Visible Testing

07 Tuesday Aug 2012

Posted by claire in Agile, Approaches, CAST 2012, Context, Experiences, Experiments, Publications

≈ 2 Comments

Presented as an Emerging Topic at CAST 2012

This was my talk proposal:

I have always thought of myself as an agile tester. After all, my development teams have always delivered features in 2 week sprints. My testing activities included reviewing requirements or stories before the planning meetings to assemble a list of questions and test ideas that I would use to approach the work proposed. I participated in a review before code completion that allowed for some exploratory testing, brief and informal though it may have been at times. In the past couple of years, I also planned and coded test automation.

However, over the past year, I have been transforming from a pseudo-agile tester to a true agile tester. Rather than sitting apart from the software developers in my own quality engineering department, I am now seated in the same room as the other employees from a mix of disciplines who are on my product delivery team. Rather than testing in a silo, I have been gradually increasing the visibility of testing activities through exploratory test charter management, defect backlog organization, and paired exploratory testing with both testers and non-testers. The feedback loops have shortened and the abbreviated time between activities necessitated adjusting how I provide information.

Testers are in the information business. We take the interests and concerns of the business as communicated through the product owner – or in my case the product owner team – and combine those with the needs of the customer as expressed in the story and further augment those with our experience using and analyzing software for deficiencies, abberations, and oddities. We draw upon a variety of resources including the experience and perspectives of fellow testers, heuristics, and product history to approach the goal of delivering a product the customer values, focusing especially on the quality aspects of that value.

Now that the audience for my testing comprises a mix of disciplines and the work environment has shifted from a heavier process to transparent, quick information access, I have been experimenting with different ways to execute testing and to represent the outcomes of that testing activity so that the information consumers understand it in ways that best suit each of their perspectives.

In my brief presentation, we will examine 3 different agile team member personas and their implications for presenting and maintaining testing information as well as the inherent tensions between their distinct and various needs. I will trace my learning curve of adjusting to their needs through the various experiments I have completed in this context, though these lessons extend beyond a purely cross-functional agile product development team.

Other testers will come away with a fresh perspective on viewing their product team members and focus on the value testing artifacts provide to a software development team.

Big Visible Testing from Claire Moss
← Older posts
Newer posts →

♣ Subscribe

  • Entries (RSS)
  • Comments (RSS)

♣ Archives

  • November 2024
  • 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
    • Reliability
  • 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.