<?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 Matt Wynne on Medium]]></title>
        <description><![CDATA[Stories by Matt Wynne on Medium]]></description>
        <link>https://medium.com/@mattwynne?source=rss-1b56fc1005fe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2ztb_M_QFPVc3Xph.jpeg</url>
            <title>Stories by Matt Wynne on Medium</title>
            <link>https://medium.com/@mattwynne?source=rss-1b56fc1005fe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:05:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mattwynne/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[Cucumber: a year in review]]></title>
            <link>https://medium.com/@mattwynne/cucumber-a-year-in-review-acf07096d69f?source=rss-1b56fc1005fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/acf07096d69f</guid>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[cucumber]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[bdd]]></category>
            <dc:creator><![CDATA[Matt Wynne]]></dc:creator>
            <pubDate>Mon, 16 May 2022 18:11:31 GMT</pubDate>
            <atom:updated>2022-05-18T15:15:21.839Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s a little over a year since I re-joined the Cucumber open source team as co-lead with the inimitable <a href="http://twitter.com/aslak_hellesoy/">Aslak Hellsøy</a>, joining a team of full-time SmartBear staff including <a href="http://github.com/aurelien-reeves">Aurélien Reeves</a> and Jo Laing. I want to look back on what we’ve achieved in that year.</p><h3>Cucumber continues to grow</h3><p>Across the Cucumber ecosystem, we’re seeing continued overall growth in the number of downloads. JavaScript and Java are the fastest growing, with the original Ruby version starting to shrink a bit, probably as test engineers migrate from Ruby to JavaScript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5pmHDkJdWzdtG37nci5gFg.png" /></figure><h3>Cucumber School is also growing</h3><p>We’ve continued to build out our free video-based skills training for Cucumber and BDD practitioners, <a href="https://school.cucumber.io/">Cucumber School</a>, with 12 new lessons being released across the different languages, including a C# version of the courses for <a href="https://specflow.org/">SpecFlow</a>.</p><p>Cucumber School now has almost 30,000 registered users, and we’re working on commissioning some exciting new content for this year.</p><h3>The new contributors ensemble is thriving</h3><p>Last year we <a href="https://cucumber.io/blog/open-source/tackling-structural-racism-(and-sexism)-in-open-so/">committed to doing our part to tackle the structural sexism and racism</a> evident in open source, and one of the great outcomes from that endeavour has been the <a href="http://cucumber.io/docs/community/new-contributors/">new contributors ensemble</a>. We started running a weekly ensemble-programming session where people new to open source could learn together and gain the skills and confidence to play a part in open source communities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AUsANLi7OJEn_zhtiuSxCw.png" /><figcaption>The new contributors ensemble in action.</figcaption></figure><p>This group has developed it’s own manifesto, and each weekly session is streamed live on <a href="http://twitch.tv/cucumberbdd">Twitch</a>, with the recordings also up on our <a href="https://www.youtube.com/watch?v=Zj3YXaWaXEA&amp;list=PLrQMyTCtW0DZolJHWBLELne1EF2gqMaHc">YouTube channel</a>.</p><p>If you’re someone who’s curious about contributing to open source, especially if you’re from a background that’s traditionally been excluded from open source communities, we’d love you to come and join us! Join our <a href="http://cucumber.io/community#slack">community Slack</a> and head over to the #new-contributors channel.</p><h3>We continue to learn how to be more welcoming to new contributors</h3><p>This change to broaden the diversity of our contributor base is not just like turning around an ocean liner, more like turning around the ocean itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*2w9Zetfz8eqRLPV7jl7W6w.jpeg" /><figcaption>Maxar Technologies</figcaption></figure><p>It’s going to be slow progress, and we’re learning to be patient, and to be prepared to try a lot of stuff that we may not see any immediate effects from.</p><blockquote>not just turning around an ocean liner, more like turning around the ocean itself.</blockquote><p>I’ve been encouraged to see that our regular Thursday community meetings have started to attract some new faces, and we’ve seen first-time contributions from people like <a href="https://github.com/cucumber/godog/pull/468">Arianna Cooper (GoDog #468)</a>, Carl Menezes (<a href="https://github.com/cucumber/godog/pull/457">GoDog #457</a>), Emmanuel Ola (Cucumber-JS <a href="https://github.com/cucumber/cucumber-js/pull/1847">#1847</a>, <a href="https://github.com/cucumber/cucumber-js/pull/1824">#1824</a>), and Mona Ghassemi (Cucumber-JS <a href="https://github.com/cucumber/cucumber-js/pull/1770">#1770</a>).</p><p>All of those folks have benefited from the time Aurélien and I have been spending in 1:1 sessions, mentoring people in getting up to speed with the codebase, and from the support provided by our wonderful community.</p><p>I’ve learned so much from these sessions, especially about how we can improve our documentation to provide more context and signposting to people who are new in our ecosystem. You can book me at <a href="https://calendly.com/mattwynne/">https://calendly.com/mattwynne/</a> anytime, if you’d like some coaching to get you started as a contributor.</p><h3>The core contributor community is vibrant</h3><p>Each Thursday we hold a Zoom meeting with an open agenda for anyone in the community. It’s a great place to discuss topics that can be challenging or time-consuming to figure out over messages in GitHub issues or discussions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PjO3YLK6tIeyVJhON4jkfQ.png" /></figure><p>We have maintainers doing an incredible job of handling all the responsibilities of leading an open source project, mostly in their spare time (<a href="https://github.com/mpkorstanje">Rien Korstanje</a> — Cucumber-JVM, <a href="https://github.com/davidjgoss">David Goss</a> — Cucumber-JS, <a href="https://github.com/vearutop">Viacheslav Poturaev</a> — Godog) backed up generalists like <a href="https://github.com/luke-hill">Luke Hill</a>, Erik Huelsmann, Björn Rasmusson, Ciaran McNulty and others who contribute their time working on libraries and reviewing pull requests.</p><h3>Almost all of our releases are automated</h3><p>Cucumber is made of several libraries, and runs on different language implementations. This means that making releases to Sonatype, NPM, RubyGems etc. is a significant part of the maintainers’ workload.</p><p>Previously these releases had to be made from maintainers’ own machines, using a <a href="https://github.com/cucumber/build/blob/main/Dockerfile">humongous docker image</a> that includes every build tool for every one of the languages we support. It also meant that security credentials for publishing our packages were lying around on people’s machines.</p><p>This felt unsustainable, so over the year we’ve been automating this release process, first by moving the actual package publishing to a <a href="https://github.com/orgs/cucumber/repositories?q=action-publish&amp;type=all&amp;language=&amp;sort=">series of github actions</a>, then <a href="https://github.com/cucumber/cucumber-js/blob/main/.github/workflows/release-npm-latest.yaml#L6">running those actions from pushes to protected release branches</a>, using <a href="https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment">GitHub’s Environments</a> feature to protect the release credential secrets. We’ve also been building out tooling to help us <a href="http://github.com/cucumber/polyglot-release/">make releases in our polyglot repos</a>, where we keep the different language ports of a single library, like <a href="https://github.com/cucumber/cucumber-expressions">cucumber-expressions</a>.</p><p>We still have a couple of projects to go, but we’re almost there.</p><h3>We have an official VS Code Plugin</h3><p>Cucumber now has an official <a href="https://marketplace.visualstudio.com/items?itemName=CucumberOpen.cucumber-official">plugin for Visual Studio code</a>, using a newly-developed <a href="https://github.com/cucumber/language-server/">language server</a> that offers some really awesome autocomplete when you’re writing new scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*mFwlz6HuOwnFB6wgwCpYnw.gif" /></figure><h3>Major new versions of Cucumber-JS, Cucumber-JVM and Cucumber-Ruby</h3><p>All three of our main supported language flavours received major version updates this year:</p><ul><li><a href="https://github.com/cucumber/cucumber-ruby/blob/c00b355572a315d35329c9c8d650d9002a10ae85/CHANGELOG.md#700-2021-07-19">Cucumber-Ruby v7.0.0 was released in July 2021</a>.</li><li><a href="https://github.com/cucumber/cucumber-jvm/blob/main/CHANGELOG.md#700-2021-10-06---release-announcement">Cucumber-JVM v7.0.0 was released in October 2021</a>.</li><li><a href="https://github.com/cucumber/cucumber-js/blob/main/CHANGELOG.md#800---2022-04-06">Cucumber-JS v8.0.0 was released in April 2022</a>.</li></ul><p>Godog, the Cucumber implementation for Go, is planning a 1.0.0 release soon.</p><h3>So what’s next?</h3><p>The team at SmartBear who works on Cucumber full-time (Jo Laing, Aurélien Reeves and me) remain committed to the mission to nurture and enable the community to solve its own problems wherever possible.</p><blockquote>Nurture and enable the community to solve its own problems wherever possible</blockquote><p>In practice, this will involve us continuing our efforts to make the lives of existing maintainers and new contributors easier, with a goal to broaden the diversity of our contributor base, reducing the burden on the existing core team.</p><p>Through that work, I want us to become more flexible on two axes:</p><ol><li>make it simpler to write Cucumber implementations in new programming languages</li><li>make it simpler to add new features to existing Cucumber implementations across programming languages</li></ol><p>We’ve been gradually dismantling a <a href="https://github.com/cucumber/common/issues/1724">large monorepo of shared libraries</a> which we realised had become intimidating for new contributors and existing maintainers alike. I expect to see that effort completed this year, and as as result the number of release from and contributions to those libraries will hopefully increase. We’ve already seen some <a href="https://github.com/cucumber/cucumber-expressions/issues/41">exciting discussions with the team building a Cucumber for Rust</a>, for example, since the cucumber-expressions library was extracted into it’s own repo.</p><p>We’ll be continuing to improve signposting and documentation for contributors, and providing automation and tooling to streamline mundane tasks for maintainers.</p><h4>New messages protocol</h4><p>Cucumber’s been using a standardised NDJSON message format across the different language implementations for some time now, but it’s been mostly used internally, without much documentation available for 3rd parties to use for integrating with it. This year I’d like to see us formalise the message protocol as the de-facto standard for writing Cucumber reporting and other extensions, with well-documented examples and tutorials.</p><h4>Cucumber School</h4><p>We’re still working our way through the epic BDD with Cucumber course, with Chapter 9 (Support Code) still in development and Chapter 10 (Acceptance Tests vs Unit Tests) still to do.</p><p>Once that’s done, I hope to tackle some shorter, practical lessons centred around common uses for Cucumber, a bit like we did in our <a href="https://pragprog.com/titles/dhwcr/cucumber-recipes/">Cucumber Recipes</a> book.</p><h3>What do you think?</h3><p>If you’ve read this far, you’re obviously someone who uses and cares about Cucumber! Do our strategy and plans align with your needs? Do you think we‘re spending our precious time on this earth wisely? Please let us know by <a href="http://twitter.com/mattwynne/">tweeting me</a> or <a href="http://twitter.com/cucumberbdd/">@cucumberbdd</a>, or come hang out in our <a href="https://cucumber.io/community#slack">community Slack</a> for a chat.</p><p><em>This post was originally published on the </em><a href="https://cucumber.io/blog/cucumber-a-year-in-review/"><em>Cucumber blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acf07096d69f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning to be a better dad]]></title>
            <link>https://medium.com/@mattwynne/learning-to-be-a-better-dad-7e6834f4a334?source=rss-1b56fc1005fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e6834f4a334</guid>
            <category><![CDATA[family]]></category>
            <category><![CDATA[mindful-parenting]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[parenting]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Matt Wynne]]></dc:creator>
            <pubDate>Wed, 24 Oct 2018 20:50:18 GMT</pubDate>
            <atom:updated>2018-10-24T21:13:58.982Z</atom:updated>
            <content:encoded><![CDATA[<p>Last Friday night I was in a reflective mood and I wanted to try and engage my family in giving me some feedback about what I could do to be a better dad.</p><p>I tried something was based on the <a href="http://www.liberatingstructures.com/13-wise-crowds/">Wise Crowds</a> workshop format, not that they had any idea what I was up to! We did this with my wife <a href="https://www.instagram.com/anna.wynne">Anna</a>, Rufus (8) and Torben (7). It took about 45 minutes, while I was cooking dinner. It turned out to be a really lovely and insightful activity. We all enjoyed it, I learned some things about myself and how my family perceives me, and it set a really nice mood for the rest of the evening, and beyond.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3hX4ZU4IkZO92drGfT1IzA.jpeg" /></figure><h4>The mechanics</h4><p>I started by unrolling a length of brown parcel paper on the floor, lying down and getting Torben to draw around me.</p><p>Then, while they were colouring in my outline, I hurriedly prepared a few question on index cards, based on the <a href="https://agileforall.com/facilitating-with-the-focused-conversation/">ORID conversation structure</a>:</p><p>Observation:</p><ul><li>What are all the things you see me do?</li><li>Which of them do you see me do <strong>a lot</strong>?</li></ul><p>Reflective:</p><ul><li>What things do you love it when I do them?</li><li>What things do you wish I didn’t do so much?</li></ul><p>Interpretive</p><ul><li>Which of these things give you <strong>big feelings</strong>?</li></ul><p>Decisional</p><ul><li>If I was a RoboDad and you could rewrite my code, what would you change so that I would be a better dad for you?</li></ul><p>I numbered the cards on the back and laid them face down in a pile.</p><p>I explained that I wanted them to be completely honest, and that although I would be listening I wanted them to try and talk about me like I wasn’t there. That they could say whatever they wanted to and I wouldn’t interrupt or answer back.</p><p>Then, as I cooked dinner, I got them to go grab a card, read it out to the others, and then talk about it together, making notes however they wanted on the drawing. When they were done with that question, they could go grab another one.</p><h4>What I learned about myself</h4><p>Here are all the things my family see me do (or be):</p><ul><li>a friend</li><li>loving!</li><li>be scary!</li><li>cook</li><li>share</li><li>help people</li><li>letting people have crisps</li><li>fun to play with</li><li>shout</li><li>look at a screen and ignore me</li><li>massage me</li><li>do coding with me</li><li>hug me</li><li>play video games with me</li><li>poo</li><li>work</li><li>angry</li><li>busy</li><li>washing up</li><li>meditate</li><li>kayak</li><li>run</li><li>talk about the world</li><li>play in the snow</li><li>stress</li><li>forget to each lunch</li><li>put on movies</li><li>look tired</li><li>drive too fast up the track</li><li>be kind</li><li>sing</li><li>fix things</li><li>play music</li><li>give treats</li><li>look for lost things</li><li>talk on Skype</li></ul><p>The biggest feelings were about:</p><ul><li>poo</li><li>work</li><li>shouting</li></ul><p>I do have a habit of disappearing into the bog for a while sometimes, busted!</p><p>And I know I’ve been working a lot lately, and that it’s been getting on top of me a bit. I’ve let some of my self-care habits like running and meditation and getting enough sleep, slip. And I have found myself losing my temper and shouting when I get frustrated and don’t feel like I’m being listened to. I was proud of the kids for telling me about it but it gave me chills to see what a big feature it was of me for them.</p><p>It was really powerful to be confronted by this feedback so directly by the people I love most in the world, and especially in the context of all this other lovely appreciative stuff.</p><h4>What I’m going to do</h4><p>Rufus summed up his request for me in two concise points:</p><ul><li>less shouting</li><li>more pocket money</li></ul><p>Well he doesn’t really get any pocket money at the moment, so that should be easy.</p><p>For the shouting, I’m doing three things.</p><p>First I’m making myself accountable to the family with a chart on the wall in our kitchen. I don’t like these sticker charts when you do them for (more like to) your kids, but I think it’s OK when the shoe’s on the other foot. I get a tick for each day I don’t shout, and if I slip up, I lose the lot. A bit like a <a href="https://lifehacker.com/281626/jerry-seinfelds-productivity-secret">Seinfeld Streak</a>.</p><p>Second, I’m reading Laura Markham’s book, <a href="https://www.amazon.co.uk/Peaceful-Parent-Happy-Kids-Connecting-ebook/dp/B008JHXOOK">Peaceful Parent, Happy Kids</a>. Seems to hit the spot.</p><p>Third, I’m paying more attention to self care. I’m staying off Slack in the evenings, meditating daily and generally trying to put work a bit lower down the pecking order.</p><p>I’ll let you know how it goes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e6834f4a334" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 easy ways to fail at BDD]]></title>
            <link>https://medium.com/@mattwynne/10-easy-ways-to-fail-at-bdd-95a01cc53d63?source=rss-1b56fc1005fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/95a01cc53d63</guid>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[bdd]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Matt Wynne]]></dc:creator>
            <pubDate>Wed, 17 Oct 2018 12:42:20 GMT</pubDate>
            <atom:updated>2018-10-17T12:42:20.286Z</atom:updated>
            <content:encoded><![CDATA[<p>In my work, I come across many organisations who desperately want to enjoy the benefits of practicing BDD, yet set themselves up for failure.</p><p>Growing new practices in your teams is a lot like growing plants: you need to create the right environment for the changes to take root and establish themselves. Did you ever bring one of those basil plants home from the supermarket, and three weeks later it was all limp and brown and, well, a bit <em>dead</em>?</p><p>That wasn’t the basil plant’s fault.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-MI9egCfGctsJLrwKkTgA.jpeg" /></figure><p>In a similar way, there are some systemic impediments we see organisations put in the way of their teams making a success of BDD. Let’s have a look at some of the most common ones.</p><h4>1. Try to change everything all at once</h4><p>A really effective way to get nowhere is to try and do everything all at the same time.</p><p>This applies at both the organisational and team level.</p><p>At the organisational level: push to get all your teams adopting BDD at the same time. The resources you have for training, coaching, and mentoring these teams will be spread paper-thin, meaning that only outlier teams stand any real chance of making a success of it.</p><p>At the team level: encourage people to start doing BDD on everything, all the time, immediately. Throw off the training wheels! Get out of the slow lane! This is a great way to alienate your business stakeholders as the team thrash around and get nowhere fast.</p><h4>2. Make it mandatory</h4><p>A lot of people in your organisation will be skeptical about BDD. Perhaps they’re jaded from previous silver-bullet transformation schemes that have been sold to them. Perhaps they are scared of being pushed out of their comfort zones.</p><p>Either way, an excellent way to build solid resistance to change is to force it on people. Let it be known that change is coming and you’d better get on board or get off the train. Don’t, whatever you do, listen to people’s concerns or give them <a href="https://cucumber.io/blog/2017/05/26/unconference-the-rocket-fuel-in-your-agile-transformation">any way to talk to each other about the change</a>. That would only show weakness and you are a powerful leader who knows best!</p><p>Ideally, try to introduce BDD as part of several other major changes to people’s working lives all at the same time. Why not change their job title, or the processes and tools they use for their daily work, for example?</p><h4>3. Keep the pressure on</h4><p>Have you ever seen a mechanic work on a moving car?</p><p>Have you ever thought about the proportion of time professional athletes or musicians spend practicing, compared to performing?</p><p>Learning new skills will be impossible if your teams are expected to keep delivering features at the same pace. Yes, you must expect an overall improvement in the team’s performance eventually, but you <a href="https://cucumber.io/blog/2017/04/10/improving-throughput-and-collaboration">must also be prepared for an initial dip</a>, while they <strong>slow down to speed up</strong>.</p><p>Keep the pressure on the team to deliver, and you’ll guarantee that any aspirations to improve are nipped in the bud.</p><h4>4. Don’t budget for infrastructure &amp; devops</h4><p>If you’ve not been doing much test automation in the past, you may well not be prepared for the kind of automation of infrastructure that’s also required to have a healthy build pipeline. Excellent!</p><p>Ideally a team doing BDD will need to be able to spin up a realistic environment for their application on any developer’s workstation in a few seconds, so that they can run repeatable tests against it.</p><p>Similarly, they will need to be able to quickly provision machines to run their tests on checked-in code against a clean, stand-alone environment (fresh copy of the database etc.) as part of their build pipeline.</p><p>A great way to stamp out any efforts to implement BDD is to inhibit this kind of activity. Mandate the use of databases with expensive per-server licensing models! Force all teams to share a single build server! Only allow access to cloud VMs to some privileged, central team! Whatever you do, don’t give anyone the time to automate any of this stuff.</p><h4>5. Focus on the tools</h4><p>You’re reading this blog so you probably know that BDD is <a href="https://lizkeogh.com/2011/03/04/step-away-from-the-tools/">more about collaboration than it is about tooling</a>. The tools are just there to facilitate the collaboration. But your people don’t know that! And they love tools!</p><p>Try to ignore those messy, fuzzy, collaborative practices like <a href="https://cucumber.io/blog/2015/12/08/example-mapping-introduction">example mapping</a> for as long as you can. They’re just for the purists!</p><p>Instead, just get people using Cucumber to automate tests. Keep everyone thinking about this as a testing tool, and <a href="https://cucumber.io/blog/2014/03/03/the-worlds-most-misunderstood-collaboration-tool">never let anyone tell you any different</a>, whoever they are!</p><h4>6. Keep the silos strong</h4><p>You have a separate QA department for a reason, right? Nobody can remember what that reason is, but that doesn’t necessarily mean it’s a bad idea: that’s the way things have always been around here!</p><p>The last thing you need is to have developers and QA people talking to each other. Make sure nobody ever tries anything like a <a href="https://johnfergusonsmart.com/three-amigos-requirements-discovery/">three amigos meeting</a>, or there’s a danger you might start learning about defects <em>before</em> they get written into the code!</p><p>Another great reason to keep QA and devs apart is that tests are for testers. If you’re automating tests, it’s not real software development is it? There’s no need to involve engineers who know anything about software development practices. What kind of crazy person would suggest that?</p><h4>7. Have a messy backlog</h4><p>BDD is a tactical practice. It takes user stories as input, helps you test your understanding of them and tease out small chunks of well-understood work from the complexity of the real-world problem. Then it helps you deliver them.</p><p>I often think about the discovery practice of BDD, where we examine the user story and explore our understanding of it, as a filter. We can use it to reject stories that are either poorly-understood, or too big, or both.</p><p>So what if your backlog of stories is a hideous jumble of half-baked notions? Perfect! Each and every three amigos meeting will be a disaster! Make sure nobody is accountable for cleaning up your backlog. The product owner is too busy doing their day-job! And anyway nobody ever gave them any training!</p><h4>8. Avoid anyone with experience</h4><p>People who have used TDD or BDD before have this unswerving confidence that it will be worth it in the end. They’ve seen the benefits of having pushed through that initial pain, and would never go back.</p><p>Avoid these people like the plague!</p><p>The last thing you need is people like this infiltrating your teams with practical knowledge about how to make these practices work, combined with a confidence that the investment will be worth it. Toxic stuff!</p><h4><strong>9. Keep the features hidden</strong></h4><p>If you must tolerate people collaborating to express the system’s behaviour using examples, you can at least make sure those examples are as inaccessible as possible.</p><p>Once people start getting the idea that these examples are not just tests, but could actually double as a living document that describes the system’s behaviour, all hell will break loose!</p><p>Make sure that once the feature files are written, they go into source control and never surface anywhere your non-technical stakeholders might be able to read and refer to them! Anything else would be mayhem!</p><h4>10. Learn on a legacy codebase</h4><p>Your five-year old Java 5 app is going to be just the ideal place for a team to learn BDD. After all, this codebase we never designed with testability in mind, and probably has hideous dependencies that will make it almost impossible for it to be automated. Excellent!</p><h3>Only joking</h3><p>Instead of changing everything all at once, <strong>start with a single team, and a single user story</strong>. Put that story in the “slow lane” and let it take as long as it needs to for the team to learn how to do this really well. Keep going until the team are confident about applying this on all of their stories, all of the time. Now you have a success story you can tell to the rest of the organisation.</p><p>Instead of making it mandatory, <strong>give your explicit support</strong>. Most developers feel guilty about how long their stuff takes — it always takes longer than we expect it to — and they will naturally tend to avoid slowing down to speed up. You need to regularly send them the message that this is OK, that you believe this is the right thing to do, that they have the time.</p><p>Instead of keeping the pressure on the team to deliver, put your energy into <strong>selling the benefits</strong> of BDD to business stakeholders. Work with them to see this as an investment. Be clear that the team will need a few months before the return on investment will be visible.</p><p>As well as investing in the skills of your people, budget to <strong>invest in the infrastructure</strong> they will use those skills on. To get the benefits of BDD, they will need fast feedback from their tests, and that means automation of infrastructure. This is another great reason for starting with a single team — you can learn from their pain-points and resolve them before scaling out.</p><p>Instead of focussing on the tools, <strong>start with the discovery practices</strong> from BDD. Keep banging the drum that automated tests are a secondary benefit from practicing BDD, and that <strong>shared understanding</strong> is the main goal. Coach teams in these collaborative practices, and help them work through the people problems that will inevitably result, just as you’re working through those infrastructure issues too.</p><p>Break down silos and have testers get involved in <strong>testing the requirement</strong>, instead of <a href="https://vimeo.com/143941147">waiting to scrape off the burnt toast</a>. Pair QAs and developers so that developers can use their expertise in software engineering, as well as their deep knowledge of the system to build the most reliable, fast tests you can get. Make it clear that <strong>quality is everyone’s responsibility</strong>.</p><p>Before trying to introduce BDD, make sure you’ve <strong>got the basics of agile</strong> practice down. Professionalise the product ownership in your organisation, by making it a <a href="https://cucumber.io/blog/2016/02/01/what-makes-a-great-product-owner">recognised role with specific skills</a>, not just a part-time job for someone with knowledge of the business domain. Get training for people if they need it. Keep your backlog short, prioritised and well-refined using other excellent techniques like <a href="https://jpattonassociates.com/user-story-mapping/">story mapping</a> and <a href="https://www.impactmapping.org/">impact mapping</a>.</p><p>Embrace people with previous experience of TDD and BDD. These practices are hard to introduce, and having people around with the <strong>confidence that comes from having got to the other side of the hump</strong> will be invaluable.</p><p>Instead of burying your feature files in source control, <strong>publish them somewhere everyone on the team will be able to read</strong> them as documentation. Like anything that’s presented, the team will take more pride in their work, and you’ll likely get more feedback on them, meaning you learn about any misunderstandings sooner.</p><p>Like starting with a single story on a single team, try to <strong>make this easy on yourselves</strong> by starting a codebase that, while representative of other ones you’ll need to tackle soon, isn’t going to put up significant resistance to being automated by tests. Learning to make TDD a habit is hard enough without the codebase getting in the way. Let your teams get their skills and confidence levels built up a little before trying to tame these older codebases.</p><p>There. Those are all the ones I can think of. Do you have any to add? Please respond in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95a01cc53d63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who writes the Cucumber scenarios?]]></title>
            <link>https://medium.com/@mattwynne/who-writes-the-cucumber-scenarios-6ca5f390c2fa?source=rss-1b56fc1005fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ca5f390c2fa</guid>
            <category><![CDATA[bdd]]></category>
            <category><![CDATA[cucumber]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Matt Wynne]]></dc:creator>
            <pubDate>Thu, 05 Jul 2018 17:24:08 GMT</pubDate>
            <atom:updated>2018-07-07T12:54:12.347Z</atom:updated>
            <content:encoded><![CDATA[<p>Barbara is a business analyst.</p><p>Until recently, Barbara hated BDD.</p><p>When her company first adopted Agile, lots of things changed. She was told she no longer needed to write requirements documents. Instead, she was expected to express the business user’s requirements as something called User Stories and put them into their Agile project management tool.</p><p>Jordan, their old Agile Coach, had told Barbara that each User Story needed to have acceptance criteria. When Barbara asked Jordan what acceptance criteria were, he was pretty vague. “Just write whatever you need so that the developers will understand what you want them to build”. He said.</p><p>So she did.</p><p>One thing Barbara liked about the move to Agile was that she sat with the team, instead of with all the other business analysts like she used to. She did miss her BA buddies but they still met up for lunch every Thursday and went for pizza at the mall across the road. Sitting with the team meant she got into lots more conversations with them about the work they were doing together, and had a chance to share some of her deep knowledge of the business domain.</p><p>So it didn’t matter too much what she wrote in the acceptance criteria. After all, as Jordan said, <em>a user story is just a token for a conversation.</em></p><p>Then one day, the team got a new Agile coach, Nigel.</p><p>Nigel told Barbara that she should write all of her acceptance criteria using a new format: Given, When, Then. He said she didn’t need to spend so much time talking with the developers. Nigel said that was inefficient.</p><p>Nigel said that she should try to record everything she knew about each requirement using this Given, When, Then format. It felt kind of awkward, but she gave it a go.</p><p>Nigel said that the advantage of using Given, When, Then was that not only were they requirements for the developers, but the testers could use them for automated testing too. Nigel said this was called BDD. Barbara was starting to find Nigel quite irritating.</p><p>Anyway, Barbara carried on like this for a while. Her job became more lonely. She wrote up her user stories, and her Given, When, Thens, and assigned the stories to the developers in their Agile project management tool. The atmosphere in the team changed. People didn’t talk so much any more. It started to feel like the old days, except that she had to use this stupid fiddly project management tool and this silly Given, When, Then format — or “Gherkin” as Nigel insisted on calling it for some reason — for all her requirements, instead of just opening up Microsoft Word.</p><p>Barbara complained to her buddies on Thursdays about BDD. One of her friends, Carol, who was working in a different division of the company now where Jordan was coaching, seemed surprised.</p><p>“Wait, <em>who</em> do you say writes the scenarios?” asked Carol.</p><p>“I do”, said Barbara, “who else do you think could do it? The developers don’t seem to know enough about what the product does. And anyway, Nigel says they’re too busy to talk to me.”</p><p>“Too busy my ass! Busy writing code that does the wrong damn thing I’ll bet!” said Carol. “Let me tell you how we do it on <em>my</em> team.”</p><p>Barbara blushed a little at Carol’s language, but she couldn’t hide her smile. She really admired Carol’s up-front style. She listened as Carol explained.</p><p>“BDD is all about <em>learning early</em>. About <em>deliberate discovery.</em> About <em>embracing your ignorance</em>. If you have the person with the most domain knowledge write the scenarios, you’re missing a learning opportunity. That is a weak-ass move.</p><p>“Instead, use the act of writing the scenarios as <em>feedback</em>.</p><p>“Start with a conversation including at least the <a href="https://www.agilealliance.org/glossary/three-amigos/#q=~(filters~(postType~(~&#39;page~&#39;post~&#39;aa_book~&#39;aa_event_session~&#39;aa_experience_report~&#39;aa_glossary~&#39;aa_research_paper~&#39;aa_video)~tags~(~&#39;three*20amigos))~searchTerm~&#39;~sort~false~sortDirection~&#39;asc~page~1)">BA, tester and developer</a>, to talk through the scope of the story. You can use <a href="https://cucumber.io/blog/2015/12/08/example-mapping-introduction">example mapping</a> or some other way to manage that conversation, but keep it quick and focussed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GRABHv7ynanVvSIIzslr0Q.png" /><figcaption>How BDD teams work</figcaption></figure><p>“Next, have <em>the people who learned the most</em> in that conversation — that’s generally going to be the tester and developer — go off and write down what they heard as scenarios.</p><p>“Now they share those scenarios back with you, the domain expert, and see if they got it right. They <em>test their understanding</em>. Writing scenarios is so much cheaper that writing code, and we all know it’s much cheaper to fix a mistake before it gets into the code.</p><p>“You might need to go around this loop a few times to get it right, but that’s good. Better than waiting until they already coded up a bunch of shit you never wanted, right?</p><p>“Anyway, once everyone’s happy that those scenarios describe the thing as we want to build it, the team can automate it and use Cucumber to guide then as they write the code.”</p><p>“This sounds really good,” nodded Barbara, her eyes gazing idly out of the window. “Now how am I going to convince Nigel to let us try it…?”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ca5f390c2fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we do this]]></title>
            <link>https://medium.com/@mattwynne/why-we-do-this-72a7d78f3f03?source=rss-1b56fc1005fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/72a7d78f3f03</guid>
            <category><![CDATA[bdd]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Matt Wynne]]></dc:creator>
            <pubDate>Fri, 12 Jan 2018 23:59:15 GMT</pubDate>
            <atom:updated>2018-01-17T21:52:49.609Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>I just got home from a week-long retreat with the rest of the team from <a href="https://medium.com/u/dd5bd70a2b67">Cucumber</a>, along with a special guest <a href="https://twitter.com/salfreudenberg">@salfreudenberg</a>. We started the meetup by reflecting on and sharing the values and motivations that have brought us all together, trying to sum them up into one short, memorable statement of purpose that expresses our shared mission.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atGVLDxL1R-vDCvRVkBVXw.jpeg" /></figure><p>We covered the walls and windows with hand-drawn posters showing various attempts at distilling into words the meaning behind the stories we told each other. We couldn’t quite find the words to do those stories justice.</p><p>This post is an attempt to share the essence of that mission with you. To give you an idea of the people who make up our company, what we believe in, what we stand for, and what you should expect from us over the months and years to come.</p><h4>Rubbish software is a waste of human potential</h4><p>When software delivery goes wrong, everyone involved is made miserable.</p><p>The customers or executives who commissioned the software feel cheated by the spiralling costs and missed opportunities due to late delivery.</p><p>The end-users feel the frustration of wasted hours working around bugs and missing features as they try to actually make use of the shitty product.</p><p>The development team work long hours, feeling pressured and overwhelmed, only to learn that their end-users hate what they’ve made and the executives are pissed off with them.</p><p>And the code they’re written is so rotten it will have to be thrown away and re-written inside five years.</p><h4>It doesn’t have to be this way</h4><p>Each of us working at Cucumber has experienced the sheer joy of working on a software delivery team that clicked.</p><p>Where the developers, end-users and customers had regular open lines of rich, meaningful communication and feedback.</p><p>Where the pace of delivery was exhilarating.</p><p>Where the end-users were passionate advocates for the software product, and the executives sang the praises of the development team.</p><h4>We want to share that joy with everyone</h4><p>The practices we’ve used over the years to <a href="https://twitter.com/woodyzuill/status/555771271342850048">be in that wonderful state that makes great software inevitable</a> are not some secret sauce, available only to an elite.</p><blockquote>I’m not a great programmer, I’m just a good programmer with great habits.</blockquote><blockquote>— Kent Beck</blockquote><p>These are real, tangible everyday practices. Practices we believe anyone can learn, if they’re willing to put in the hard work.</p><p>We care greatly about helping other people discover just what a wonderful, creative activity software development can be.</p><p>But sometimes it feels like it might take a revolution to get there.</p><h4>We’re learning all the time</h4><p>Is this just about Cucumber and BDD? No.</p><p>Are we experts with all the answers? No.</p><p>This is a tremendously exciting time to be working in software. We love experimenting with new practices, developing new tools and sharing what we’ve learned and built.</p><p>We love working with organisations, big and small, and learning how the dynamics and culture can be shifted to get better results.</p><p>We’ll never be done. There is always more to learn.</p><h4>Collaboration is the key</h4><p>If I have to find one word to best express the essence of what we consider to be fundamental in all of this, it’s <em>collaboration</em>.</p><p>Being part of a community that cares about collaboration is what drew all of us into the BDD community in the first place, and into the XP community before that.</p><p>Collaboration is how <a href="https://github.com/cucumber/cucumber">Cucumber</a>, the open-source tool that brought us together, is built: thousands of collaborators all over the world working together on the same product.</p><p>Collaboration is how we’re building Cucumber Pro, working closely with our <a href="https://app.cucumber.pro/projects/cucumber-pro/documents/branch/master/features/early_access_programme.md">Early Access Programme</a> customers to drive our priorities on a daily basis. Collaboration is <em>why</em> we’re building Cucumber Pro, so that everyone on the delivery team can collaborate on shared, executable specifications.</p><p>Collaboration is what lies at the heart of the way we run our business, involving everyone in key decisions and ensuring every voice is heard.</p><p>So there you have it. To sum all of this up into a short, memorable phrase or two will take some distance, and some persistence. Watch this space.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72a7d78f3f03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Example Mapping]]></title>
            <link>https://medium.com/@mattwynne/introducing-example-mapping-42ccd15f8adf?source=rss-1b56fc1005fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/42ccd15f8adf</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Matt Wynne]]></dc:creator>
            <pubDate>Tue, 15 Dec 2015 10:59:12 GMT</pubDate>
            <atom:updated>2015-12-16T11:52:49.344Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BTcib_sFyaFJQj45ONGGnw.jpeg" /></figure><p>Before you pull a user story into development, it’s crucial to have a <a href="http://ronjeffries.com/xprog/articles/expcardconversationconfirmation/">conversation to clarify and confirm</a> the acceptance criteria.</p><p>Some people do this during their backlog refinement or planning poker sessions. Other teams have a specific <a href="http://www.velocitypartners.net/blog/2014/02/11/the-3-amigos-in-agile-teams/">three amigos</a> meeting, <a href="http://gojko.net/2008/11/12/specification-workshops-an-agile-way-to-get-better-requirements/">specification workshop</a> or <a href="http://dannorth.net/2010/08/30/introducing-deliberate-discovery/">discovery workshop</a>.</p><p>Whatever you call this conversation, many teams find it hard: it’s unstructured, it takes too long and gets boring. The result is they don’t do it regularly or consistently, or maybe they just give up on it entirely.</p><p>I’ve discovered a simple, low-tech method for making this conversation short and powerfully productive. I call it <a href="https://twitter.com/search?q=%23ExampleMapping">Example Mapping</a>.</p><h3>How it works</h3><p>Concrete <em>examples</em> are a tremendous way to help us explore the problem domain, and they make a great basis for our acceptance tests. But as we discuss these examples, there are other things coming out in the conversation that deserve to be captured too:</p><ul><li><em>rules</em> that summarise a bunch of examples, or express other agreed constraints about the scope of the story.</li><li><em>questions</em> about scenarios where nobody in the conversations knows what the right outcome is. Or <em>assumptions</em> we’re choosing to make in order to progress.</li><li>new <em>user stories</em> we discovered or sliced and deferred out of scope.</li></ul><p>Example Mapping uses a <a href="http://www.staples.com/Staples-Assorted-Color-Index-Cards/product_SS1037669">pack of 4-coloured index</a> cards and some pens to capture these different types of information as the conversation unfolds. As we talk, we capture them on index cards, and arrange them in a map:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*BrGJ6H_TdbHu0-ik0Y7vNg.png" /></figure><p>We start by writing the <strong>story</strong> under discussion on a <strong>yellow</strong> card and placing it at the top of the table.</p><p>Next we write each of the acceptance criteria, or <strong>rules</strong> that we already know, on a <strong>blue</strong> card and placing those across the table beneath the yellow story card.</p><p>For each rule, we may need one or more <strong>examples</strong> to illustrate it. We write those on a <strong>green</strong> card and place them under the relevant rule.</p><p>As we discuss these examples, we may uncover <strong>questions</strong> that nobody in the room can answer. We capture those on a <strong>red</strong> card and move on with the conversation.</p><p>We keep going until the group is satisfied that the scope of the story is clear, or we run out of time.</p><p>And that’s it. I told you it was simple!</p><h3>Instant Feedback</h3><p>As the conversation flows, we quickly build up a visual representation on the table in front of us reflecting back our current understanding of the story:</p><ul><li>A table covered in red (question) cards tells us that we still have a lot to learn about this story.</li><li>A table covered in blue (rule) cards tells us that this story is big and complicated. Perhaps we can slice it? Take another yellow (story) card and put the sliced story on the backlog.</li><li>A rule with many examples might be over-complex. Are there multiple rules at play that need to be teased apart?</li></ul><p>You’ll find that some rules are so obvious you don’t need examples at all. It’s clear from the conversation that everyone understands the rule. Great! You can all move on with your lives without forcing yourselves to grind out examples like BDD-brainwashed automatons.</p><h3>Thinking inside the time-box</h3><p>A small group of amigos should be able to map out a well-understood, well-sized story in <strong>about 25 minutes</strong>.</p><p>If you can’t, either you’re still getting the hang of this (which is fine), the story is too big (definitely not fine), or it still has too much uncertainty in it. Listen to that, and either try and slice the story, or let the product person go off and do some homework before you put story back into another example mapping session at a later date.</p><p>At Cucumber, we use a quick <a href="http://www.conferencesthatwork.com/index.php/event-design/2012/06/testing-consensus-using-roman-voting/">thumb-vote</a> after 25 minutes to determine whether we think the story is ready to pull into development. Even if there are some questions remaining, you might think they’re minor enough that you can resolve them as you go. Let the group decide.</p><h3>Benefits</h3><p>Example Mapping helps you zoom in and focus on the smallest pieces of behaviour inside your story. By mapping it out you can tease apart the rules, find the core of the behaviour you want, and defer the rest until later. With this level of scrutiny, example mapping acts like a filter, preventing big fat stories from getting into your sprint and exploding with last-minute surprises three days before demo-day.</p><p>It also saves time, and so helps maintain busy product people’s interest in the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*IUInhxY336FflAAZRiG-zA.png" /></figure><p>Many teams assume that the three amigos should write acceptance tests (e.g. Cucumber scenarios) <em>during</em> this session, sitting around a projector while someone types formal gherkin scenarios into an IDE. There are occasions when this is valuable, but generally I think it’s a bad idea. It can actually be distracting from the true purpose of the conversation.</p><p>It’s easy to see why people make this mistake: the apparent purpose is to take a user story, which already has some pre-defined <em>acceptance criteria</em>, and come up with <em>examples</em> that can be turned into <em>acceptance tests</em>.</p><p>I think the true purpose, however, is to reach a <em>shared understanding</em> of what it will take for the story to be done. You can move much more quickly towards this goal by staying low-tech.</p><h3>Friends episodes</h3><p>So instead of going for full-blown formal Gherkin scenarios, just try to capture a list of <em>rough examples</em>, using the <em>friends episode</em> naming convention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/351/1*SkFRwqe6_WOtFRALubaH9g.png" /></figure><p>For example:</p><ul><li>The one where the customer forgot his receipt</li><li>The one where the product is damaged</li><li>The one where the product was bought 15 days ago</li></ul><p>Sometimes, when uncertainty lurks, you’ll instinctively want to be more concrete than this. You still don’t need to resort to the rigid structure of <em>Given When Then</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n0LhqGju2-ZQa8qVRB5ekw.jpeg" /></figure><p>When the outcome (Then) is unclear, you don’t have an example, you have a question.</p><h3>Known unknowns</h3><p>Whenever a conversation like this is going round in circles, it’s because you don’t have enough information. Probably someone is missing from the conversation, or maybe you need to do some user research, or a <a href="http://www.extremeprogramming.org/rules/spike.html">spike</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KvrSgLNKH1UrH1PxyPgKpg.jpeg" /></figure><p>Instead of letting everyone share their <em>opinion</em> about what they think the outcome should be, simply capture the question and move on. Congratulations! You’ve just turned an <em>unknown unknown</em> into a <em>known unknown</em>. That’s great progress.</p><p>Many people tell me that just this one aspect of example mapping has transformed their discovery workshops from dull ramble-athons into snappy productive mind-melds.</p><h3>Who should come?</h3><p>The bare minimum is your three amigos: a developer, a tester and a product person. That’s just a minimum though. By all means invite your operations, user experience people or whoever else is relevant to the story being discussed. Anyone likely to help you discover new questions, or to turn questions into decisions during the conversation will be useful.</p><p>While you’re learning this technique, it can help to have someone in the formal role of facilitator, whose job it is to make sure everything that’s being said is being captured on a card. Examples and questions fly around the room quickly, and it takes discipline to capture them on the table so you can see what you’re talking about.</p><h3>So when do we write Gherkin?</h3><p>Don’t let this post confuse you: there is immense value in writing Gherkin together too, especially during the early days of a project. That’s where you develop your <a href="http://martinfowler.com/bliki/UbiquitousLanguage.html">ubiquitous language</a>, and it’s vital to have those scenarios expressed in a way that everyone on the team believes in.</p><p>But expressing examples in that way requires a different mode of thinking from deciding which examples are in scope, and clarifying the underlying rules.</p><p>For a team that’s up and running, with a fairly mature domain language, my preference is for the product person to spend their time and energy in the example mapping session, and leave the actual writing of Gherkin to their other two amigos. Once they’ve drafted a Gherkin specification, the product person can give them feedback.</p><blockquote>Is that how I would have written it?</blockquote><p>This gives you an opportunity to test how effective the example mapping conversation was in transferring the product person’s knowledge to their amigos.</p><h3>How often should we do this?</h3><p>Product people are often busy. Respect their time by scheduling these sessions in a way that they’ll be able to give you their full attention.</p><p>My recommendation, based on what I’ve seen work for several teams in practice, is to run them frequently: every other day is often a good rhythm. Just pick one story and give it 25 minutes of attention, then go back to work. Trying to do more in a big batch will just drain your energy.</p><h3>But my team is distributed!</h3><p>I’ve seen innovative hacks on this already: some people use bullet lists in a shared Google doc, I’ve seen people using a spreadsheet with coloured cells to represent the cards. You could also use a mind-map. The key is to keep it quick and easy to work with, <em>so you can focus on the conversation</em>.</p><h3>Some final tips</h3><p>It’s important to clearly understand the distinction between <a href="http://lizkeogh.com/2011/06/20/acceptance-criteria-vs-scenarios/">rules and examples</a> before you can make use of Example Mapping. I have a <a href="https://speakerdeck.com/mattwynne/rules-vs-examples-bddx-london-2014">fun exercise</a> for teaching this that I’ll share in a future post.</p><p>Remember that the whole purpose of this conversation is to <strong>discover the stuff you don’t already know</strong>. So there are no stupid questions. Have some fun and really explore the problem.</p><p>You’ll find that rules make natural fault lines for slicing your story. Try to feel comfortable deferring as much as possible, so that you can focus on solving the core of the problem. You can add more sophistication (and complexity) later.</p><p><em>Thanks to Janet Gregory, Aslak Hellesøy and Seb Rose for their feedback on this post, to Theo England for his patience while I perfected it, and to Tom Stuart for </em><a href="https://twitter.com/tomstuart/status/673447106506563584"><em>getting me to pull my finger out</em></a><em>.</em></p><p><em>This article was originally posted </em><a href="http://cucumber.io/blog/2015/12/08/example-mapping-introduction"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42ccd15f8adf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>