<?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 Jonathan Law on Medium]]></title>
        <description><![CDATA[Stories by Jonathan Law on Medium]]></description>
        <link>https://medium.com/@jonathan.law.?source=rss-3f759180eb86------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gc1td_3YdXxwyLeG6o8MKw.png</url>
            <title>Stories by Jonathan Law on Medium</title>
            <link>https://medium.com/@jonathan.law.?source=rss-3f759180eb86------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:41:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jonathan.law./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 Art of Being Consistently Less Wrong]]></title>
            <link>https://medium.com/ncr-edinburgh/the-art-of-being-consistently-less-wrong-7d51f30d89eb?source=rss-3f759180eb86------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d51f30d89eb</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jonathan Law]]></dc:creator>
            <pubDate>Fri, 18 May 2018 14:57:24 GMT</pubDate>
            <atom:updated>2018-05-18T14:57:24.936Z</atom:updated>
            <content:encoded><![CDATA[<h4>Practical advice to fight the fear of agile estimation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/1*cNVRyPCQCWpZQ55BKQXOlQ.jpeg" /></figure><p><strong>Note: This blog post has been migrated, and was originally published on 24th November 2014.</strong></p><p>When teams adopt agile, there is one activity that always causes disagreement, confusion, and stress: the dreaded estimation of stories.</p><p>For a team new to the concepts presented in agile, especially a team with experience of more traditional project-managed development, the idea of assigning abstract values to their stories is usually unsettling. You will often hear comments like:</p><blockquote>“What is a point really? Is it a day?”</blockquote><blockquote>“I need to understand the requirements more. I can’t possibly commit to a size in this meeting.”</blockquote><blockquote>“What if we say it is a 5 point story, but we find out it is a 50? Will we get in trouble?”</blockquote><p>Stop. Take a breath. As a team, accept the liberating fact that <strong><em>your estimate is WRONG</em></strong>. No matter what you do, who is in the meeting, and how much knowledge of the work you have, <strong><em>you are WRONG to some degree.</em></strong></p><p>Does that make you feel better? Probably not. As Engineers, we are conditioned to be precise, to back up our views with evidence and commit. It is not a natural feeling to take a punt on (normally) very little information and pick a card from the planning poker deck.</p><p>Don’t try to be exact; try to be <strong><em>LESS WRONG</em></strong>. The only way you can be less wrong is to learn. The only way to learn is to do. Letting go of correctness and embracing the desire to be less wrong can help a team change what is normally a painful, drawn out meeting into a quick, focused and collaborative discussion. Get past the estimation and get back to delivering features.</p><h3>How do we learn to be consistently LESS WRONG?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qmC1dhOEMw_4awMaT-Uf8w.jpeg" /></figure><h4>Estimating together means less errors</h4><p>You should already be getting the benefit of this. During your planning poker session, the team are working together to assign the points to a story.</p><p>You listen to the story details, ask for clarification if required and pick the points individually without being influenced by others in the team. This allows us to quickly see if everyone agrees. If they do, you can have some confidence in your points allocation but remember:</p><ul><li>Take time to question the outliers. They may have considered something that is important.</li><li>Learn from previous mistakes. For example:</li></ul><blockquote>“We didn’t consider the effort for documentation last time.”</blockquote><blockquote>“We forgot that a similar story required us to build a complex test scenario to allow us to demo it.”</blockquote><h4>Don’t estimate, compare.</h4><p>People generally find estimation difficult, but we are very good at comparing. When people are asked: <em>“Estimate how many pages are in the phone book?”, </em>there will be a wide variety of responses, and many might will struggle to give an answer.</p><p>If we ask the same people to tell us: “<em>How big is the phone book compared to a standard paperback? Is it bigger, smaller? Is it twice as big? Three times?” </em>You will still get a variety of answers, but people generally won’t struggle so much to at least offer their views.</p><p>When you are estimating, use relative estimation based on data from your previous sprints. Ask questions like:</p><blockquote>“We don’t fully understand this, but do you think it feels about the same effort as the story from the last sprint?”</blockquote><blockquote>“We know it is bigger than the last story, but do you think it is twice as big?”</blockquote><h4>Don’t dwell on mistakes</h4><p>Drawn out meetings full of guilt and worry about missed stories in a sprint should be avoided. Learn from what happened, and try to be less wrong next time. In agile, we sacrifice extended analysis of requirements to focus on discovery through doing. There is an acceptance that the work will start without full knowledge, so misunderstandings and issues are expected. The great news is that we find these out early in the process rather than months into the project.</p><p>Next time you find yourself struggling to assign story points, try to relax, focus less on sizing and more on comparing it to previous stories, remember what mistakes were made in previous sprints and learn from them.</p><p>As the team becomes consistently less wrong, the meetings should be easier and faster, and you will wonder what the fuss was about when you first started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d51f30d89eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ncr-edinburgh/the-art-of-being-consistently-less-wrong-7d51f30d89eb">The Art of Being Consistently Less Wrong</a> was originally published in <a href="https://medium.com/ncr-edinburgh">NCR Edinburgh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Darwin Information Typing Architecture]]></title>
            <link>https://medium.com/ncr-edinburgh/darwin-information-typing-architecture-b9ad1d318095?source=rss-3f759180eb86------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9ad1d318095</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jonathan Law]]></dc:creator>
            <pubDate>Fri, 04 May 2018 09:42:22 GMT</pubDate>
            <atom:updated>2018-05-04T09:42:22.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MUohbbavedE5Jcy3amfJxA.jpeg" /></figure><p><strong>Note: This blog post has been migrated, and was originally published on 21st February 2017.</strong></p><p><strong>Darwin Information Typing Architecture</strong> (DITA) is an XML-based open standard for structuring and publishing technical documentation. It is a popular standard for creating topic-based minimalist documentation sets with the goal of delivering what customers actually need to know, when they need to know it.</p><p>The standard is managed by the <strong>Organization for the Advancement of Structured Information Standards</strong> (OASIS) DITA Technical Committee. It first started as a proprietary standard at IBM with the goal of creating content that could be efficiently reused in multiple output formats.</p><p>However, DITA is also known for being restrictive and best suited to highly structured products. Could it really be useful for an evolving software product, developed in an Agile environment?</p><p>The answer, perhaps surprisingly, is yes.</p><p>DITA builds on the fundamental principle that all technical authors must follow. That is, the aim of the documentation is not to describe how the product works but to help the users of the product to accomplish their goals.</p><p>It does this by advocating task-orientated documentation as you would expect, but goes further and expects authors to split the user’s tasks into mental and physical steps. The reason for this is to separate the information required for decision-making from the actual actions taken to do the task. By separating the information in this way, and by knowing the audiences they are writing for, authors can write very clear step-by-step instructions, conceptual information and reference material which can then be assembled into various documentation products for the different audiences.</p><p>The distinct nature of each type of information is captured in the four DITA Topic Types — Concept, Task, Reference and Glossary. These types can be specialised to meet individual company or industry requirements without losing their basic properties which are always inherited, hence the reference to Darwin in the name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*SSxFGcml-fn9p4HLRb19Ig.jpeg" /><figcaption>DITA Topics visualised</figcaption></figure><p>As well as the topics themselves, authors must write DITA Maps to arrange the content of topics to form documents such as online help topics, user guides and reference manuals. Content references (known elsewhere as snippets) and nested topics can be used to reuse content within topics to avoid duplication.</p><p>Here is an example, from <a href="https://dita.xml.org/">dita.xml.org</a>, to show how a DITA Maps are used to produce different documents from different combinations of the same set of source topics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*IW7udYnNvOglJA45uyLa4g.png" /><figcaption>DITA Maps used to produce different documents</figcaption></figure><p>DITA tools which create the necessary code and help build the map files are available but these are expensive and difficult to learn. We are unlikely to adopt this standard any time soon.</p><p>However, we could separate our topics into the DITA types of Task, Concept, Reference and Glossary. This would have several benefits for ourselves and our users. Users would find the information they need more quickly and have to read less to achieve their goals. It would also be easier for the documentation to keep pace with a changing product.</p><p>In this Agile environment, the ability to divide content sensibly into small, maintainable, reusable chunks makes perfect sense.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9ad1d318095" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ncr-edinburgh/darwin-information-typing-architecture-b9ad1d318095">Darwin Information Typing Architecture</a> was originally published in <a href="https://medium.com/ncr-edinburgh">NCR Edinburgh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coffee Morning: Mostly Cakes]]></title>
            <link>https://medium.com/ncr-edinburgh/coffee-morning-mostly-cakes-7681f123f398?source=rss-3f759180eb86------2</link>
            <guid isPermaLink="false">https://medium.com/p/7681f123f398</guid>
            <category><![CDATA[coffee]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ncr-edinburgh]]></category>
            <category><![CDATA[macmillan-cancer]]></category>
            <category><![CDATA[cake]]></category>
            <dc:creator><![CDATA[Jonathan Law]]></dc:creator>
            <pubDate>Tue, 03 Oct 2017 09:59:17 GMT</pubDate>
            <atom:updated>2017-10-03T09:59:17.276Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many sides to NCR Edinburgh life, but the most important is, of course, coffee and cake.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MYxKC_B9IGiPHj7T1Eq8wA.jpeg" /><figcaption>Macmillan Coffee Morning</figcaption></figure><p>On 29th September 2017, NCR Edinburgh participated in <a href="https://www.macmillan.org.uk/">Macmillan’s</a> Coffee Morning Project, by hosting a Coffee Morning in its own Village Green. Macmillan has been inviting people all over the UK to host Coffee Morning fundraisers every year since 1990, raising over £16.5 million in the process.</p><p>With each slice, a 50p donation was requested, with the proceeds helping Macmillian continue to provide vital support to those affected by cancer.</p><p>Our talented bakers provided a Bakewell Cake, an Orange Almond &amp; Poppy Seed Cake, a Malteser Fridge Cake and many, many more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uF-fuBFbG-_JWhAVbrYuhQ.jpeg" /><figcaption>The cakes are ready for us.</figcaption></figure><p>The cakes were laid out and ready, but not to be touched until precisely 11am, and when the clock struck, people arrived in droves.</p><p>The treats were speedily picked up, and the coffee machine worked in overdrive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oo1f-lbLvdJdDlGlYACPcA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KiqA2VGtmLV8ClfADRZf4A.jpeg" /><figcaption>Coffee and cake appears to be a popular hit</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*0qVfpIFkB8mW3pvPAYsF7w.png" /><figcaption>£337.02 raised for Macmillan.</figcaption></figure><p>Luckily, the donation box filled up, and we managed to raise <strong>£337.02.</strong></p><p>With plates and tins cleared, coffee beans running low, and wallets emptied, the morning was a great success.</p><p>Bring on next year.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7681f123f398" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ncr-edinburgh/coffee-morning-mostly-cakes-7681f123f398">Coffee Morning: Mostly Cakes</a> was originally published in <a href="https://medium.com/ncr-edinburgh">NCR Edinburgh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>