<?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>SDLC on Allen Ziegenfus</title><link>https://allenz.net/tags/sdlc/</link><description>Recent content in SDLC on Allen Ziegenfus</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 03 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://allenz.net/tags/sdlc/index.xml" rel="self" type="application/rss+xml"/><item><title>Retrospectives: an opportunity for double-loop learning</title><link>https://allenz.net/writing/retrospectives-are-double-loop-learning/</link><pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate><guid>https://allenz.net/writing/retrospectives-are-double-loop-learning/</guid><description>Most of a team&amp;rsquo;s week is single-loop — execute the process, close the ticket. The retrospective is the one ritual that questions the process itself, and what quietly breaks when a team skips it.</description></item><item><title>What is code review actually for?</title><link>https://allenz.net/writing/what-code-review-is-actually-for/</link><pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate><guid>https://allenz.net/writing/what-code-review-is-actually-for/</guid><description>The mandatory, blocking PR gate is barely fifteen years old — and the research says review&amp;rsquo;s value diverges from its justification. What code review is actually for, and why most of its jobs are better served elsewhere.</description></item></channel></rss>