<?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 Terry Thrasher on Medium]]></title>
        <description><![CDATA[Stories by Terry Thrasher on Medium]]></description>
        <link>https://medium.com/@terrythrasher?source=rss-aeaedaf12624------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6uWUnLxbW5x3dpT6ZZfvrg.png</url>
            <title>Stories by Terry Thrasher on Medium</title>
            <link>https://medium.com/@terrythrasher?source=rss-aeaedaf12624------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:32:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@terrythrasher/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[Incredible Instant Pot Chili Recipe]]></title>
            <link>https://medium.com/@terrythrasher/incredible-instant-pot-chili-recipe-41ecfec57e1a?source=rss-aeaedaf12624------2</link>
            <guid isPermaLink="false">https://medium.com/p/41ecfec57e1a</guid>
            <category><![CDATA[chili]]></category>
            <category><![CDATA[instant-pot]]></category>
            <category><![CDATA[cooking]]></category>
            <category><![CDATA[recipe]]></category>
            <dc:creator><![CDATA[Terry Thrasher]]></dc:creator>
            <pubDate>Mon, 27 May 2019 00:20:56 GMT</pubDate>
            <atom:updated>2019-05-27T00:20:56.969Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone loves chili, and I have found the greatest chili recipe in the history of the world! You won’t want to miss this incredible instant pot recipe… it’s so <strong>easy</strong> and <strong>delicious </strong>and <strong>nutritious</strong> and <strong>cures diphtheria!</strong></p><p>If you have an instant pot and a whole bunch of beans, this recipe is for you! If you want to impress your friends and deter your enemies, this recipe is for you! If you want something you can cook <strong>in less than an hour</strong> on a <strong>stove top</strong>, this recipe will work! But we recommend an <strong>instant pot</strong> because it is <strong>instant!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*9-bsKndS3Oirud7TFv1Tyg.jpeg" /></figure><h3>Ingredients, Part One</h3><blockquote>1 1/2 pounds lean ground beef</blockquote><blockquote>1 15oz can of kidney beans</blockquote><blockquote>1 15 oz can of pinto beans</blockquote><p>Shopping for ingredients is hard because you are a busy person. But luckily I have put <strong>all</strong> of the ingredients in this <strong>handy list</strong> to make it easy to shop for what you need for this amazing chili! Remember that when you shop, you should make use of your Aeroplan card or rewards on your credit card so that you can also <strong>earn while you shop</strong>!</p><h3>Ingredients, Part Two</h3><blockquote>1 15oz can of black beans</blockquote><blockquote>1 15oz can of fire roasted diced tomatoes (juicy)</blockquote><blockquote>1 6oz can of tomato paste</blockquote><p>One time I hosted a <strong>party</strong> and served this chili and everyone was <strong>amazed how good it tasted</strong>! They said “Terry we have never seen you cook before and this chili is <strong>edible</strong>!” I told them that not only was it edible, it was also <strong>good for them</strong>, as in if they knew what was good for them, they would keep eating!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*uKqlVWWFWkq3kT3wDyyHIw.jpeg" /></figure><h3>Ingredients, Part Three</h3><blockquote>1 red onion, cut into chunks</blockquote><blockquote>1 red bell pepper, cut into chunks, ideally with no seeds unless you want the crunch</blockquote><blockquote>2 cups of beef stock</blockquote><p>I have been asked how I developed my cooking style! <strong>No one</strong> believes me when I tell them that I took a class at my local culinary <strong>school</strong>! They think I just googled and copied and pasted the recipe and <strong>started taking credit for it</strong>! They have no idea that I have changed at least <strong>two things</strong> about the original recipe because I <strong>can’t find a potato peeler</strong>!</p><h3>Ingredients, Part Four</h3><blockquote>1 tbsp oregano</blockquote><blockquote>2 tsp cumin</blockquote><blockquote>2 tsp salt</blockquote><p>People ask me <strong>all the time</strong> where I got my instant pot! I always tell them Canadian Tire… because I don’t want to admit I was shopping at <strong>Walmart</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*_uMGrbgmR1vZXeQAAV018g.jpeg" /></figure><h3>Ingredients, Part Five</h3><blockquote>1 tsp pepper (the shakeable kind)</blockquote><blockquote>1 tsp paprika</blockquote><blockquote>2 tbsp chili powder</blockquote><p>This food helps me stay active and strong while I play <strong>dodgeball</strong>! Did you know that in each 20 minute game of dodgeball you will burn <strong>500 calories</strong>? That is what my Apple Watch tells me I burned and that is <strong>science for you</strong>! I credit my success in dodgeball to <strong>this exact chili recipe</strong> because you guys I eat this chili <strong>every day for lunch</strong>!</p><h3>Ingredients, Part Six</h3><blockquote>1 tbsp Worcestershire sauce</blockquote><blockquote>1 tbsp minced garlic</blockquote><blockquote>2 cups of love</blockquote><p>I assume this chili would also work with other meats such as <strong>turkey</strong> and <strong>bacon</strong> and <strong>elephant</strong>! Have you experimented with other meats? Let us know in the <strong>comments below</strong>! We would love to hear about your foodsperiments so that we can <strong>copy them for future posts on this site</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*q7-dZXpCiEOGz1oFUsSGFg.jpeg" /></figure><h3>Instructions</h3><blockquote>1. Turn on your instant pot!</blockquote><blockquote>2. Throw in the onion and pepper!</blockquote><p>Cooking in an instant pot <strong>enhances the flavor</strong> by using pressure and time! Microwaves and stove tops and ovens make everything taste like <strong>rust</strong> and <strong>diapers</strong> so stop using them and use your instant pot instead!</p><h3>More Instructions</h3><blockquote>3. Add the meat, and break it up, and cook it until it browns!</blockquote><blockquote>4. Drain any gross grease that is in the pot! You can drink it for a tasty beverage!</blockquote><p>When you’re <strong>done making this chili</strong> you can even freeze it by putting it in your <strong>freezer</strong>! Through the magic of being very cold you can even eat this chili later! If it is a very warm summer day you could nibble on a <strong>chili puck</strong> for a refreshing treat!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cOv2bJ0MdX_oiH9d_YZuuQ.jpeg" /></figure><h3>Even More Instructions</h3><blockquote>5. Throw everything else in the pot!</blockquote><blockquote>6. Stir until it looks like reddish-brown slop!</blockquote><blockquote>7. Set your instant pot to “chili” because you are <strong>making chili!</strong> If your pot doesn’t have a chili setting, <strong>throw</strong> it out! Or set it to manual and <strong>cook</strong> for the number of minutes I mentioned in the story above about dodgeball!</blockquote><p>There are <strong>all kinds</strong> of foods and drink that go well with this chili such as my famous <strong>instant pot corn bread</strong> and my patented <strong>boiled water</strong>! Who knew that chili could be so <strong>versatile</strong> while also being delicious! I may never eat anything else ever again, except on the side! And <strong>dessert</strong> because chili cannot replace ice cream, unless you freeze it!</p><h3>Wrapping Up</h3><p>Once the chili has cooled down for a bit, serve it with cheese and sour cream to make it much less healthy than it was before! Use <strong>bowls</strong> or your favorite large <strong>ladle!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCmMh-6685HQynwDDdtusw.jpeg" /></figure><h3>More Recipes</h3><p>If you want even more recipes just like this one, my <strong>delicious food newsletter</strong> is coming <strong>soon!</strong> It will have incredible recipes <strong>just like this one</strong> formatted in <strong>exactly the same way</strong> for all your flavored sustenance needs! Follow me on Facebook and <strong>Pinterest</strong> and Twitter and Instagram and Snap and <strong>Tiktok</strong> for sneak peeks at all my <strong>latest</strong> content!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41ecfec57e1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Across the River]]></title>
            <link>https://medium.com/@terrythrasher/getting-across-the-river-895d5530ae60?source=rss-aeaedaf12624------2</link>
            <guid isPermaLink="false">https://medium.com/p/895d5530ae60</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Terry Thrasher]]></dc:creator>
            <pubDate>Tue, 12 Mar 2019 16:48:40 GMT</pubDate>
            <atom:updated>2019-03-12T16:48:40.334Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ix1fHzSPellePEKbtYGhjg.jpeg" /><figcaption>Donner und Blitzen Wild and Scenic River from <a href="https://www.flickr.com/photos/blmoregon/">https://www.flickr.com/photos/blmoregon/</a></figcaption></figure><p>Several years ago I was a new product manager. One of the items in my portfolio was a game that was doing pretty well on the App Store. Our CEO, seeing the trend of iOS games moving to freemium models, decided that we needed to do something similar. He wanted to take our single-purchase games and introduce trial versions.</p><p>Classically, the logic of a trial version is that a greater number of potential customers will try it because it’s free. From there, you can monetize more of them than if you were depending on people to pay for the game in the first place.</p><p>At the time, the conventional wisdom was that games converted from trial to paid at an average rate between 2 and 2.5%. I didn’t have experience with designing trials… but I figured I could beat that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*YOP-3TkSjEbOV-HwZlA2rw.jpeg" /><figcaption>A representation of the brainstorming stage, except the chair looks more comfortable than mine.</figcaption></figure><h3>Research Time</h3><p>I looked into how different games established this kind of trial to paid path. How did they set expectations with customers? What was promised for free? What was teased if they paid? What actually drove a player to decide “I like this and I want more, so I’ll pay a few dollars”?</p><p>My method was to sketch out various user journeys. I imagined different ways of encountering the game, what the user would want at each stage, and when would be the best times to draw their attention to the choice to upgrade.</p><p>The plan was to provide the full game play experience, but eliminate the progression found in playing over time. Players could do everything they could in the full game, except that instead of a sequence that built up to a conclusion, things just happened one after the other.</p><p>There was skepticism about my plan, because it was a little unusual: normally free versions of games limited the time the player had, or limited the game options available. At the time, our company’s best conversion rate was 5.1%, and it capped players by time. I was urged to follow that model. I didn’t believe it was the right choice for my product, though, and I stuck to my guns.</p><h3>The Results</h3><p>After a couple of weeks, I checked the stats… <em>13.3%!</em> That was an <em>outstanding</em> conversion rate! My rookie efforts at designing a high conversion trial were much more successful than I’d expected. And it felt pretty good to be able to show those numbers to the folks who’d doubted my approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x8jF9PV_RHc8pUJQziM5_A.png" /><figcaption>Up and to the right!</figcaption></figure><h3>The Real Results</h3><p>However, after a month or so with the trial in market, revenue hadn’t actually changed. Despite the conversion rate being very high, the game wasn’t actually making any more money. The direction provided by the CEO was essentially just “make trial versions of our games.” I adopted conversion rate as my success metric, and optimized for a high rate. I achieved that, and learned a lot, but in terms of business results, I didn’t actually achieve anything.</p><h3>The Lesson</h3><p>Because we hadn’t established clear business goals early on, we didn’t truly know if we were working toward the right things. Because I chose the wrong focus for the trials, I wildly achieved success according to the wrong metric. It would have been worth the time and effort to identify our true aim before starting on the work, because then our plan might have been different (and might have made more money).</p><p>What should we have done instead? There’s a saying we could have considered: “Don’t design a bridge, design a way across the river.” If we wanted to increase revenue, perhaps we should have spent money marketing the game, or put ads in our other games, or tested how trials might increase revenue before committing to that plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFnqFEDXRA97o4vKoYd0-w.png" /></figure><p>In the end, it was a valuable lesson for me to start with clear outcomes that definitely represent success. If I can say I met all my objectives, but nothing improved for customers, or the business, or even really for me, then what did I actually do? Now I know to ask myself if anyone is actually going to get to the other side of the river… or if I’ve built a beautiful broken bridge.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=895d5530ae60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Worst Day of My Life]]></title>
            <link>https://medium.com/@terrythrasher/the-worst-day-of-my-life-99a96450afac?source=rss-aeaedaf12624------2</link>
            <guid isPermaLink="false">https://medium.com/p/99a96450afac</guid>
            <dc:creator><![CDATA[Terry Thrasher]]></dc:creator>
            <pubDate>Sat, 12 May 2018 19:50:30 GMT</pubDate>
            <atom:updated>2018-08-18T17:47:26.928Z</atom:updated>
            <content:encoded><![CDATA[<p>I’d like to share a story with everyone. It’s a story about the single worst day I’ve ever experienced.</p><p>After reading about this day, you might think it’s not so bad. You might think that if this is the worst I’ve gone through, I’ve been lucky in life. I won’t deny that.</p><p>There have been other bad days in my life. There was the day my cat died. That was the first time a pet I owned had passed away. It was tough. There was the day my fiancée dumped me. That was the first major heartbreak of my life. It was tough. There was the day my dad hit me in the head with a shovel. That was the first time I had been hit in the head with a shovel. I didn’t like it.</p><p>Still, none of those days are likely to stick in my memory the way Jeff’s bachelor party will.</p><h3>The Weekend</h3><p>I’d known Jeff for about ten years. We met at work, when he trained me as a video game tester. We bonded over XBox 360 games, football, and having anxieties, and we stayed close after we’d both moved on from the company.</p><p>After several years in a relationship with a lovely woman, Jeff proposed. She said yes. Marriage plans were made. Like most soon-to-be-married men, Jeff would have a bachelor party. The best man, Danny, got to planning.</p><p>Jeff grew up in a pretty rural area, which he refers to as “the Woods”. He enjoyed being outside among greenery and bugs. Danny planned an appropriate bachelor party, with a cottage and outhouse and canoe trip and board games and alcohol. A nice, wholesome-ish weekend.</p><p>Friday night went well. Six guys arrived at the cottage, had some food and drinks, and played a few games. We made plans for the following morning, when we would hit a nearby river for a relaxing multi-hour canoe trip, before returning to the cottage for a BBQ.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*yqP1eRybJsRMIAE5iLMLkQ@2x.jpeg" /></figure><h3>The Fateful Morning</h3><p>On Saturday morning, we gathered our supplies and headed to Swamp River. The plan was to put in the water at 10am, pause for lunch in the early afternoon, and finish around 5pm. All of us had done some canoeing in the past, one of the guys had gone down this very river last year, and it wasn’t going to be a hard day anyway.</p><p>At least, none of us expected it to be. You know the saying “the best laid plans of mice and men often go awry”? Well, our plans weren’t the best laid, because none of us had checked into one <em>very important</em> detail: the water level. And we really should have, because the river was two feet or more below its usual level. And so our moderately well laid plans were <em>for sure</em> going to go awry.</p><p>The six of us paired off into three canoes and started paddling at a leisurely pace. I was enjoying the pleasant temperature, and the soothing feeling of making slow progress downriver, until we rounded our first bend and saw a beaver dam.</p><p>The dam was sort of impressive, in a really frustrating way, because it completely blocked our path forward. We could try to bring our canoes to the dam and climb over, or we could get out and walk around it.</p><p>Except remember the name of the river? Swamp River? It lived up to the moniker, and so walking around the dam was difficult. For the two guys who tried, they lost their shoes, because the river bank was actually just muck that would suck them both in up to the knees. The other four of us decided to go over, so we pulled up sideways, climbed out, lifted the canoes over, got back in, and carried on.</p><p>About a hundred feet beyond the dam, around another bend, we encountered a fallen tree, which beavers probably didn’t put there, but it was still blocking our progress.</p><p>“Awesome,” I said. I didn’t mean it.</p><p>Everyone went over the second obstacle. It wasn’t too bad, though it was slippery. I lost my footing on the slick, wet bark and slid into the water, but it wasn’t particularly deep, and my FitBit survived being dunked just fine. The tree just slowed us down a bit, like the beaver dam before it.</p><p>And like the beaver dams after it, and the fallen trees after it, and the shallow, mucky water after it. Every one or two hundred feet, we encountered a new reason to swear. At times we could go around the obstacles, if the ground was solid enough, or if there was enough wood to spread our weight over the surface of the dark, viscous mud. Our progress was slower than expected.</p><p>In front of me, one of the guys was mid-stroke when his oar snapped in half. He looked at it with a mix of confusion and resignation before he began paddling again… now with far less leverage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*0IVylkWVTwl4YB30vcA4cg@2x.jpeg" /></figure><h3>The Longest Afternoon</h3><p>Somewhere around the seventh beaver dam I was definitely thinking to myself that we should turn back. It felt like we were going very slowly. We would go over or around one obstacle, only to see another just ahead. This was supposed to be a leisurely day of paddling, not a discount woodsy obstacle course.</p><p>I couldn’t have been the only one thinking about some alternative plan, but none of us voiced our thoughts, other than the guy who’d been down the river last year. “It opens up not far ahead, and it’ll be smooth sailing after that.” He said that a few times. I was skeptical.</p><p>We had some snacks and water, but they were light fare, because we weren’t expecting to have to work that hard on the water. The paddling wasn’t even the hardest part: when we reached a fallen tree that was only barely underwater, we would try and scoot over in an action that can only be described as synchronized powerfucking. I had never thrust so vigorously for so long.</p><p>At one point, several hours after we’d first gotten on the water, we came around another bend, only to see a <em>lot</em> of stuff we were going to have to go over. Jeff said “the ground looks solid enough, I’m going to go scout ahead.”</p><p>Grabbing an oar and leaving his canoe, Jeff headed to what passed for the shore, and was quickly obscured by the shrub-like plants. However, he hadn’t gone far when we heard a crack and a yell. “Fuck!!”</p><p>“What happened?” “Are you OK?”</p><p>He didn’t answer at first, but we could hear the plants rustling as he made his way back toward us. Jeff emerged back into view holding half of his oar in each hand. “I was using it as a walking stick, and it just broke.”</p><p>“Awesome,” I said. I didn’t mean it.</p><p>Another hour or so passed. “Maybe we should figure out how to get back by land. This river is not getting any easier.” I don’t remember who voiced it first, but surprisingly, it wasn’t me. Still, we decided to go a little farther, and to see if the river actually did get any better.</p><p>It didn’t.</p><p>At one point we were carrying our canoes around some other problem. I was the last one in the line at this point. I was walking on some wood strewn over the swamp mud, testing my weight every step of the way. However, despite my care, one of the old logs snapped under me. As I fell forward, my glasses flew off my face. With a desperate lunge I snatched them out of the air, though that meant I couldn’t land on anything, so I fell mostly into the swamp.</p><p>My shoulders, head, and hand were clear of the grime. With my other hand I’d been able to grab another nearby piece of wood to stop my fall… but at this point I was hanging from one leg and one arm over muck of an unknown depth. I sighed and had to stop myself from screaming.</p><p>Jeff had turned back in time to see my fall. Later he would comment “I thought you were going to completely snap when you almost lost your glasses.” And I might have: without them I would have been a huge liability in our group. With them I was just really, really frustrated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*Q-ZVNJd0OaSN9zihxxYcSw@2x.jpeg" /></figure><h3>The Darkening Evening</h3><p>After a bit more slogging, we hit our first landmark. I don’t remember what it was, but I remember what the guy who’d planned this part of our adventure said about it: “Uh, that means we’re about a third of the way down the river.”</p><p>It was 6pm. Originally we were expecting to be off the river around 5pm.</p><p>We found some stable shore. Exiting the canoes for a break, we took stock of the situation and discussed what to do. Five members of our six-strong group were fed up with the river, and the other guy wasn’t going to argue strongly for keeping on the “water”, so we assessed our options.</p><p>Walking along the river bank would be faster than paddling, except for the whole not-being-solid-earth thing. Following the river on land probably wasn’t an option.</p><p>We had one phone with us, secured in a ziplock bag. We opened it up and turned it on to see where the nearest road was. About two kilometers southeast.</p><p>It was hard to tell from the map, but it looked like it was a mix of forest, clearings, and farming fields between us and the road. We’d be carrying the canoes, but it had to be faster than sticking to the river.</p><p>Slightly complicating things, four of us didn’t have shoes. I had gotten into the canoe barefoot, because why would I need shoes if we were just paddling down the river? Other people had lost their shoes in the swamp. The two guys who did still have shoes mentioned that their shoes were soaked. I didn’t feel bad for them.</p><p>We had maybe 20% battery remaining on the phone, and we would probably need to actually call someone when we reached the road. So we checked the map again, oriented ourselves, shut off the phone, and set off.</p><p>Of course, it wasn’t going to be rainbows and strawberries. Actually it was raspberries. Did you know wild raspberry bushes are full of thorns? I know that now, because they raked every exposed bit of skin below my shoulders as I walked through them. Walking around wasn’t a realistic option so we tried to press through and avoid bleeding too much. However, there’s only so much you can do, and before long all of us were sporting angry red scratches and blood.</p><p>We were also going uphill all the time somehow. Barefoot. On rocky ground, and bleeding. Like a walk to school that a sitcom grandfather would reminisce about. At least we knew there was a road, and it wasn’t too far away.</p><p>When we finally crested the rise, there was a relatively harmless-looking clearing in front of us. That’s when one of our most outdoor-savvy members said “Stop. We have to go around this.”</p><p>“What? Why?”</p><p>“Wild parsnip.”</p><p>He explained that the sap from those plants can easily burn a person and cause massive painful blisters. I would later google image search those blisters and profoundly regret my decision.</p><p>Luckily it was possible to walk around the wild parsnip, as long as you didn’t mind going through more wild raspberry bushes and their plentiful thorns. We chose the less problematic vegetation and carried on.</p><p>In time, we found old fences among wild plant growth, markers of what was nominally someone’s property. We were getting closer to the road! But we also weren’t traveling in a straight line. Our meandering path around wild parsnip, around more swampy ground, and around growth too thick to push through was taking longer than we expected. We were also out of food and water. One of us called a halt. We turned the phone back on to see what our progress was like.</p><p>“Guys, I don’t think we’re going fast enough. We only have maybe an hour of daylight left, and I don’t know about you, but I don’t want to do all this barefoot in the dark. I think we’re going to have to leave the canoes.”</p><p>They weren’t even our canoes. We had borrowed them from cottage neighbors. Sometimes it’s us versus them, and the them is someone else’s canoes.</p><p>We quickly discussed the points, but ultimately it was clear that our way forward would be without the canoes. We turned on the phone to try and fix the coordinates where we were leaving the canoes, and we started to track our progress so that we could hopefully retrace our steps the next day. And we headed toward the road a little faster, with the sun getting closer and closer to the horizon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*2Y1NjOANuqoGY5cRMnXJdw@2x.jpeg" /></figure><h3>The Sun Sets</h3><p>With as much hustle as the group could manage, which actually was more than I expected, we continued toward the road, mostly in silence. We were seeing more fences, so we were confident that the direction was correct, but the trip wasn’t getting easier.</p><p>Until we reached an opening with clear signs of human use. “It’s a four-wheeler trail!” And it was heading in the right direction! Finally, we knew we were on the last part of our ill-conceived trek.</p><p>Although there were, of course complications. “Uh, this trail is mostly mud and cow shit. I don’t think there’s any way to avoid stepping in cow shit.”</p><p>Barefoot, bleeding from the toll extracted by the thorns and the rocks, I considered this. I would be getting brown muck of various origins into open scrapes and scratches. “Awesome,” I said. I sort of meant it.</p><p>Because now we were walking in a straight line toward a road. We were on solid ground that wasn’t trying to make me bleed. Sure, my open scratches were probably getting some fecal matter in them, but after everything else that had gone wrong on this day, that felt like a problem I would happily leave for myself in the future.</p><p>After a short walk, we saw cows. I’d say they were probably surprised to see us, but I don’t think cows are very smart. We were happy to see them, though, because cows meant a field that was close to a house, which would be close to a road.</p><p>Only a little farther along, we saw a couple of houses and a barn. Civilization! Smiles finally cracked our faces. The end was in sight.</p><p>We reached the road, tired and dirty and totally relieved. The sun had just set, and though it was dark, there was light in our voices. The guy with the phone started calling people to find someone who could pick us up and take us back to our own vehicles. In the meantime, some of us discussed other options.</p><p>“We could just knock on one of the houses here. They will have water, and I really, really want some water.”</p><p>I can only imagine what the roughly 20 year old woman answering her family’s front door must have thought when she saw two grimy men looking like they’d been through a war. We asked for water. Luckily she was very compassionate. She shared bottles of water with us, and in those minutes I learned what it was probably like to meet an angel.</p><p>The phone calls hadn’t yielded much, but the woman in the house said she’d call her grandparents. They owned the house and farm, and were nearby at a friend’s house. After a little while they arrived and regarded us with some amusement. Also they had questions.</p><p>“You came down the river? From over there?” asked the grandfather. He pointed in the direction of the cows, shit path, and deadly plants, toward the river.</p><p>“Yeah, we did.”</p><p>“Swamp River is down a couple of feet this year. Did you know that when you set out?”</p><p>“Nope.”</p><p>“Ha. Normally it’s pretty good paddling, but this year it would have been really rough.”</p><p>“Yeah.”</p><p>“I bet you wish you hadn’t gone out there without checking the water, eh?”</p><p>“…”</p><p>“OK well let’s get you back to your cars!”</p><p>We silently climbed into the back of his pickup truck. A mere five hours and much darkness after we thought we’d done, we were heading back to our cars and the cottage.</p><p>“Hold on,” said the young woman who’d met us at the door. We all turned in the truck to face her.</p><p>“Can I take a Snapchat? My friends will <em>love</em> this.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*8jkLySjSllgbscvpnof2-Q@2x.jpeg" /></figure><h3>The Aftermath</h3><p>We got back to the cottage at 11pm. Danny’s aunt had prepared a nice barbecue meal for us that was now hours old. “Where were you? I was really worried!”</p><p>“That was probably justified.” We were all covered in dark mud and blood, and the burst of energy that came from reaching the road had long since been spent.</p><p>We took turns showering, trying to wash out as much grime as we could. We cleaned our cuts and checked ourselves for ticks. When you’re waist-deep in the muck in Swamp River, who knows what might cling to you?</p><p>The burgers and water were like ambrosia and nectar. As we refueled and reminisced, I think we were all grateful to be safe and relatively unharmed. “I thought we did a good job of just keeping going, and no one got really mad at anyone else,” said Jeff.</p><p>It was true: I’d say that despite our frustration with the circumstances, and our incomplete preparation, we faced the obstacles with grim determination and a plan. We may have been dirty, tired, thirsty, hungry, and mildly wounded, but we were focused.</p><p>The next morning I stayed and cleaned up the cottage while Jeff, Danny, and the others went back to the farm with a four-wheeler and a trailer to retrieve the canoes. We had to replace the broken paddles, but all in all the non-psychological damage was minimal.</p><p>We left the trip behind, now wiser, but thankfully with no lasting damage. Danny’s feet would swell up two shoe sizes and made dancing at the wedding really awkward, which I thought was suitable because someone had to pay for what we’d all gone through.</p><p>In the end, my childlike innocence about canoe trips was destroyed, but nothing else. I count myself lucky that the only scars I have from the worst day of my life are purely mental. I have learned to always check the water levels before you get on a river. And I know that any future bachelor parties I attend had better be entirely indoors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99a96450afac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using JIRA to Solve Agile Problems]]></title>
            <link>https://medium.com/building-freshbooks/using-jira-to-solve-agile-problems-23188dcbfa83?source=rss-aeaedaf12624------2</link>
            <guid isPermaLink="false">https://medium.com/p/23188dcbfa83</guid>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Terry Thrasher]]></dc:creator>
            <pubDate>Tue, 09 May 2017 19:14:33 GMT</pubDate>
            <atom:updated>2017-05-09T19:14:33.787Z</atom:updated>
            <content:encoded><![CDATA[<p>As a Scrum Master, my primary responsibility is to help my team grow. That includes measuring how much stuff we do, and how consistently we do stuff.</p><p>In early 2016, my team at FreshBooks was working on a new product. At times it felt like we were making progress slowly, and that our estimates for how long things would take weren’t lining up with reality.</p><p>I thought about how to tackle this, and broke it up into three questions:</p><p>1) Are we actually moving slowly?</p><p>2) Are our estimates reliable enough?</p><p>3) Do we need to change anything about the way we work?</p><p>I needed answers to the first two questions in order to answer the third. The best way I could think of to approach the problem was to look in our project tracking software, <a href="http://www.atlassian.com/software/jira">JIRA</a>.</p><p>At FreshBooks, all of our product development work is managed via JIRA, typically with Agile boards. There are built-in reports to measure work being done… but each team operates differently and with autonomy, so comparing one team’s reports to another’s wouldn’t shed any light on my questions.</p><p>Another Scrum Master suggested that the control chart was a great way to get a high-level view of my team’s work. When I looked at it for the first time, it was clear I would have to learn to use it, because it looked like a Petri dish:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y6bTmm0r0hQKQCwI." /></figure><p>What this chart shows is a timeline with every issue that is or was captured by our Agile board. The dots are issues, and the higher dots represent things that took longer to finish, from the time the issue was started till the time it was marked as complete.</p><p>Once I understood how to use it, I realized the chart is a treasure trove of useful information. And here’s how it helped me answer those three questions.</p><h3><strong>1) Are we actually moving slowly?</strong></h3><p>As a representation of how quickly our team was working, I focused on how long it took for us to complete our tasks in JIRA.</p><p>My first step was to reduce the noise by constraining the data shown on the control chart. To do this, I searched for what I was interested in, then saved the search as a <a href="https://confluence.atlassian.com/agile/jira-agile-user-s-guide/configuring-a-board/configuring-filters">filter</a>. For example, early on I realized that including bugs and tasks wasn’t useful: they varied too much and weren’t representative of our team’s momentum. So I wrote a filter to include only the team’s stories. Now the chart was more readable and less of a chemistry experiment.</p><p>There were a few stories that were clearly outliers. I expected to see our large stories take 5–7 work days to complete, but there were some stories that took 20+ days, even 70 days in one case. Was our planning really that bad?</p><p>I looked at each outlier individually, and found some commonalities. When a story took a very long time, it often meant the person working on it had got stuck, or that we had finished the work but had forgotten to mark the issue as complete in JIRA. I created another filter to remove the outliers so that we had the option of looking at our standard results.</p><h3><strong>2) Are our estimates reliable enough?</strong></h3><p>Next I broke up our stories by their estimates.</p><p>We were estimating each item with two, three, or five story points. Two point stories were expected to be low risk and take a couple of days to complete. Five point stories involved more risk and took a full one-week sprint to complete. And three point stories landed somewhere in the middle. After plotting the issues and showing the sizing here’s what I saw:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/0*NuYD5PV3_cjXp-lM." /></figure><p>While we weren’t surprised by the five pointers, the two and three point stories were taking the same amount of time! It was clear that our estimates weren’t lining up very well with the amount of time we were actually taking.</p><h3><strong>3) Do we need to change anything about the way we work?</strong></h3><p>Now that I had a bunch of interesting, informative data, I walked everyone through my findings. As we talked through the points and what they represented, the team clearly saw that our estimates weren’t reliable. They also felt that we were taking too long to finish our stories. As a group, we discussed why that was, and what to do about it.</p><p>The first insight was that we weren’t breaking up our stories enough before we started working on them. Many of the stories that took a long time involved someone getting stuck, and we might have been able to anticipate the obstacles if we had taken a more granular look at the work we needed to do. While we’d be adding some overhead, the team felt it was worth doing.</p><p>The second insight was that if we were going to more effectively break up and estimate our stories, we needed to use a finer points scale. We settled on expanding our range to six numbers (1, 2, 3, 5, 8, 13), and committed as a team to breaking up stories so that they fit one of our new sizes. We also committed to honestly assessing any large stories that might bleed past the end of a sprint, and promised ourselves that if we could break those up, we would.</p><h3><strong>So did it work?</strong></h3><p>With general agreement on the team, and a framework in place, the last question was “how will we know if it’s better?”</p><p>It was going to take some time to update our backlog with our new standards, and it was going to take some time to practice our new costing and story writing standards. After trying it out for a month, everyone on the team agreed it was a good approach. Starting from this point, the data would count.</p><p>Three months later we checked in to see if we’d been successful…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*xZcMnN5ZOHC9YN7nIVjO8Q.jpeg" /></figure><p>Look at that graph! It’s almost too perfect!</p><p>Our estimates had become pretty good predictors of the time we would spend working on stories. The variance was lower than before. We were spending less time per issue overall. We were more consistent about completing what we took on in the expected time frame. We had more time to spend on bugs, research, and paying down technical debt. And as an unexpected bonus, everyone was more mindful about keeping JIRA up to date, so we had fewer outliers.</p><p>The role of a Scrum Master is often represented as all soft skills and indirect action. However, doing my job properly sometimes means taking direct, data-driven action. JIRA is a powerful tool for collecting data to help a team understand how they’re working and to target areas of improvement. Sometimes that’s exactly the kind of tool I need.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23188dcbfa83" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-freshbooks/using-jira-to-solve-agile-problems-23188dcbfa83">Using JIRA to Solve Agile Problems</a> was originally published in <a href="https://medium.com/building-freshbooks">Building FreshBooks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>