<?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 wijet on Medium]]></title>
        <description><![CDATA[Stories by wijet on Medium]]></description>
        <link>https://medium.com/@wijet?source=rss-6bbeb25cb100------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pbIT5_vmpImblhOye2opQA.jpeg</url>
            <title>Stories by wijet on Medium</title>
            <link>https://medium.com/@wijet?source=rss-6bbeb25cb100------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:21:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wijet/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[How To Be Better At Recruitment Than A Coin-Toss]]></title>
            <link>https://medium.com/ragnarson/how-to-be-better-at-recruitment-than-a-coin-toss-a30a764175d1?source=rss-6bbeb25cb100------2</link>
            <guid isPermaLink="false">https://medium.com/p/a30a764175d1</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[recruitment]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[wijet]]></dc:creator>
            <pubDate>Mon, 28 May 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-06-04T10:30:11.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/912/0*DFfCIhY4eseGWOs-.jpg" /></figure><p>We tend to overestimate our potential and abilities. The more complex a task is and the further away in time the consequences of our decisions are, the harder it is for us to accurately evaluate our performance.</p><p><strong>It’s not bad will or lack of judgment, it’s a natural bias people have.</strong></p><p>This fact is clearly visible in the hiring process, because it’s hard to evaluate someone’s knowledge, motives, potential and cultural fit based on a few calls. Whether a candidate was actually a good fit can sometimes come out only after several months.</p><h3>For small companies a wrong hire can be a real hiccup</h3><p>Each employee contributes to the company culture in a unique way. In a small company, not shackled by politics, the impact one person can make is more profound than in a large company, and a person who doesn’t fit can make the rest of the team miserable.</p><p>Recruitment is a lengthy process. It can take one to two months to hire a person, then another two to three months for the trial period. If it was a wrong hire, the process must be repeated to hire a replacement and hope that this time things will be different. The whole process can take six months or more.</p><p>If you happen to be an agency, as we are, and the hire is a developer, your client won’t be very happy, either, if you need to replace him.</p><p>Let’s not forget that with a bad hire, we also waste the candidate’s time. Since you know the company, it’s your responsibility to help the candidate discover whether he or she is a good match or not.</p><p>This is not a trivial decision.</p><p>At <a href="https://ragnarson.com/">Ragnarson</a>, every successful recruitment involves from 8 to 12 of our developers. Each developer has to be aware of the math, the rules and the mechanics of the process. There are multiple factors that are not obvious at first glance. <strong>That’s why last month we carried out a hiring workshop for our developers.</strong></p><p>You, too, need to know your factors. Being aware of the facts and statistics and how to improve them will increase your chances of recruiting top talent.</p><h3>Your personal evaluation skills</h3><p>If you happen to be God, you have an accuracy of 1. This means that you’re right 100% of the time.</p><p>The very best professional interviewers have an accuracy of 0.7. Their evaluations are 70% correct. Most people fall in the 0.3 range, so they are right only 30% of the time¹. Not surprisingly, when deciding whether <em>a candidate at hand</em> is a match or not, they’re wrong 70% of the time².</p><p>It doesn’t matter where you land on this scale. Even if you’re better than the industry’s ‘crème de la crème’ and you have an accuracy of 0.9, the odds are still against you. And here is why.</p><h3>What are your chances when aiming for the top 10% of talent?</h3><p>It’s not uncommon that during any two year period, an HR specialist will have gone through hundreds of job candidates. So, let’s assume that you have a group of 100 people, and in this group, 10 are top talents and 90 are the rest.</p><p>Every company prides itself on hiring only the best, so, naturally, you aim for exactly those top 10%. However, you don’t know who these people are. So, what will be your error rate in picking the top 10%?</p><p><strong>The harsh reality is 50%. Your error rate will be the same as a coin-toss.</strong> Keeping in mind that you have an unrealistic accuracy of evaluating a candidate at hand of 90%.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/0*BCMXPijyqMZXt6E3.png" /></figure><p>Let me explain that. If we have 10 top talents, 90 suboptimal choices and your accuracy is 90%, you’ll pick 9 top talents from the group of 10 and dismiss one of them. From the group of 90, again, you’ll rightly eliminate 81 candidates as not top 10% and wrongly pick 9. You end up with 9 right and 9 wrong choices that you think are the top 10%.</p><p><strong>So you’re correct in 50% of the cases.</strong></p><p>Sadly, this is not the end of the bad news. The calculations assume that your evaluations are 90% correct, which is hardly possible. If you’re in a group of the industry’s best interviewers, you’re only 70% accurate. Presented with the same group of 100 people, your error rate will top almost 80%. Have a look at the figure below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/0*8MYnYCyBTyT1Dj2W.png" /></figure><p>If you have an accuracy of 30%, your error rate is close to 96%, which means you would be better off doing the opposite of what your gut tells you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*_ECxcZaGlvjf7ai7.png" /></figure><h3>How can we improve our odds?</h3><p>Two things come swiftly to mind.</p><p><strong>We could simply improve the quality of the pool of candidates.</strong> If we had a group of 100 people in which 60 would be top performers and your accuracy were 70%, we would have an error rate of 22% instead of 80%. Not bad, but of course, that’s easier said than done.</p><p>How, then, do we improve our odds if we can’t dramatically improve the quality of the pool?</p><p><strong>We can add filters to the recruitment process, or simply put, include more decision-makers.</strong> Have a look at the table below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u2rkZ3jOubwlTT4v.png" /></figure><p>Imagine our starting scenario with a group of 100 people: 10 top performers, 90 suboptimal choices and three people evaluating them with an accuracy of 70% each. We would have an error rate of 80% on the first person (as previously mentioned). The second person would have a 61% error rate because it would only work on the pool previously filtered by the first person, and the third person would have an error rate of 41%.</p><p><strong>We managed to get from an 80% error rate to 41%.</strong></p><p>However, the decision-makers <em>(the filters)</em> don’t just sit together and come up with a democratic verdict. Each filter is applied after the other.</p><h3>So, multiple interviews?</h3><p>You may be thinking, well, you didn’t exactly spill the beans, here. Every recruitment process has several interviews, filters or stages: first call, homework exercise, pair programming session and a meeting with the management.</p><p>You’re right, but if those interviewers influence each other’s decisions, <em>they all act as one filter instead of many</em>. For example, some interviewers (like managers) might have a stronger incentive to hire because they have more work than their current team can handle.</p><p>Moreover, you don’t know who should remain as an interviewer because of excellent accuracy and who just throws spaghetti at the wall.</p><h3>Interviewers’ accuracy varies</h3><p>As we saw in the table with filters, three interviewers, each with a 0.3 accuracy, have an overall error rate of 99%. To get reasonable results, we still need to strive for the highest possible evaluation accuracy of each interviewer.</p><p>Following the advice from K. Pearson and P. Drucker, <em>‘That which is measured, improves’</em>, you need to start keeping individual scores of each interviewer.</p><p>At <a href="https://ragnarson.com/">Ragnarson</a>, we do exactly that. If a newly recruited employee leaves the company without so much as a ‘goodbye’ or we need to fire someone, we consider that person a bad hire. This will affect the accuracy rate of the team-members who approved the hire.</p><h3>Engage the team</h3><p>Besides looking at the personal accuracy, we encourage the people who will work with a newly hired employee to take part in the process.</p><p>They’re the ones spending the most time with a newcomer, they’re the ones understanding role requirements and the company from the inside, so they’re the ones who should make the final call.</p><h3>Conclusion</h3><p>Everyone wants to work with the best, and sometimes we let ourselves get carried away by guesses, hunches and wishes. In these moments, it’s good to know what the odds are. Multiple interviews working as independent filters and a simple scoring system for each interviewer could increase the effectiveness of the recruitment process.</p><p>I would love to hear about your ideas for increasing the odds of a good hire. Feel free to ping me on Twitter at <a href="https://twitter.com/wijet">@wijet</a>.</p><h3>Notes</h3><p>Insights and figures in this article come from a great book on recruitment called <a href="https://goo.gl/3jSNhu"><em>It’s Not the How or the What But the Who: Succeed by Surrounding Yourself with the Best</em></a> by Claudio Fernández-Aráoz. I recommend it to anyone dealing with hiring.</p><p>Here is the Google <a href="https://goo.gl/3dPQPi">spreadsheet</a> with the error rate calculations.</p><ol><li>According to the Claudio Fernández-Aráoz the author of <a href="https://goo.gl/3jSNhu"><em>It’s Not the How or the What But the Who: Succeed by Surrounding Yourself with the Best</em></a> <a href="https://wijet.pl/better-at-recruitment#fnref:1">↩</a></li><li>To simplify calculations, we assume that people have the same accuracy in evaluating whether someone matches the profile as when they don’t. <a href="https://wijet.pl/better-at-recruitment#fnref:2">↩</a></li></ol><p><em>Originally published at </em><a href="https://wijet.pl/better-at-recruitment"><em>wijet.pl</em></a><em> on May 28, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a30a764175d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ragnarson/how-to-be-better-at-recruitment-than-a-coin-toss-a30a764175d1">How To Be Better At Recruitment Than A Coin-Toss</a> was originally published in <a href="https://medium.com/ragnarson">Ragnarson</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to choose a bug tracker for a small startup team]]></title>
            <link>https://medium.com/@wijet/how-to-choose-a-bug-tracker-for-a-small-startup-team-bd2faa16a221?source=rss-6bbeb25cb100------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd2faa16a221</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[bug-tracking]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[wijet]]></dc:creator>
            <pubDate>Fri, 14 Jul 2017 13:18:05 GMT</pubDate>
            <atom:updated>2017-07-14T13:18:05.231Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*h2XY1geUXTHW1vuKZl95HQ.png" /></figure><p>Choosing a project management tool isn’t an easy task. There are tons of SaaS/web-based issue tracking tools out there (like with TODO apps for personal use.) Quora and Stack Exchange threads are full of comments written by marketing teams about these tools. It’s as easy to overshoot and choose a massive product, packed with hundreds of features, that cripples your productivity and joy, as undershoot and end up with a service that you will outgrow in a matter of weeks.</p><p>I assume that you run a small startup company. If that’s true you will most likely have two areas to align. Some kind of software product or products and the company itself. The latter includes things like marketing, recruitment, employees’ on-boarding, etc.</p><p>In our 10 years of experience we have found that these two areas are different matters and require quite different tools. Running an agile software development project requires a strict and repeatable process of defining, estimating, planning, developing, testing and deploying. There is a deadline, a list of milestones broken down into smaller tasks etc. Those are the industry standards. On the other hand, marketing or sales isn’t that “linear” at the beginning and it often differs from company to company. Committing to pay for HubSpot or Salesforce from the very start might be an exaggeration and a shot in the dark.</p><h3><strong>Why is it important to choose the right tool?</strong></h3><p>Your workflow within a project management tool influences factors like ease of planning, efficient execution of the plan, progress tracking, teamwork and overall team motivation. What is more, once you commit to one solution it’s not that easy to migrate halfway through (because of the vendor lock-in.) Sure, there are migration tools, but in my experience, for anything larger than a pet project, it’s never a matter of only pushing a button.</p><p>To give you more context, we have completed over 50 projects with various project management tools, from modern issue trackers to real dinosaurs. We used <a href="https://trac.edgewall.org/">Trac</a>, <a href="http://www.redmine.org/">Redmine</a>, <a href="https://lighthouseapp.com/">Lighthouse</a>, <a href="https://www.pivotaltracker.com/">Pivotal Tracker</a>, <a href="https://trello.com/">Trello</a>, <a href="https://basecamp.com/">Basecamp</a>, <a href="https://www.atlassian.com/software/jira">Jira</a>, <a href="https://guides.github.com/features/issues">GitHub Issues</a> (with and without <a href="https://huboard.com/">Huboard</a>.) And we were lucky enough to test numerous others because from time to time the client already had his tool of choice in place. The size of the teams varied between 2 and 20 people. We always use <a href="https://en.wikipedia.org/wiki/Agile_software_development">“agile-ish” methodology</a> with weekly sprint meetings.</p><h3><strong>What to look for when choosing a tool for a software development project</strong></h3><p>In our experience agile methodology is perfect for startups and small companies. That’s why we lean towards tools that support this “flow”. When running a technical startup and using a project management tool you want to be able to:</p><ul><li>Plan tickets for the two to three upcoming weeks and see the plan on one screen. So it’s clear what, when and in what order.</li><li>Get time or complexity estimations from developers on every ticket, so you can prioritize stuff.</li><li>Monitor project’s velocity.</li><li>Handle hundreds of tickets on one screen (you don’t want to scroll back and forth).</li><li>Quickly see what’s in progress, what waits, quickly distinguish features, from bugs and from chores.</li></ul><p>Based on the above requirements, we have been using Pivotal Tracker for most of our software development projects. For projects from €15.000 to €1M, from 2 months up to 3 years and counting, from 2 up to 15 people involved in the project. It’s kind of like Ruby on Rails in the Ruby frameworks world. It follows a convention over configuration principle, thus most of the concerns of the software development in a lean startup company are addressed from the very start.</p><p>Here is an example Pivotal Tracker board (project).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WjrwCj75w9csXH0AbyGGKQ.png" /></figure><p>Similar to Pivotal Tracker is Jira. It’s much more flexible, so it allows you to design your own flows. For example, a ticket can start as an idea, go through a designing phase by a design team, then through implementation, user experience testing by one team, again through implementation, deployment by another team, A/B testing and so on. However, you have to pay for the flexibility with administrative time and ease of use.</p><h3><strong>What to look for when choosing a project management tool for less technical stuff</strong></h3><p>Besides the software product, there will be other matters to be organized in your company. Things like orchestrating sales and marketing efforts, recruitment processes or onboarding/offboarding employees’/client’s projects. Based on our experience such a tool should allow you to:</p><ul><li>Create multiple named lists, so you can map your process (funnel) properly</li><li>Create multiple checklists within tickets; so for example, when recruiting for the 10th time none of the steps will be forgotten (and you have this feeling of accomplishment when checking a task within a list)</li><li>Allow tickets and board templating; there are tons of use cases here, a template for a recruitment candidate card, a template for project’s onboarding board, etc</li></ul><p>Here we suggest using Trello. Workflows in each of the “departments” tend to differ and Trello boards can be easily adapted to represent them. The tool will adjust to you and not the other way around. What is more, it’s very intuitive and easy to use even for a non-technical person.</p><p>Below is a hiring board by 42Hire:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p6phm3f3OiE_N9I433W2JA.png" /></figure><p>You can <a href="https://42hire.com/how-you-can-use-trello-to-organize-your-hiring-funnel-2d36caad9023">read more</a> about how they mapped a real hiring process (funnel) into Trello board.</p><p>Trello is also great for presenting a process or information that a certain person has to follow or be aware of. A really useful example is an employee onboarding board. When a new employee joins the team, a copy of this board is created just for her/him to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GDHPqO1wuZpFsssSXMr_jA.png" /></figure><p>More inspirations on how to use Trello can be found here <a href="https://trello.com/inspiration">https://trello.com/inspiration</a>.</p><h3>Pivotal Tracker vs Trello</h3><p>Sometimes I get this question, “ok, but which one is better?”. The answer is as always, “It depends”. It’s hard to compare these tools because they are intended for different tasks. Once we took over a software project run on Trello and it was a nightmare. Hard to navigate through countless tickets, hard to estimate and tell how long tickets would take and how to tell what’s important given the available time. We had to build some kind of system on top of it. On the other hand, I can’t imagine squeezing PT flow into recruitment or onboarding.</p><p>We are always excited about new stuff and haven’t tried everything. Share in the comments your favourite project management tools. You can also contact me at wijet at ragnarson dot com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd2faa16a221" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to choose a bug tracker for a small startup team]]></title>
            <link>https://medium.com/ragnarson/how-to-choose-a-bug-tracker-for-a-small-startup-team-3fff659e062b?source=rss-6bbeb25cb100------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fff659e062b</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[bug-tracking]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[wijet]]></dc:creator>
            <pubDate>Fri, 14 Jul 2017 00:00:00 GMT</pubDate>
            <atom:updated>2017-07-14T13:27:33.469Z</atom:updated>
            <content:encoded><![CDATA[<p>July 14, 2017 — <a href="https://blog.ragnarson.com/authors/mariusz-pietrzyk.html">Mariusz Pietrzyk</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*M69JdAALxUtLG9_b.png" /></figure><p>Choosing a project management tool isn’t an easy task. There are tons of SaaS/web-based issue tracking tools out there (like with TODO apps for personal use.) Quora and Stack Exchange threads are full of comments written by marketing teams about these tools. It’s as easy to overshoot and choose a massive product, packed with hundreds of features, that cripples your productivity and joy, as undershoot and end up with a service that you will outgrow in a matter of weeks.</p><p>I assume that you run a small startup company. If that’s true you will most likely have two areas to align. Some kind of software product or products and the company itself. The latter includes things like marketing, recruitment, employees’ on-boarding, etc.</p><p>In our 10 years of experience we have found that these two areas are different matters and require quite different tools. Running an agile software development project requires a strict and repeatable process of defining, estimating, planning, developing, testing and deploying. There is a deadline, a list of milestones broken down into smaller tasks etc. Those are the industry standards. On the other hand, marketing or sales isn’t that “linear” at the beginning and it often differs from company to company. Committing to pay for HubSpot or Salesforce from the very start might be an exaggeration and a shot in the dark.</p><h3>Why is it important to choose the right tool?</h3><p>Your workflow within a project management tool influences factors like ease of planning, efficient execution of the plan, progress tracking, teamwork and overall team motivation. What is more, once you commit to one solution it’s not that easy to migrate halfway through (because of the vendor lock-in.) Sure, there are migration tools, but in my experience, for anything larger than a pet project, it’s never a matter of only pushing a button.</p><p>To give you more context, we have completed over 50 projects with various project management tools, from modern issue trackers to real dinosaurs. We used <a href="https://trac.edgewall.org/">Trac</a>, <a href="http://www.redmine.org/">Redmine</a>, <a href="https://lighthouseapp.com/">Lighthouse</a>, <a href="https://www.pivotaltracker.com/">Pivotal Tracker</a>, <a href="https://trello.com/">Trello</a>, <a href="https://basecamp.com/">Basecamp</a>, <a href="https://www.atlassian.com/software/jira">Jira</a>, <a href="https://guides.github.com/features/issues">GitHub Issues</a> (with and without <a href="https://huboard.com/">Huboard</a>.) And we were lucky enough to test numerous others because from time to time the client already had his tool of choice in place. The size of the teams varied between 2 and 20 people. We always use <a href="https://en.wikipedia.org/wiki/Agile_software_development">“agile-ish” methodology</a> with weekly sprint meetings.</p><h3>What to look for when choosing a tool for a software development project</h3><p>In our experience agile methodology is perfect for startups and small companies. That’s why we lean towards tools that support this “flow”. When running a technical startup and using a project management tool you want to be able to:</p><ul><li>Plan tickets for the two to three upcoming weeks and see the plan on one screen. So it’s clear what, when and in what order.</li><li>Get time or complexity estimations from developers on every ticket, so you can prioritize stuff.</li><li>Monitor project’s velocity.</li><li>Handle hundreds of tickets on one screen (you don’t want to scroll back and forth).</li><li>Quickly see what’s in progress, what waits, quickly distinguish features, from bugs and from chores.</li></ul><p>Based on the above requirements, we have been using Pivotal Tracker for most of our software development projects. For projects from €15.000 to €1M, from 2 months up to 3 years and counting, from 2 up to 15 people involved in the project. It’s kind of like Ruby on Rails in the Ruby frameworks world. It follows a convention over configuration principle, thus most of the concerns of the software development in a lean startup company are addressed from the very start.</p><p>Here is an example Pivotal Tracker board (project).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2YiWgEY6g_0BOuq9.png" /></figure><p>Similar to Pivotal Tracker is Jira. It’s much more flexible, so it allows you to design your own flows. For example, a ticket can start as an idea, go through a designing phase by a design team, then through implementation, user experience testing by one team, again through implementation, deployment by another team, A/B testing and so on. However, you have to pay for the flexibility with administrative time and ease of use.</p><h3>What to look for when choosing a project management tool for less technical stuff</h3><p>Besides the software product, there will be other matters to be organized in your company. Things like orchestrating sales and marketing efforts, recruitment processes or onboarding/offboarding employees’/client’s projects. Based on our experience such a tool should allow you to:</p><ul><li>Create multiple named lists, so you can map your process (funnel) properly</li><li>Create multiple checklists within tickets; so for example, when recruiting for the 10th time none of the steps will be forgotten (and you have this feeling of accomplishment when checking a task within a list)</li><li>Allow tickets and board templating; there are tons of use cases here, a template for a recruitment candidate card, a template for project’s onboarding board, etc</li></ul><p>Here we suggest using Trello. Workflows in each of the “departments” tend to differ and Trello boards can be easily adapted to represent them. The tool will adjust to you and not the other way around. What is more, it’s very intuitive and easy to use even for a non-technical person.</p><p>Below is a hiring board by <a href="https://42hire.com/">42Hire.com</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NAzO3DI_f-L3ogss.png" /></figure><p>You can <a href="https://42hire.com/how-you-can-use-trello-to-organize-your-hiring-funnel-2d36caad9023">read more</a> about how they mapped a real hiring process (funnel) into Trello board.</p><p>Trello is also great for presenting a process or information that a certain person has to follow or be aware of. A really useful example is an employee onboarding board. When a new employee joins the team, a copy of this board is created just for her/him to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*norzZ7_7_4bFWMnN.png" /></figure><p>More inspirations on how to use Trello can be found on <a href="https://trello.com/inspiration">Trello inspirations page</a>.</p><h3>Pivotal Tracker vs Trello</h3><p>Sometimes I get this question, “ok, but which one is better?”. The answer is as always, “It depends”. It’s hard to compare these tools because they are intended for different tasks. Once we took over a software project run on Trello and it was a nightmare. Hard to navigate through countless tickets, hard to estimate and tell how long tickets would take and how to tell what’s important given the available time. We had to build some kind of system on top of it. On the other hand, I can’t imagine squeezing PT flow into recruitment or onboarding.</p><p>We are always excited about new stuff and haven’t tried everything. Share in the comments your favourite project management tools. You can also contact me at wijet at ragnarson dot com.</p><p><em>Originally published at </em><a href="https://blog.ragnarson.com/2017/07/14/how-to-choose-a-bug-tracker-for-a-small-startup-team.html"><em>blog.ragnarson.com</em></a><em> on July 14, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fff659e062b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ragnarson/how-to-choose-a-bug-tracker-for-a-small-startup-team-3fff659e062b">How to choose a bug tracker for a small startup team</a> was originally published in <a href="https://medium.com/ragnarson">Ragnarson</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>