<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Ian Kent</title>
    <description>The latest articles on Forem by Ian Kent (@iankent).</description>
    <link>https://forem.com/iankent</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F9808%2F2300772.png</url>
      <title>Forem: Ian Kent</title>
      <link>https://forem.com/iankent</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/iankent"/>
    <language>en</language>
    <item>
      <title>Manifesto for Technology Leadership</title>
      <dc:creator>Ian Kent</dc:creator>
      <pubDate>Wed, 29 Mar 2017 21:38:31 +0000</pubDate>
      <link>https://forem.com/iankent/manifesto-for-technology-leadership</link>
      <guid>https://forem.com/iankent/manifesto-for-technology-leadership</guid>
      <description>&lt;p&gt;One of the things I care about a lot is leadership in technology - how can we as leaders, and how can our leaders, nurture an environment which gets the best out of our people.&lt;/p&gt;

&lt;p&gt;It's easy to complain when we don't like something. It's much harder to explain what we want instead.&lt;/p&gt;

&lt;p&gt;The &lt;a href="http://agilemanifesto.org/"&gt;agile manifesto&lt;/a&gt; does an excellent job at setting out the principles we should aim for when building software - without dictating any particular style. Importantly, it sees everything as a compromise (‘&lt;em&gt;Individuals and interactions&lt;/em&gt; over &lt;em&gt;processes and tools&lt;/em&gt;') and doesn't treat either as always right or always wrong.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;While there is value in the items on the right, we value the items on the left more&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Although this has given rise to numerous methodologies, each with their own distinct interpretations, it ensures teams and organisations have the flexibility to approach agile in a way which suits their unique circumstances - and to adapt as those circumstances change.&lt;/p&gt;

&lt;h4&gt;
  
  
  I propose we do the same for technology leadership.
&lt;/h4&gt;

&lt;p&gt;And so I shamelessly rip off the agile manifesto style to get us started. And selfishly use the things I care about most. But I think this should be a collaboration - not just from leaders, but also the people we lead - so we create a manifesto which &lt;em&gt;means&lt;/em&gt; something to us all.&lt;/p&gt;

&lt;p&gt;And I think this is important. Even if we're already doing these things, others aren't.&lt;/p&gt;

&lt;h3&gt;
  
  
  Manifesto for Technology Leadership - alpha!
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Support and direction&lt;/strong&gt; over solutions and constraints&lt;br&gt;
&lt;strong&gt;Responsibility and accountability&lt;/strong&gt; over processes and rules&lt;br&gt;
&lt;strong&gt;Encouragement and honesty&lt;/strong&gt; over criticism and discipline&lt;br&gt;
&lt;strong&gt;Goals and objectives&lt;/strong&gt; over to-do lists and priorities&lt;br&gt;
&lt;strong&gt;Appreciation and respect&lt;/strong&gt; over praise and reward&lt;/p&gt;

&lt;h3&gt;
  
  
  And so...
&lt;/h3&gt;

&lt;p&gt;Whatever your job role - be it developer, tech lead, UX designer, product owner, CTO or CEO - &lt;strong&gt;I'd like your contributions, your feedback, and hopefully your willingness to sign it&lt;/strong&gt; to show your commitment to your teams. &lt;/p&gt;

</description>
      <category>manifesto</category>
      <category>agile</category>
      <category>leadership</category>
      <category>technology</category>
    </item>
  </channel>
</rss>
