<?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 David Clarke on Medium]]></title>
        <description><![CDATA[Stories by David Clarke on Medium]]></description>
        <link>https://medium.com/@dnjclarke?source=rss-c8c8a832983f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*c0ORsqI2FDlm4-GRKpWTzA@2x.jpeg</url>
            <title>Stories by David Clarke on Medium</title>
            <link>https://medium.com/@dnjclarke?source=rss-c8c8a832983f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:35:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dnjclarke/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[Five Questions That Define Your Disaster Recovery Readiness]]></title>
            <link>https://medium.com/@dnjclarke/five-questions-that-define-your-disaster-recovery-readiness-aa6e70d254a2?source=rss-c8c8a832983f------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa6e70d254a2</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[disaster-recovery]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[David Clarke]]></dc:creator>
            <pubDate>Mon, 20 Oct 2025 20:28:33 GMT</pubDate>
            <atom:updated>2025-10-20T20:28:33.052Z</atom:updated>
            <content:encoded><![CDATA[<p>Every organisation says they have a disaster recovery plan.</p><p>Few have ever tested it.</p><p>And even fewer could actually rebuild their platform if everything disappeared tomorrow.</p><p>Disaster recovery isn’t a checklist – it’s a proof of capability.</p><p>The only way to know if your organisation is truly ready is to ask uncomfortable questions and be honest about the answers.</p><p>Here are five that matter most.</p><h3>Have You Ever Recovered Your Platform?</h3><p>A recovery plan that’s never been executed is just a document.</p><p>Until you’ve actually recovered your systems in a realistic exercise, you don’t know how long it really takes, what silently fails, or who panics under pressure.</p><p>Run a full or partial recovery drill. Measure how long it takes to bring core services back, validate data, and confirm everything is functional.</p><p>The gap between a plan and a tested recovery can mean the difference between hours of downtime and days of chaos.</p><h3>Is There a Written Procedure?</h3><p>When disaster strikes, people don’t rise to the occasion – they fall back on what’s documented.</p><p>A clear, written, and accessible procedure is your best defense against confusion.</p><p>It should include step-by-step recovery actions, roles and responsibilities with escalation paths, communication plans for internal and external stakeholders, and the locations of backups, credentials, and documentation.</p><p>If your recovery plan lives only in someone’s head or an outdated internal page, you don’t have a plan – you have a liability.</p><p>Treat documentation as a living asset, reviewed after every test or major system change.</p><h3>Did the Team Do The DR Without Access to Any Existing Platform?</h3><p>A real recovery test assumes the worst case: no production environment, no internal tools, maybe not even your chat system.</p><p>Could your team rebuild from nothing?</p><p>Try performing a recovery with no access to your current infrastructure – no shared drives, automation scripts, or management consoles.</p><p>If your process only works when your systems are still half-alive, it’s not recovery – it’s just a reboot.</p><h3>Were Any Shared Resources Reused (Like Databases or S3 Buckets)?</h3><p>Many so-called successful recovery tests depend on shared resources that weren’t actually lost. Maybe the database was still online. Maybe the S3 bucket was the same one used in production. Maybe the authentication service was untouched.</p><p>That’s not a real test.</p><p>A true recovery should rebuild all infrastructure from code or templates, restore data from backups, and validate that no hidden dependencies remain.</p><p>If your recovery depends on systems that might also fail, you’re not testing resilience – you’re testing luck.</p><h3>Did Someone Do It Who Was Not Very Familiar with the Platform?</h3><p>The ultimate test of readiness: can someone who didn’t build the system recover it successfully?</p><p>In most teams, a few experts hold the critical knowledge. But disasters don’t wait for them to be online.</p><p>Have a different engineer or even another team perform the recovery using only the documentation. Where they struggle, your plan needs work.</p><p>If your recovery only works when the original engineers are present, you haven’t built resilience – you’ve built dependency.</p><h3>Final Thoughts</h3><p>Disaster recovery isn’t about perfection – it’s about proof. Proof that your systems can be rebuilt. Proof that your documentation works. Proof that your people are ready, even when the experts aren’t around.</p><p>You can’t prevent disasters. But you can choose whether you’ll be the team that recovers confidently or the one that scrambles desperately.</p><p>The difference lies in the questions you’re willing to ask and the honesty of your answers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa6e70d254a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unfinished business: Scrumbut and Immutability]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/serious-scrum/unfinished-business-scrumbut-and-immutability-6eb29cb2c276?source=rss-c8c8a832983f------2"><img src="https://cdn-images-1.medium.com/max/2600/1*L6d99l52If8whEDkupQkQw.jpeg" width="3000"></a></p><p class="medium-feed-snippet">Words are important&#x200A;&#x2014;&#x200A;I think it&#x2019;s time we thought carefully about terms like Scrumbut and immutable.</p><p class="medium-feed-link"><a href="https://medium.com/serious-scrum/unfinished-business-scrumbut-and-immutability-6eb29cb2c276?source=rss-c8c8a832983f------2">Continue reading on Serious Scrum »</a></p></div>]]></description>
            <link>https://medium.com/serious-scrum/unfinished-business-scrumbut-and-immutability-6eb29cb2c276?source=rss-c8c8a832983f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6eb29cb2c276</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[serious-scrum]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[David Clarke]]></dc:creator>
            <pubDate>Fri, 04 Oct 2019 06:24:46 GMT</pubDate>
            <atom:updated>2019-10-04T06:24:46.940Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Retros Should Be Awkward Sometimes]]></title>
            <link>https://medium.com/serious-scrum/retros-should-be-awkward-sometimes-4949c9d48545?source=rss-c8c8a832983f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4949c9d48545</guid>
            <category><![CDATA[retro]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[serious-scrum]]></category>
            <dc:creator><![CDATA[David Clarke]]></dc:creator>
            <pubDate>Fri, 20 Sep 2019 12:51:50 GMT</pubDate>
            <atom:updated>2019-10-01T06:08:28.741Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DD1XCOQKFiKM9OApabc0qw.jpeg" /><figcaption>Image by <a href="https://pixabay.com/users/PDPics-44804/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=389944">PDPics</a> from <a href="https://pixabay.com/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=389944">Pixabay</a></figcaption></figure><p>An objective of the Sprint Retrospective, according to the Scrum Guide, is to:</p><p><em>Inspect how the last Sprint went with regards to people, relationships, process, and tools</em></p><p>This <strong><em>should </em></strong>sometimes lead to uncomfortable discussions and tough decisions. Retrospectives should sometimes result in change that impacts <em>people, relationships, process, and tool </em>in significant ways.</p><p>So why are Retrospectives often timid affairs with discussions of Backlog Items that were not quite ready to work on or issues deploying a Feature?</p><p>Let’s take some examples of conversations that should sometimes be happening:</p><h3>No more full-time Scrum Master</h3><p><strong>Raised at Retro:</strong> ‘We don’t think we need a full-time Scrum Master anymore. We can share the role between us, we have been together as a team for a long time and have good relationships with the rest of the business.‘</p><p><strong>Why would this not come up?</strong> Talking about roles means discussing a subject that impacts our colleagues and friends. Such transparency and frankness is not yet part of the culture of many teams and organisations.</p><h3>Feeling let down by team members</h3><p><strong>Raised at Retro: ‘</strong>We don’t think certain teams members (they would not name who) took the Sprint seriously and we feel let down. This has happened three or four times now in recent months. We would like everyone to try and take things more seriously or maybe consider finding other teams.’</p><p><strong>Why would this not come up? </strong>Discussing individuals’ commitment to a Sprint and to their Team means being direct. And it does not come naturally to a lot of people to be outspoken about their feelings.</p><h3>Stop doing Retrospectives every Sprint</h3><p><strong>Raised at Retro:</strong> ‘We feel we don’t often get much out of our Retrospectives any more and feel we could use the time more productively. We only want to do a Retro when we all feel we need one.’</p><p><strong>Why would this not come up? </strong>The Scrum Guide does not permit Scrum to be changed and so this raises an awkward problem, in that, if the retro change is enacted, according to the Scrum Guide, the Team is no longer able to say they are doing Scrum. So often discussions about the Teams’ use of the Scrum framework are dismissed altogether.</p><h3>We have a lot of ideas for change that never happen</h3><p><strong>Raised at Retro:</strong> ‘We have a long list of improvements items that never get addressed. And we frequently raise the same issues in Retros.’</p><p><strong>Why would this not come up? </strong>It’s very easy to gather a long list of improvement actions but nothing is worse for moral than great ideas for change languishing in a Backlog. Making change can be hard if it means getting buy from the wider organisation — outside of the Scrum Team. Teams may be reluctant to push for change if it means they will be in the spotlight.</p><h3>Conclusion</h3><p>Sometimes you have to be prepared to shake things up and experiment with breaking the rules to figure out what is important.</p><p>Retrospectives should be challenging. If your Retros are not encouraging the Team to question all aspects of the way they work and occasionally experiment with significant change then you are missing an opportunity.</p><p>The mark of good Retrospectives is that they help both immature and mature teams to find improvements and stay on the rails. Mature teams may be very comfortable and not keen on change. Immature teams may try to make radical changes. It does not matter what the conversion is, as long as it is happening.</p><p>It is the responsibility of the entire Scrum Team to find ways get everyone to fully participate in Retrospectives and I think a good indication that Retrospectives are working well is that sometimes they get a little awkward!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*qsg-zjcnz5A8B1xmBbdIfw.png" /><figcaption><a href="https://medium.com/serious-scrum/your-invitation-to-the-serious-scrum-slack-workspace-f424aeea4093?sk=e8334e6ee505a85ae6b9d2a1ce37219c">Do you want to write for Serious Scrum or seriously discuss Scrum?</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4949c9d48545" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serious-scrum/retros-should-be-awkward-sometimes-4949c9d48545">Retros Should Be Awkward Sometimes</a> was originally published in <a href="https://medium.com/serious-scrum">Serious Scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do You Really Know Scrum?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/serious-scrum/do-you-really-know-scrum-a11f87da88f7?source=rss-c8c8a832983f------2"><img src="https://cdn-images-1.medium.com/max/1379/1*9gVhDOhAuEzjsdzyW1Sw8w.png" width="1379"></a></p><p class="medium-feed-snippet">Not that many people read the Scrum Guide. But everyone thinks they understand Scrum.</p><p class="medium-feed-link"><a href="https://medium.com/serious-scrum/do-you-really-know-scrum-a11f87da88f7?source=rss-c8c8a832983f------2">Continue reading on Serious Scrum »</a></p></div>]]></description>
            <link>https://medium.com/serious-scrum/do-you-really-know-scrum-a11f87da88f7?source=rss-c8c8a832983f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a11f87da88f7</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[serious-scrum]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[David Clarke]]></dc:creator>
            <pubDate>Thu, 05 Sep 2019 14:00:04 GMT</pubDate>
            <atom:updated>2019-10-01T06:16:23.972Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[3 Classic Comp. Sci. Books You Should have Read by Now]]></title>
            <link>https://medium.com/@dnjclarke/3-classic-compsci-books-you-should-have-read-by-now-fc70a8a87ec?source=rss-c8c8a832983f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc70a8a87ec</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[David Clarke]]></dc:creator>
            <pubDate>Mon, 26 Aug 2019 09:59:13 GMT</pubDate>
            <atom:updated>2019-08-26T14:41:06.266Z</atom:updated>
            <content:encoded><![CDATA[<h3>Compilers — Principles, Techniques and Tools</h3><p>Who did not write their first LR parser with this book open in the lab at 12.30AM? The tools might have changed but the principles and techniques are still relevant. And the book has a dragon on the front, what’s not to love?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*Ez-0je1jxF-2DtLnqKVNCA.png" /></figure><h3>The Mythical Man-Month: Essays on Software Engineering</h3><p>Many of the essays in this book are revered by engineers and Agile gurus. No Silver Bullet discusses accidental /essential complexity and the creative aspect of programming. Some lessons still have not been learnt. The title essay argues that adding people to projects results in diminishing returns due to combinatorial explosion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*Druppe-nWA4H5aLptlWtDA.png" /></figure><h3>The C Programming Language</h3><p>Even if you don’t code C you would grok this book. It’s beautifully written by authors who clearly love programming and love C as a High-level language. My copy rarely left my side during my twenties. 2nd edition of course!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*pTReFUB_n3KzwUnRpOf6Fg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc70a8a87ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You’re Measuring the Wrong Things..]]></title>
            <link>https://medium.com/series/youre-measuring-the-wrong-things-57b6cc66d130?source=rss-c8c8a832983f------2</link>
            <guid isPermaLink="false">https://medium.com/p/57b6cc66d130</guid>
            <dc:creator><![CDATA[David Clarke]]></dc:creator>
            <pubDate>Mon, 26 Aug 2019 09:10:50 GMT</pubDate>
            <atom:updated>2019-08-26T09:12:06.651Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/354/1*ggM40yLshQ06eLHh6mQatg.png" /></figure><p>Measure the time engineers say they are spending doing stuff not related to building software and professional development.</p><p>Then figure out how to reduce it.</p><p>Measure the ratio of QA folks / Engineers.</p><p>Reduce QA and focus on test quality. Have QA merge with feature teams.</p><p>Measure how many folks in your group are committing to your git repos.</p><p>Increase it. Aim high.</p><p>Measure the hurdles and time required to put code into production.</p><p>Every hurdle is another reason an engineer will leave your organisation and another way in which a feature will be delayed.</p><p>Measure the level of inner sourcing within your organisation.</p><p>You can do this by measuring the ratio of contributors /committers.</p><p>Improve it. The more folks that can make changes to code across the organisation the better.</p><p>Measure the number of meetings that don’t have an agenda and the number of wasted hours they result in.</p><blockquote><em>Measure the open source contributions your teams are making.</em></blockquote><p>They are a great indicator of your engineering teams’ maturity.</p><p>More to follow…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57b6cc66d130" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Should Start Coding Again]]></title>
            <link>https://medium.com/@dnjclarke/why-its-good-to-keep-coding-a1fd60fc7231?source=rss-c8c8a832983f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1fd60fc7231</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[David Clarke]]></dc:creator>
            <pubDate>Sat, 24 Aug 2019 16:54:03 GMT</pubDate>
            <atom:updated>2019-08-26T14:50:52.946Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*IXBIYkScsn-ZiiUr8Vznng.png" /></figure><p>I used to code a lot.</p><p>I spent my teens and twenties coding, first as a hobby and then as a researcher of distributed computing languages. I built Petrochemical systems emulations and built products for a non-profit. It was great fun and I loved it.</p><p>Slowly, though, as I became more senior I started to get pulled into organisational change stuff. In my thirties I spent a lot of time helping teams adopt frameworks and practices like Scrum, Kanban, XP (and later even SAFe, LeSS, DAD); writing user stories; acceptance criteria with GWTs etc. You know the type of thing.</p><p>This transition made sense to me at the time, and I think I was OK at it because I could relate to the folks in the teams. After all, I had been there myself, both as a PO and developer. Folks call it being an agile coach nowadays. I slowly moved away from coding altogether.</p><p>But a few years ago I became more involved in a side project, and one day just rolled my sleeves up to help develop again. I was terrible and no use to the team. I was really slow. I did not know the languages, IDEs, tooling, frameworks or patterns. Pretty much everything had moved on. It was an eye-opener for me.</p><p>It really dawned on me that I could not possibly be as good at helping teams as I had been some ten years earlier. Although I knew a lot about the product and organisational side of things, much of my knowledge for how modern software was being built was defunct.</p><p>So I decided to take the time to get up to speed with Python, Java and Javascript and their ecosystems. It was hard. But as the pieces fell into place I started to remember why I had loved developing so much. And have a rekindled enthusiasm for building software.</p><p>To be clear, i’m not criticising any of the folks coaching Agile or agile methods. I just know that I am in a much better place since I took the time to relearn my craft, and I am not planning to stop again any time soon.</p><p>It’s way too much fun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1fd60fc7231" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>