<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>leadership on Tom Hickerson's Site</title><link>https://tomhickerson.com/en/tags/leadership/</link><description>Recent content in leadership on Tom Hickerson's Site</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Copyright 2023-2026</copyright><lastBuildDate>Wed, 15 Aug 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://tomhickerson.com/en/tags/leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Software Development Requires Servant Leaders</title><link>https://tomhickerson.com/en/archives/en/2018/2018-08-15-aaron-longwell-why-software-development-requires-servant-leaders-culture-foundry/</link><pubDate>Wed, 15 Aug 2018 00:00:00 +0000</pubDate><guid>https://tomhickerson.com/en/archives/en/2018/2018-08-15-aaron-longwell-why-software-development-requires-servant-leaders-culture-foundry/</guid><description>&amp;ldquo;When the business side “wins”, the developers end up in a death march. When development concerns outweigh business ones, you end up blowing the budget and deadline. Either way you’re broken. Successful software managers find ways to be flexible; to bend without breaking and to resolve the tension gradually. Servant leadership can be a guide to finding this flexibility.&amp;rdquo;
tags: programming
Aaron Longwell | Why Software Development Requires Servant Leaders | Culture Foundry</description></item></channel></rss>