<?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 Dominic Goldsworthy on Medium]]></title>
        <description><![CDATA[Stories by Dominic Goldsworthy on Medium]]></description>
        <link>https://medium.com/@dom.goldsworthy?source=rss-24490e0f060d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0w-YqsIa6hASAnB_7AWUQA.jpeg</url>
            <title>Stories by Dominic Goldsworthy on Medium</title>
            <link>https://medium.com/@dom.goldsworthy?source=rss-24490e0f060d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:59:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dom.goldsworthy/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[The Importance of Defining and Measuring ‘Done’]]></title>
            <link>https://medium.com/@dom.goldsworthy/the-importance-of-defining-and-measuring-done-5e41103d3db2?source=rss-24490e0f060d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e41103d3db2</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[features]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Dominic Goldsworthy]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 01:18:43 GMT</pubDate>
            <atom:updated>2017-12-16T01:18:43.855Z</atom:updated>
            <content:encoded><![CDATA[<p>Software projects tend to trail on when features, or improvements, lack a precise definition of ‘Done’ — a moment in time at which the team can huddle around what they’ve built, agree on its ship-ability, then revel in their achievements before confidently moving onto the next priority.</p><p>The definition of ‘Done’ allows for objective feedback and measurement of metrics to determine whether or not the project requires further attention, and to what degree the team will respond.</p><p>The effect of a never-ending project can confuse and demoralize teams. It begins to raise questions such as: <em>“is this our top priority?”, “why are we doing this?”, “how much time should we spend on this?”</em>. To avoid this distracting uncertainty considered measurement and definition of ‘Done’ should be baked into your <a href="https://svpg.com/assets/Files/goodprd.pdf">Product Requirements Document</a> with criteria that the team agrees can be achieved, measured, and validated.</p><p>An important caveat to defining ‘Done’ is that software, the ever-evolving and plastic systems built atop of a lawless landscape of business and user requirements, will never truly be ‘Done.’ To quote <a href="https://medium.com/u/4c3f4fe11e6b">John Cutler</a> on the adversity of being ‘Done’:</p><blockquote>Software is rebuilt constantly. Technology shifts constantly. Our work isn’t additive (like a perfect Mona Lisa, painted iteratively). Every day…humans and machines show up to work, and do their job. We can (and should) tear things down and start over. How we operate and what we subtract and refactor, is as important as what we add.</blockquote><blockquote>If you’re done, you’re a zombie (or dead).</blockquote><p>Additionally, depending on the team or business’s underlying principals there may not exist the luxury of achieving what some would consider a high level of ‘Done.’ One might compare ‘Done’ to ‘Quality’ which is about as subjective as your taste in music, and ridiculously hard to define.</p><p>As a team, especially if you haven’t already, it’s important to frame your projects around company values and principals. Each company principal comes with pros and cons for agreeing upon, defining, and measuring ‘Done.’ Perhaps your team is focused on the more delicate details to ensure a consistent level of quality, or maybe they can be forgiving of detail to move at pace. Whatever your team’s overarching principals may be, provide the team agrees on these principles at a foundational level.</p><h3>Choosing your Criteria</h3><p>Proper acceptance criteria for ‘Done’ are indicative of a well-thought-out solution; they should frame the conversations, decisions and final output of your team’s projects. Leaving a plan open to interpretation can risk degrading the team’s success and ability to move on with confidence.</p><ol><li>How <strong>Reliable</strong> does the solution need to be to <strong>Perform</strong>?</li></ol><p>Think about the importance and acceptable levels of reliability and performance for your solution; metrics such as connection uptime, latency, success and failure rates of the system and user interactions.</p><ul><li><em>≤ 300ms connection latency</em></li><li><em>≤ 1% connection failure rate</em></li></ul><p>2. How should the solution <strong>Scale</strong>?</p><p>Consider the solution’s need to function in situations of higher throughput, heavy-usage and how this can take full advantage of different conditions regarding performance. Can it, and does it need to, solve for small and large operations?</p><ul><li><em>capable of handling X transactions per second/minute/hour</em></li></ul><p>3. How will <strong>Usability</strong> be tracked and measured?</p><p>Does the solution require logging efforts or a <a href="http://www.usabilitybok.org/contextual-inquiry">contextual inquiry</a> to discern user errors. What is an acceptable level of user error before action should be taken?</p><ul><li><em>allow for ≤ 10% of users becoming ‘stuck’</em></li><li>see a simple guide to <a href="https://measuringu.com/sus/">Measuring Usability</a> the “System Usability Scale”</li></ul><p>4. To what degree will the business happily <strong>Support</strong> the product?</p><p>Support comes at a cost for your team members who are both directly and indirectly ‘responsible.’ What is a reasonable amount of support your team is willing and capable of providing? Are you open to accepting increased levels of support to ship the product faster? Is the solution aiming to be support-free allowing you to scale faster?</p><h3>Measure &amp; Respond</h3><p>Your team has agreed upon the feasible criteria, set metrics of either a quantitative or qualitative nature, shipped the solution that meets your standard and now it’s time to learn how it’s performing. Ensure you have feedback loops in place to measure ‘Done’ whether in the form of logs, crash and error reports, customer feedback surveys, contextual inquiries or internal team feedback relative to the metric you are measuring.</p><p>The findings should remain public, an ideal place for results to live is alongside your Product Requirements to add a retrospective layer to work completed.</p><p>With a gauge to monitor ‘Done’ the team can wholly agree upon when and how to respond. Consider how the learnings can be interweaved with work ‘In Progress’ to avoid the learnings from becoming stale.</p><p>‘Done’ will inevitably fade as your team discovers new requirements via feedback from both your customers and the business. However, be wary not to pile these discoveries on top of the existing project. Gather the feedback to create a new project, with new requirements, new metrics and a new definition of ‘Done.’</p><p><em>This is my first piece of a new writing endeavour:, I am going to share ideas, insights, and learnings from working in software teams of varying sizes as well as other aspects of my own business. If you enjoyed this piece, please provide your feedback and thoughts in the comments.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e41103d3db2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>