<?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 Dan Laasna Reuter on Medium]]></title>
        <description><![CDATA[Stories by Dan Laasna Reuter on Medium]]></description>
        <link>https://medium.com/@dan.reuter?source=rss-7a7b42831304------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*172z1Uj-L5JanFgh</url>
            <title>Stories by Dan Laasna Reuter on Medium</title>
            <link>https://medium.com/@dan.reuter?source=rss-7a7b42831304------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:28:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dan.reuter/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[Métrique à Trois]]></title>
            <link>https://medium.com/@dan.reuter/m%C3%A9trique-%C3%A0-trois-01df6d6d674e?source=rss-7a7b42831304------2</link>
            <guid isPermaLink="false">https://medium.com/p/01df6d6d674e</guid>
            <dc:creator><![CDATA[Dan Laasna Reuter]]></dc:creator>
            <pubDate>Tue, 12 Dec 2023 20:21:19 GMT</pubDate>
            <atom:updated>2023-12-12T20:21:19.837Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lkN6at5JQSAwd-fWuDqedw.jpeg" /><figcaption>FigA: Three Hills Brewing</figcaption></figure><h4>What’s the point (or three)</h4><p>Historically speaking, the Chronometer was a game changer. There were other devices used for sea faring and navigation before the Chronometer, but nothing that gave such precise and consistent accuracy; they were — and still are — the most exact portable mechanical timepieces ever produced and in fact, were only just bettered by non-portable pendulum clocks used in observatories for overall accuracy!</p><p>These devices gave the British Navy, and therefore the British Emprise itself, a significant advantage over competing agencies and allowed for almost complete domination of the sea, the lifeline of colonies and wealth at the time.</p><figure><img alt="Fig1 A Chronometer" src="https://cdn-images-1.medium.com/max/686/1*bHC6pXNuXLSnkcNdLnFiCg.jpeg" /><figcaption>Fig1: A chronometer</figcaption></figure><p>The fundamental problem that the Chronometer solved was to know where you were at any one moment in time, that was not dependent on sighting land mass (“I recognise that island!”) or clear skies (“follow the North Star!”); it answered the age-old dilemma…</p><p><strong><em>How do I know which direction to turn if I do not know where I am?</em></strong></p><p>And how many times <em>should</em> we consider that question when we look at our teams and not only how to continuously improve them, but how do we track progress?</p><p>The word Chronometer is derived from Chrono (Greek for time) and Meter (meaning to measure); what is a Chronometer; it is the ability to measure against time.</p><p>This is also neatly summarizing what Agile Metrics are, the ability to measure progress of a team over time; the oversight of whether we are on course, whether we need to move the tiller in a direction to steer us towards safety or to go faster in a safe direction.</p><p>Metrics give us the line of sight for teams in becoming more sustainable and predictable, and like a Chronometer that measures three different planes (vertical, horizontal &amp; perpendicular) against time, the same three measurements can be used to gauge where a team is with regards to Metrics.</p><h4>Why Three?</h4><p>As seen in Fig1, a chronometer uses triangles.</p><p>In surveying, navigation, astronomy, triangulation is used consistently and constantly for validating where <em>something</em> is.</p><figure><img alt="Fig2: Find my boat" src="https://cdn-images-1.medium.com/max/800/1*2DjPaBJRDNpzZzk_zjQqsg.png" /><figcaption>Fig2: Find my boat</figcaption></figure><p>Figure 2 shows how you can find my boat using triangulation; Point A and C are the constants, or the knowns where B (for Boat) is the information you seek.</p><p>We use two points to seek the third because <em>more</em> than two points add <em>uncertainty</em> to the mix and increases the risk of inaccuracy, whereas one point decreases <em>certainty </em>and only allows for a very rough estimate.</p><p>Three is the sweet spot for measuring…</p><h4>Which Three?</h4><p>This is where it gets interesting, everyone within the Agile community and beyond has their personal Metrics and reasons why they matter. This is not an attempt to disparage those opinions or metrics, but an explanation as to the three Metrics that I believe guide the team and provide the feedback and data needed for not only continuously improvement, but also to assess progress along that journey.</p><ol><li><strong>Customer Satisfaction</strong>: Simply put, it is all about your <em>CUSTOMERS. </em>Whilst the customer <em>may not always be right</em>, you need to be across them and understand how and why they are feeling. Irrespective of whether you are not for profit charity, a small start-up, or a massive conglomerate, you are creating an output that is to achieve a desired outcome for your customer and the fundamental point of Agile is the feedback loop from your customers. If your team is not “end user” facing, you will still have people who will use your output, be them internal customers or third-party partners. Get close to these people, they either pay your wages directly or will impact them indirectly! <strong><em>There is no compromise of this Metric</em>.</strong></li><li><strong>Team Satisfaction</strong>: If you have delighted customers, amazing throughput metrics but a team that is NOT happy or in disarray, how long will those other metrics remain strong? It is the Team that create the value and as the saying should go “<em>Happy Team, Happy Customers</em>” as the reverse is proven to be true! The other metrics will tell you what <em>has</em> happened, lagging metrics, but the Team Satisfaction can have the power to inform you what may happen unless there is intervention, for example, if you note there is a downturn then measures can be pit in place to resolve them before it impacts the other metrics significantly</li><li><strong>Throughput</strong>: how long does it take to get stuff done? Is it good, is it bad, is there a context for this? Lean focuses on the flow of work through the system, this measurement is vital in understanding where your blockages are, and your pain / pinch points are. Think of this as the flow of blood though; how do you know if you are about to suffer a major artery block, and subsequent severe health complications, unless you regularly check your blood pressure? There are various schools of thoughts on <em>which</em> metric to use to use, the assorted options are listed below, but my advice is to assess what you already measure, not create data from scratch!</li></ol><p>A) Lead Time: the period between the moment of making a request for delivering a product and the actual delivery. All the processes to bring a product to completion come under lead time. It also includes developing a business requirement and fixing bugs. Lead time is an important metric. The reason for this is it provides the exact time calculation for every process (e.g. from the moment a ticket is created to when it is released into Production)</p><p>B) Cycle Time: measures work processed from when it starts, it represents a team’s productivity level. Cycle Time helps you understand the effect of workflow on business performance. You can get a better overview of the capacity of your team and the flow of work from when the “value add” starts through to when it is released into Production. Cycle Time is a subset of Lead Time (see fig 3)</p><p>C) Work Age Item: a measure at task level, this metric indicates the time that passes between the start of a task and the <em>current </em>time. This is used in flow analysis for real time dashboards that provides <em>in the moment feedback</em>.</p><p>D) Blocked time: Either duration of being blocked or number of tickets blocked. This can be an indication of something that requires further attention if this is a consistent issue.</p><p>D) Churn rate: how often are tickets bought into a sprint, or tickets removed? The churn rate can be an indication of a symptom that requires further investigation.</p><p>E) Spill over per sprint: tickets not completed in a sprint can also be a sign of something that needs assessing the understanding as it can be a signal of something that can be improved.</p><p>F</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*aOG_rFWp7zLQDCfJqGdWrQ.png" /><figcaption>Fig3: Lead Time and Cycle Time in context</figcaption></figure><h4>Three Hills Brewery</h4><p>So whilst my favourite brewery is Three Hills Brewery (see links below) because of their very indulgent and dangerous B.A.B.P.A.V.K TRIPLE SEC (see FigA), my favourite set of Metrics are presented as follows…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cDCp5nlvq0eb69vG" /><figcaption>Fig4: Team metrics as presented via the Métrique à Trois</figcaption></figure><p>The selection is as follows:</p><ol><li>Median Cycle Time- From Jira on a fortnightly end of sprint basis- The “Median” removes any nasty extremities from both sides<em>- </em>we have a <em>target</em> measure of 2 days</li><li>App Store Rating- Updated on a monthly basis direct from the App Store itself- Completely independent rating — However, when it was realized that the monthly rating of 2.1 out of 5 was provided by only 82 users out of the 850,300 user base, work was undertaken to deliver a gentle nudge users to rate the app, and this in turn improved the return rate from 1:10,000 to 1:1,000, and the scores also improved as well!- There was a target that took into consideration that perfection is not the objective</li><li>Team Satisfaction- Asked after every retro or at a convenient point on a regular basis- Anonymous feedback via whichever medium suitable; MS Form for example- Rating from 1 to 4 (no fence sitting)- we also included free text for for comments that may not arise in the Retro itself</li></ol><p>However, we within the Agile community all strive for Continuous Improvement and the look and feel of report was nice, but it was onerous to do as it was a manual update each time and there was room for streamlining the look and feel to focus on the signal and remove the noise. So, following Agile Principle #10 “Simplicity”, it has been improved further to make it clean and unambiguous in its message… I give you the Métrique à Trois V2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*pRWieAzkgbm93tW1UPeRtQ.png" /><figcaption>Fig5: Métrique à Trois V2</figcaption></figure><p>This is not to say DO NOT USE ANY OTHER METRIC, as they will all give you valuable data that can be used to highlight where the problems might be, and also what to try next to fix them. There is often no single solution, no silver bullet, but a series of levers to be pulled, impact measure and understood.</p><p>But in my opinion, the main three that should be main gauge of progress towards your destination, much like the Chronometer, should be</p><ul><li>Customer</li><li>Team, and</li><li>Throughput</li></ul><h4>Epilogue</h4><p>I answer this question now to save doing so in the comments field of this article, “how does the Three Hills Brewing B.A.B.P.A.V.K TRIPLE SEC measure up?”</p><p>Using my standard approach, <em>let me tell you</em>:</p><ul><li><strong>Smell</strong>: full, robust, Dark Chocolate Orange with a sharpness edge of danger (4/4)</li><li><strong>Appearance</strong>: flows thick and consistent like a good sprint should; black gold with a head of burnt meringue (4/4)</li><li><strong>Taste</strong>: decadent, like drinking gold bullion but possibly costing more pure sip (4/4)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/0*1hisakTcI34Yorhi" /><figcaption>be careful of perfection!</figcaption></figure><p>References:</p><p><a href="https://www.plutora.com/blog/agile-metrics">Agile Metrics: The 15 That Actually Matter for Success </a>— <a href="http://plutora.com/">Plutora.com</a></p><p><a href="https://www.artyfactory.com/perspective_drawing/perspective_5.html">https://www.artyfactory.com/perspective_drawing/perspective_5.html</a></p><p><a href="https://www.sciencedirect.com/topics/engineering/mutually-perpendicular-plane">https://www.sciencedirect.com/topics/engineering/mutually-perpendicular-plane</a></p><p><a href="https://www.threehillsbrewing.com/">https://www.threehillsbrewing.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01df6d6d674e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Coaches: an opinion]]></title>
            <link>https://medium.com/@dan.reuter/agile-coaches-an-opinion-edcdb2fb8794?source=rss-7a7b42831304------2</link>
            <guid isPermaLink="false">https://medium.com/p/edcdb2fb8794</guid>
            <dc:creator><![CDATA[Dan Laasna Reuter]]></dc:creator>
            <pubDate>Tue, 05 Sep 2023 16:03:47 GMT</pubDate>
            <atom:updated>2023-09-05T16:03:47.271Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ednOuDbBecUkkfDEX3BGKQ.gif" /></figure><p>On a recent trip to Munich, I struck up a conversation with the man sitting next to me on the plane as we were approaching Amsterdam. We were working out how best to deal with missing the connecting flight after our two hour delay. He was also en route to Munich and we discussed plans and I offered my experience having been in a similar situation not six weeks previous.</p><p>He was a Sales Team Programme Manager and when he asked me what I did, I mentioned that I help facilitate the delivery of change using the Agile Mindset. He knew of Agile and the roles and then went quiet. A minute later, he turned and asked me a very simple question “what’s your biggest challenge working in Agile?”</p><p>A beat of my heart later I answered him,</p><p>“People”</p><p>He looked at me and smiled, then settled back into his seat and for the next few minutes chuckled to himself.</p><p>“People” he repeated, still chuckling.</p><h3>The Agile Coach</h3><p>And it is people; people make things happen both good and bad, yet within the main Agile Frameworks, Scrum &amp; Kanban, there are only two specific roles for people to actually fulfill; the Scrum Master and the Product Owner. Yet among all the frameworks, principles, mindset approaches a role seems to have been fashioned; that of the Agile Coach.</p><p>Both within the Agile community and beyond, there is a debate about the true value of the “Agile Coach”. Having experience from many different business sectors, at many different levels and in many different roles, I would like to offer an opinion that creates certainty about not just the Value that the role will add, but also provide signage as to how they should go about providing that value.</p><h3>So what is “success”?</h3><p>My starting point is that an Agile Coach’s success is derived from two key goals; how influential they are at Executive Level, how in touch they are at an operational level. But before I get into detail, I think defining the word “success” is critical here.</p><p>There are Agile Coaches who seem to be very successful and have continued on that trajectory, but when you speak to the teams within the company where that success took place, their opinion of the Agile Coach was not a positive one. Likewise, there are Scrum Masters aplenty out there who are superb at coaching Agile both within their teams but also influencing those above them by Showing and Doing. There are also Agile Coaches I’ve worked with who have inspired me, educated me, coached me and done everything I never knew a coach could do, and more besides.</p><p>Within the industry, there are often cited “Four Stances” that an Agile Coach can take</p><ul><li>Coaching,</li><li>Facilitating,</li><li>Mentoring,</li><li>Training</li></ul><p>These are great and are all important in How you go about achieving success, but they are not signifiers themselves of success. So what DOES define success of an Agile Coach? In my opinion, the same gauge of success that we use for those delivering the Business Value — Metrics!</p><h3>“Metric a trois”</h3><p>There are also wide variety of Metrics used to a measure a Teams Performance, my personal three most important are:</p><ul><li>Team Satisfaction (a happy team creates happy output)</li><li>Customer Satisfaction (happy output should achieve a happy outcome for the customer)</li><li>Mean Cycle Time (and all underpinned by a happy flow of work)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/0*o8fJaBER4MJRzB94" /></figure><p>This is great for the team and the Scrum Master, but as an Agile Coach, they may not have had direct involvement in these metrics, so the high or low ratings (or scores) could be in spite of the Agile Coach, not because of.</p><p>The role of the Agile Coach is to take a holistic view of these metrics across the company. The Agile Coach should be creating the environment for company wide improvements as well as supporting the eco-system for individuals as well as the teams. The Four Stances mentioned above are a way of achieving those improvements at all levels of the company.</p><h3>Health check</h3><p>Another part of gauging success is a regular “health check” across the relevant teams. This can be done via HR as a temperature check for the entire company, in addition to using Agile Maturity Assessment — or similar — to monitor progress over a longer period. The Agile Maturity assessment, despite the name, is not Agile specific but can be used to gauge progress and performance not only on a team by team basis, but also at a company level. The assessment can be a very useful prompt that Agile is not just the destination, but the journey to improve the ways of working within an organisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Nwu3RrMA9jL-aYiy" /></figure><p>These assessments / health checks should be no more than quarterly but more frequently than yearly to prevent over-saturation. This cadence can yet still indicate any negative trends and patterns before they become embedded, and also show positive trends that should be understood as well as celebrated!</p><h3>Successful</h3><p>All in all, the Healthcheck, combined with the collective teams Metric a trois over time can be used to gauge the success of an Agile Coach; they create and support the wider environment and the individual teams eco-systems.</p><p>So this provides a guide on the Agile Coach success at an Operational Level, but what about at Executive Level?</p><h3>Enterprising</h3><p>The common understanding is that the Agile Coach looks upwards; they provide Coaching, knowledge and support at the Organisational level and are expected to help influence decisions at the executive level. The common understanding is that they will do the following tasks as part of the remit:</p><ul><li>Work with organisational structure and culture to help create the environment that helps sustain and grow the Agile mindset throughout</li><li>Develop thought Leaders to be advocates and to further spread the Agile mindset</li><li>To understand the dynamics and lines of communication across teams to manage dependencies, support the removal of impediments and reduce the overall friction within the organisation.</li><li>Managing &amp; embracing change both at the team process level, but more importantly, changes at the executive level and being seen as a leader in light of change and managing the fear and the impact that change can bring about</li><li>Leadership agility is also vital; they need to be seen as a trusted advisor to and within the Leadership Team and act from an independent perspective, asking powerful questions to challenge and represent what is best for the organisation. The “Four Stances” of the Agile Coach is an important part of this task</li></ul><p>The purpose is to create the environment for sustained success across the organisation, in which Agile is the vehicle to achieve that success and the Agile Coach the driver.</p><h3>In Conclusion</h3><p>The ultimate judgement of the success of an Agile Coach is down to the people and teams creating the Business Value; Engineers, Designers, Researchers, Testers, Products Owner and everyone within Leadership that help create and support the environment.</p><p>The Health Check and the collective Metrics of the teams are a great way of determining success across a period of time as ultimately, the role of the Agile Coach is all about creating sustainable improvement across the organisation to the benefit of the organisation at every level of the organisation</p><p>In summary; “Leave It Better than You Found It {including people}” Anon</p><h3>Epilogue</h3><p>I arrived in Munich on the next available flight the following morning. I carried hand luggage only, learning from my previous experience where my checked-in bag did not arrive until the night before I was due to return. The guy who had sat next to me was not on my plane; maybe he hadn’t learnt from others and did not question the assumptions nor remove the uncertainty as soon as he could.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edcdb2fb8794" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>