<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Detecting Agile BS on Engineering as a Leadership System</title>
		<link>https://engineering.hinshelwood.com/guides/detecting-agile-bs/</link>
		<description>Recent content in Detecting Agile BS on Engineering as a Leadership System</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 17 Sep 2024 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://engineering.hinshelwood.com/guides/detecting-agile-bs/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Detecting Agile BS</title>
				<link>https://engineering.hinshelwood.com/guides/detecting-agile-bs/versions/2024/</link>
				<pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
				<guid>https://engineering.hinshelwood.com/guides/detecting-agile-bs/versions/2024/</guid>
				<description>Many projects claim to be agile but are not, so leaders should look for real user involvement, continuous feedback, automation, and cross-functional collaboration to spot genuine agile practices. Key signs of “agile BS” include lack of user interaction, manual processes where automation is possible, and siloed teams. Ask targeted questions about testing, automation, user feedback, and release cycles to verify true agile delivery and ensure teams can adapt based on user needs.</description>
			</item>
	</channel>
</rss>
