<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Chris</title>
    <description>The latest articles on Forem by Chris (@twentyonehundred).</description>
    <link>https://forem.com/twentyonehundred</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F134346%2F68cd43ab-e3a6-4a50-86dc-8cc3ae18b19e.jpg</url>
      <title>Forem: Chris</title>
      <link>https://forem.com/twentyonehundred</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/twentyonehundred"/>
    <language>en</language>
    <item>
      <title>How do you create accurate quotes and stick to them?</title>
      <dc:creator>Chris</dc:creator>
      <pubDate>Wed, 20 Feb 2019 12:24:26 +0000</pubDate>
      <link>https://forem.com/twentyonehundred/how-do-you-create-accurate-quotes-and-stick-to-them-11bi</link>
      <guid>https://forem.com/twentyonehundred/how-do-you-create-accurate-quotes-and-stick-to-them-11bi</guid>
      <description>&lt;p&gt;Something that I and colleagues sometimes struggle with is creating accurate quotes / estimations / timings, &lt;em&gt;whatever&lt;/em&gt; you call them. These quotes are &lt;em&gt;usually&lt;/em&gt; given in hours or days, which is translated into an actual $$$ cost. The hard part is making them as accurate as possible, so that we don't let the &lt;strong&gt;scope creep&lt;/strong&gt;, smash &lt;strong&gt;past our budget&lt;/strong&gt; and end up having a very &lt;strong&gt;awkward conversation&lt;/strong&gt; with a client.&lt;/p&gt;

&lt;p&gt;It seems that they are two main ways to attack this; either you do whatever you can to understand as much &lt;strong&gt;as possible about the task or project beforehand&lt;/strong&gt;, &lt;em&gt;or&lt;/em&gt; you &lt;strong&gt;intentionally leave some ambiguity and room&lt;/strong&gt; in the project and in the budget to allow for some wiggle room.&lt;/p&gt;

&lt;p&gt;Both options seem to have positives and negatives, as with the &lt;em&gt;former&lt;/em&gt;, it can be very difficult to lock down every possible eventuality that can arise with some clients. I can spend an hour, a day or a week on a specification sometimes and (apart from already haven taken up a week) I can still be blindsided by something that me or the client overlooked or that we understood would work differently.&lt;/p&gt;

&lt;p&gt;The &lt;em&gt;latter&lt;/em&gt; option however where we leave the project somewhat open-ended is a more difficult sell initially, and doesn't &lt;em&gt;really&lt;/em&gt; seem to address the issue and help me to be more accurate.&lt;/p&gt;

&lt;p&gt;I am addressing this problem from an agency standpoint. So the projects, clients and even tech can vary quite a bit. We do what we can to sell what we know best, but that is always evolving and changing.&lt;/p&gt;

&lt;p&gt;I'd really be interested to hear what anyone else does in these sorts of situations or in similar circumstances!&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>help</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
