<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Engineering-Management on Jake Worth</title><link>https://jakeworth.com/tags/engineering-management/</link><description>Recent content in Engineering-Management on Jake Worth</description><image><title>Jake Worth</title><url>https://jakeworth.com/twittercard.png</url><link>https://jakeworth.com/twittercard.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 30 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jakeworth.com/tags/engineering-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Catastrophic Mistakes Are a Team Failure</title><link>https://jakeworth.com/posts/catastrophic-mistakes-are-a-team-failure/</link><pubDate>Mon, 20 Apr 2026 12:11:33 -0400</pubDate><guid>https://jakeworth.com/posts/catastrophic-mistakes-are-a-team-failure/</guid><description>&lt;p&gt;If people can make catastrophic mistakes on your team, the process is broken.&lt;/p&gt;</description></item><item><title>How I Run a Fully-Remote Software Engineering Standup</title><link>https://jakeworth.com/posts/how-i-run-a-software-engineering-standup/</link><pubDate>Wed, 04 Mar 2026 10:31:38 -0500</pubDate><guid>https://jakeworth.com/posts/how-i-run-a-software-engineering-standup/</guid><description>&lt;p&gt;I&amp;rsquo;ve been participating in fully-remote software standups every day for over a decade, and over the past two years, leading them, too. Here&amp;rsquo;s how I run the best standup meetings that I can.&lt;/p&gt;</description></item><item><title>Running Great Refinement Meetings</title><link>https://jakeworth.com/posts/running-great-refinement-meetings/</link><pubDate>Mon, 01 Dec 2025 11:18:17 -0500</pubDate><guid>https://jakeworth.com/posts/running-great-refinement-meetings/</guid><description>&lt;p&gt;This year I&amp;rsquo;ve run over 25 Scrum refinement meetings; here&amp;rsquo;s what I&amp;rsquo;ve learned.&lt;/p&gt;</description></item><item><title>Being the Third Engineer</title><link>https://jakeworth.com/posts/being-the-third-engineer/</link><pubDate>Wed, 16 Oct 2024 13:37:01 -0400</pubDate><guid>https://jakeworth.com/posts/being-the-third-engineer/</guid><description>&lt;p&gt;I was the third engineer hired by my company, not counting our technical co-founder. I like that position, and it seems to play to my strengths.&lt;/p&gt;</description></item><item><title>How to Run an Agile Retrospective for Leaders</title><link>https://jakeworth.com/posts/how-to-run-an-agile-retrospective-for-leaders/</link><pubDate>Wed, 15 Mar 2023 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/how-to-run-an-agile-retrospective-for-leaders/</guid><description>&lt;p&gt;Retrospectives are one of my favorite engineering team practices. In this post,
I&amp;rsquo;ll explain why and how I run retros.&lt;/p&gt;</description></item><item><title>Weekly Summary Technique for Software Engineers</title><link>https://jakeworth.com/posts/weekly-summary-routine/</link><pubDate>Fri, 04 Feb 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/weekly-summary-routine/</guid><description>&lt;p&gt;&lt;em&gt;&amp;ldquo;What did you do this week?&amp;rdquo;&lt;/em&gt; I&amp;rsquo;ve written a weekly summary for myself and my
teams for years. It helps me think through my work and shows people what I&amp;rsquo;m
working on. In this post, I&amp;rsquo;ll explain how to use this tool.&lt;/p&gt;</description></item></channel></rss>