<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Chad Sturtz &#187; People</title>
	<atom:link href="http://chadsturtz.com/category/people/feed/" rel="self" type="application/rss+xml" />
	<link>http://chadsturtz.com</link>
	<description>A Journey Through Software</description>
	<lastBuildDate>Fri, 02 Jul 2010 20:48:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why I need Yammer</title>
		<link>http://chadsturtz.com/2010/07/why-i-need-yammer/</link>
		<comments>http://chadsturtz.com/2010/07/why-i-need-yammer/#comments</comments>
		<pubDate>Fri, 02 Jul 2010 20:48:44 +0000</pubDate>
		<dc:creator>Chad</dc:creator>
				<category><![CDATA[People]]></category>
		<category><![CDATA[teamwork]]></category>

		<guid isPermaLink="false">http://chadsturtz.com/?p=122</guid>
		<description><![CDATA[Q: Why do I need Yammer?
A:  It&#8217;s simple&#8230; I want access to my fellow software engineers and technologists that live on the other side of boundaries that get created around other Departments, Products, Business Units, and Acquisitions.
True story. I had to quickly come up to speed on a technology I had not been introduced to previously. [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fchadsturtz.com%2F2010%2F07%2Fwhy-i-need-yammer%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fchadsturtz.com%2F2010%2F07%2Fwhy-i-need-yammer%2F" height="61" width="51" /></a></div><p><strong>Q</strong>: Why do I need Yammer?</p>
<p><strong>A</strong>:  It&#8217;s simple&#8230;<strong> </strong>I want access to my fellow software engineers and technologists that live on the other side of boundaries that get created around other Departments, Products, Business Units, and Acquisitions.</p>
<p>True story. I had to quickly come up to speed on a technology I had not been introduced to previously.  I took the normal approach of aggressively searching online to find examples, white papers, blogs, anything to help.  Time was running out, and while I had learned a lot in a short amount of time, I wanted a little help connecting all of the dots and selecting what I needed to focus on to complete my task in a timely manner.  I needed 15 minutes with an expert in this technology to guide me down the right path, because I didn&#8217;t have time to go down the wrong one.</p>
<p>I jumped on Yammer and put out a call for help.  A development manager responded with the name of a person who he knew to be experienced with this technology.  He introduced us over email and a few minutes later, I was getting exactly what I needed.</p>
]]></content:encoded>
			<wfw:commentRss>http://chadsturtz.com/2010/07/why-i-need-yammer/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Why you&#8217;re not ready for Agile: The real top 10 list</title>
		<link>http://chadsturtz.com/2010/07/why-youre-not-ready-for-agile-the-real-top-10/</link>
		<comments>http://chadsturtz.com/2010/07/why-youre-not-ready-for-agile-the-real-top-10/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 19:25:38 +0000</pubDate>
		<dc:creator>Chad</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[People]]></category>

		<guid isPermaLink="false">http://chadsturtz.com/?p=115</guid>
		<description><![CDATA[The real 10 reasons your organization isn't ready for Agile.]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fchadsturtz.com%2F2010%2F07%2Fwhy-youre-not-ready-for-agile-the-real-top-10%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fchadsturtz.com%2F2010%2F07%2Fwhy-youre-not-ready-for-agile-the-real-top-10%2F" height="61" width="51" /></a></div><p>We&#8217;ve all seen too many blogs and articles along the lines of &#8220;10 reasons you&#8217;re organization isn&#8217;t ready for Agile&#8221;.  I believe that buried under all of those &#8216;reasons&#8217; are fundamental problems that will keep your organization from reaching any high level of productivity.  Here it is, the real top 10 list:</p>
<p>1. you&#8217;re not hiring the right people</p>
<p>2. you&#8217;re not hiring the right people</p>
<p>3. you&#8217;re not hiring the right people</p>
<p>4. you&#8217;re not hiring the right people</p>
<p>5. you&#8217;re not hiring the right people</p>
<p>6. you&#8217;re not hiring the right people</p>
<p>7. you&#8217;re not hiring the right people</p>
<p>8. you&#8217;re not hiring the right people</p>
<p>9. you&#8217;re not hiring the right people</p>
<p>10. you&#8217;re not hiring the right people</p>
<p>Hopefully this comprehensive list will help you and your organization.  Cheers.</p>
]]></content:encoded>
			<wfw:commentRss>http://chadsturtz.com/2010/07/why-youre-not-ready-for-agile-the-real-top-10/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Problem Solvers</title>
		<link>http://chadsturtz.com/2009/11/problem-solvers/</link>
		<comments>http://chadsturtz.com/2009/11/problem-solvers/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 20:47:19 +0000</pubDate>
		<dc:creator>Chad</dc:creator>
				<category><![CDATA[People]]></category>

		<guid isPermaLink="false">http://chadsturtz.com/?p=8</guid>
		<description><![CDATA[Over the past 5 years, I&#8217;ve had the opportunity to work with many people who were very knowledgeable in many different areas.  However, one thing I&#8217;ve come to realize all too often is that when it comes to solving difficult problems, knowledge is, at most, half the battle.  Time and time again I have seen people [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fchadsturtz.com%2F2009%2F11%2Fproblem-solvers%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fchadsturtz.com%2F2009%2F11%2Fproblem-solvers%2F" height="61" width="51" /></a></div><p>Over the past 5 years, I&#8217;ve had the opportunity to work with many people who were very knowledgeable in many different areas.  However, one thing I&#8217;ve come to realize all too often is that when it comes to solving difficult problems, knowledge is, at most, half the battle.  Time and time again I have seen people struggle at solving a problem they did not immediately know the answer to.  Without a suite of problem solving skills, the value of their knowledge of the problem domain quickly diminishes.  These are the times when the Problem Solvers step in and get the job done.</p>
<p>So, who are the real problem solvers?</p>
<p><strong>Visionaries &#8211; </strong>The greatest Problem Solvers can very quickly identify a clear path to success.  From this vision they are able to generate a plan of attack that will strategically expose the root problem and find the correct solution(s).</p>
<p><strong>Leaders &#8211; </strong>As a leader, the Problem Solver is able to coordinate the effort.  They break the the plan of attack down into individual tasks that can be executed in parallel by the resources at hand.</p>
<p><strong>Enablers &#8211; </strong>Possibly the most important skill a Problem Solver has is the ability to remove roadblocks or find alternative paths.  The key to solving a problem quickly is to never stop.  The Problem Solver recognizes this and focuses on getting himself/herself and others whatever it is they need to identify and fix the issue.</p>
<p><strong>Communicators &#8211; </strong>Solving problems requires that the right people have the right information.  The Problem Solver is able to recognize important data and ensure that the information is shared.  Furthermore, they identify all available communication channels and use them effectively.</p>
<p><strong>Adaptive -</strong> The Problem Solver knows that any new discovery can change everything.  At a moment&#8217;s notice, they are able to shift resources, open new communication channels, and devise an entirely new plan of attack.</p>
]]></content:encoded>
			<wfw:commentRss>http://chadsturtz.com/2009/11/problem-solvers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
