<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anne-Marie Charrett on Medium]]></title>
        <description><![CDATA[Stories by Anne-Marie Charrett on Medium]]></description>
        <link>https://medium.com/@charrett?source=rss-a6d38ff4735d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HEWU1L-2N_65P6b1.jpeg</url>
            <title>Stories by Anne-Marie Charrett on Medium</title>
            <link>https://medium.com/@charrett?source=rss-a6d38ff4735d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:42:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@charrett/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Quality needs a destination]]></title>
            <link>https://medium.com/@charrett/quality-engineering-b2acb9190a1f?source=rss-a6d38ff4735d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2acb9190a1f</guid>
            <category><![CDATA[quality-engineering]]></category>
            <category><![CDATA[quality]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Anne-Marie Charrett]]></dc:creator>
            <pubDate>Wed, 14 Mar 2018 10:22:51 GMT</pubDate>
            <atom:updated>2018-03-14T10:39:14.592Z</atom:updated>
            <content:encoded><![CDATA[<p>After any decent exposure to software testing, Jerry Weinberg’s definition of quality tends to gain traction and respect. That is “Quality is value to some person”. You like it because of its subjectivity. You may also hate it because of its subjectivity.</p><p>Remember that bug report you raised only to discover that others had a different view point? Forget about having a fixed mindset to quality. What was ‘quality’ yesterday is no longer ‘quality today’. Quality morphs and moulds itself to the context its living in.</p><p>Of course, this makes quality very hard to pin down and digest. A common question I get asked is “how do we know we have quality?”. Metrics are something that many reach for to understand this answer. It’s understandable but it doesn’t always tell the whole story. It’s like looking through binoculars, it’s only part of the picture. I find it’s a combination of metrics, stories and context and that x-factor that we haven’t realised provides a better view.</p><p>At a practical level, I like to frame the quality story in terms of business outcomes. In my simple language, business outcomes are goals that your business wants to achieve. For example, it could be the ability to respond rapidly to market demand, it could be reduced cost or maybe its increased sales. I can’t stress how important to work this stuff out, both the explicit and the unspoken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pXx5Ttq_F8DZqcJ0jkyM6g.png" /></figure><p>So step 1: work out your companies business outcomes. Ask people what they are being measured on, or what their teams are being measured on. (Hint — build a relationship with a person first before you get onto this topic….).</p><p>Step 2: Think about (in terms of your context) what might threaten those outcomes. For testers, it could be that your test environments prevent you from testing early in the development lifecycle. Or perhaps there’s waste in your automation in testing. Let’s call these opportunities for improvement.</p><p>Step 3: Get buy-in. In my experience, you get buy-in by doing things people are interested in. And, it’s likely the more senior the person, the more emphasis you want to place on that interest. Buy-in is important. It gives you legitimacy. You get buy in by linking the business outcome the the opportunities you have in mind.</p><p>Step 4: Start working on reducing those threats, one small step at a time. It’s not going to happen immediately, so prepare people to think long term. Also, think about how you might do small experiments that people are keen to know answers on. Analyse and refactor. The goal is not to achieve the objective but to demonstrate how you are moving to the objective.</p><p>Step 5: Don’t forget those business outcomes, they are your destination, not the experiments themselves. Speak in terms of those outcomes. Do it repeatedly. Preferably by visualising progress.</p><p>Step 6: Be pleasant, have fun and treat others with respect.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2acb9190a1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scientia potentia est]]></title>
            <link>https://medium.com/@charrett/scientia-potentia-est-eddbb97a5eac?source=rss-a6d38ff4735d------2</link>
            <guid isPermaLink="false">https://medium.com/p/eddbb97a5eac</guid>
            <dc:creator><![CDATA[Anne-Marie Charrett]]></dc:creator>
            <pubDate>Fri, 18 Oct 2013 03:55:31 GMT</pubDate>
            <atom:updated>2013-10-18T05:55:11.035Z</atom:updated>
            <content:encoded><![CDATA[<h4>Knowledge is power….</h4><p>Jerry Weinberg cites courage as the most important trait in a tester. <a href="http://blog.utest.com/testing-the-limits-with-gerald-weinberg/">Quoting Kipling, Jerry says testers</a> need to “keep your head when all about you are losing theirs and blaming it on you.”</p><p>But I see a another type of courage at play in software testing. Testers are foremost learners. Through enquiry,they learn about a system. The information they gather facilitates many kinds of decision making from releasing to designing new features.</p><p>Observe great testers and you will discover an insatiable desire to learn more, not only about the product, but the world around us, often incorporating what they learn into their testing.</p><p>For many of us, discovering that our learning is within our control and within our means, can itself be a road of discovery. It takes courage to start that journey, but it also take courage to continue along its path.</p><p>Young Luke Skywalker found the ‘Force’ early on in life. Yoda helped him connect with that power, but even then, he needed guidance and a reminder to ‘<strong>Use the Force</strong>’ when up against the evil Empire.</p><p>Some of us need that reminder now and then. We know we have the ability to learn, and we know of its power, but we forget to use it. Especially when things get tough.</p><p>When things don’t go the way you want, when the pressures of daily life cloud your ambitions and goals, it can be easy to lose site of learning. Here’s what I’ve discovered though, through focusing on learning in these times you gain great strength.</p><p>Will the actual knowledge you learn help you succeed? Perhaps. What really counts is that through learning comes power in the form of ownership and self belief. You may not be able to control the situation at hand, but through being open to and owning your learning, you regain a sense of control and a sense of focus.</p><p>So when the dog bites, when the bee stings and when you’re feeling sad, remember there is solace in learning. It’s not only as an escape, or way of learning how to deal with the situation, but helps you take ownership and responsibility over the next step. Who knows, learning may be the just the ticket you need to recharge those batteries, giving you the juice to continue on your journey or perhaps, dump it for a different destination.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eddbb97a5eac" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>