<?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>Erudite Relics of Loc Huu Ho&#187; Loc&#8217;s Blog</title>
	<atom:link href="http://www.lochuuho.com/tag/leadership/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lochuuho.com</link>
	<description>Ancora Imparo &#34;I am still learning&#34;</description>
	<lastBuildDate>Wed, 07 Jul 2010 15:03:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>&#8220;Paradoxical Commandments&#8221; by Dr. Kent Keith</title>
		<link>http://www.lochuuho.com/2010/05/12/paradoxical-commandments-by-dr-kent-keith/</link>
		<comments>http://www.lochuuho.com/2010/05/12/paradoxical-commandments-by-dr-kent-keith/#comments</comments>
		<pubDate>Wed, 12 May 2010 13:55:17 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[Positive Attitude]]></category>
		<category><![CDATA[Kent Keith]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[paradoxical commandments]]></category>
		<category><![CDATA[silent revolution]]></category>

		<guid isPermaLink="false">http://www.lochuuho.com/?p=497</guid>
		<description><![CDATA[Silent Revolutions can give deep-feeling leaders a deeply satisfying leadership experience. You can buy glory and recognition: you can't buy meaning. Satisfaction has to come from inside. Newspaper headlines can't give it to you. The price of leading a Silent Revolution is high, but well worth paying. To pay it back with interest, try some real brotherly love. It can be the happiest thing that ever happens to you.]]></description>
		<wfw:commentRss>http://www.lochuuho.com/2010/05/12/paradoxical-commandments-by-dr-kent-keith/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don’t Be A Project Manager</title>
		<link>http://www.lochuuho.com/2009/12/04/don%e2%80%99t-be-a-project-manager/</link>
		<comments>http://www.lochuuho.com/2009/12/04/don%e2%80%99t-be-a-project-manager/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 16:56:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[IT Failure]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Project Management]]></category>

		<guid isPermaLink="false">http://www.lochuuho.com/?p=429</guid>
		<description><![CDATA[PMI would be doing business a great benefit if they would invest energy in leadership and defocusing on process for their certification. Project managers and their stakeholders need to get out of their chairs, quit entering tick marks in the spreadsheet check off lists and lead. They need to get up, turn around and look outside their cubicle at the people and the project, talk to them, listen to them, compare notes and understand why they are not coming to you with their problems. Otherwise, in Colin Powell's terms, the team will lose "confidence that you can help them or conclude that you do not care." ]]></description>
		<wfw:commentRss>http://www.lochuuho.com/2009/12/04/don%e2%80%99t-be-a-project-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Number of Reasons for Project Failure</title>
		<link>http://www.lochuuho.com/2009/12/04/the-number-of-reasons-for-project-failure/</link>
		<comments>http://www.lochuuho.com/2009/12/04/the-number-of-reasons-for-project-failure/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 16:30:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[IT Failure]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Project Management]]></category>

		<guid isPermaLink="false">http://www.lochuuho.com/?p=424</guid>
		<description><![CDATA[The other day a friend said that there were three reasons for project failure.  I took exception and stated there were two.  As I thought about it more, there is only one.  People are at the root of all failures.  Let’s look at some common reasons.

The project is over constrained.  People set the constraints. If they do not understand the project well enough to set the constraints, or listen to the people that are suggesting the constraints, then they are the problem.

It is poorly managed.  Enough said about this.  It is a people problem by definition.]]></description>
		<wfw:commentRss>http://www.lochuuho.com/2009/12/04/the-number-of-reasons-for-project-failure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Book Summary: The 17 Indisputable Laws Of Teamwork</title>
		<link>http://www.lochuuho.com/2009/05/03/book-summary-the-17-indisputable-laws-of-teamwork/</link>
		<comments>http://www.lochuuho.com/2009/05/03/book-summary-the-17-indisputable-laws-of-teamwork/#comments</comments>
		<pubDate>Sun, 03 May 2009 20:18:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[Personal]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[Coaching]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[Dedication]]></category>
		<category><![CDATA[Delegation]]></category>
		<category><![CDATA[Essentials]]></category>
		<category><![CDATA[Evaluate]]></category>
		<category><![CDATA[Ideas]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[Praise]]></category>
		<category><![CDATA[success]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://www.lochuuho.com/?p=385</guid>
		<description><![CDATA[To achieve great things, you need a team. Building a winning team
requires understanding of these principles. Whatever your goal or
project, you need to add value and invest in your team so the end
product benefits from more ideas, energy, resources, and perspectives.]]></description>
		<wfw:commentRss>http://www.lochuuho.com/2009/05/03/book-summary-the-17-indisputable-laws-of-teamwork/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Advice for new managers: part 1 (By Scott Berkun)</title>
		<link>http://www.lochuuho.com/2009/04/10/50-advice-for-new-managers-part-1-by-scott-berkun/</link>
		<comments>http://www.lochuuho.com/2009/04/10/50-advice-for-new-managers-part-1-by-scott-berkun/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 09:50:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[Coaching]]></category>
		<category><![CDATA[Delegation]]></category>
		<category><![CDATA[Ideas]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[OPPORTUNITY]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[Scott Berkun]]></category>
		<category><![CDATA[success]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Trust]]></category>
		<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://www.lochuuho.com/?p=369</guid>
		<description><![CDATA[The central mistake new managers make is egoism. On the surface, the change is all about you: you’ve been promoted, you have a new job title, you have a new office. Perhaps you’ve been waiting for this change for some time, while watching peers or friends get promotions, and now finally you feel you’ve received the respect you’ve earned. Congratulations! But be warned: how or why you became a manager has little to do with doing the job well. The sooner you recognize how different success as a manager is from success as worker, the better off you’ll be. Good managers are rare (how many have you had?): so if you’re new to the game, and would like to be a good one, this essay is for you.]]></description>
		<wfw:commentRss>http://www.lochuuho.com/2009/04/10/50-advice-for-new-managers-part-1-by-scott-berkun/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top ten reasons managers become great (From The Berkun Blog)</title>
		<link>http://www.lochuuho.com/2009/04/10/top-ten-reasons-managers-become-great-from-the-berkun-blog/</link>
		<comments>http://www.lochuuho.com/2009/04/10/top-ten-reasons-managers-become-great-from-the-berkun-blog/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 09:46:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[Personal]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Motivation]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[success]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Trust]]></category>
		<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://www.lochuuho.com/?p=365</guid>
		<description><![CDATA[As a positive counterpoint to my list of why managers become assholes, and as a counterbalance to my tendency to write cynically,  here’s a list of why people become great at managing others, trying as much as possible not to just do the stupid thing and invert my other list.
]]></description>
		<wfw:commentRss>http://www.lochuuho.com/2009/04/10/top-ten-reasons-managers-become-great-from-the-berkun-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>7 Agile Leadership Lessons for the Suits by Eugene Nizker, CIO</title>
		<link>http://www.lochuuho.com/2008/09/11/7-agile-leadership-lessons-for-the-suits-by-eugene-nizker-cio/</link>
		<comments>http://www.lochuuho.com/2008/09/11/7-agile-leadership-lessons-for-the-suits-by-eugene-nizker-cio/#comments</comments>
		<pubDate>Thu, 11 Sep 2008 05:31:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[Adapt]]></category>
		<category><![CDATA[Coaching]]></category>
		<category><![CDATA[Contracts]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Motivation]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Trust]]></category>

		<guid isPermaLink="false">http://www.lochuuho.com/?p=12</guid>
		<description><![CDATA[Most of the 400 presentations at the Agile 2008 conference, held last month in Toronto, were geared for developers and testers. But the event held more than a few revelations and "Aha!" moments for IT managers, particularly revolving around team workflow, business value, company culture and the new role of the manager. Here are the key messages communicated by and to the Agile community.]]></description>
		<wfw:commentRss>http://www.lochuuho.com/2008/09/11/7-agile-leadership-lessons-for-the-suits-by-eugene-nizker-cio/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)

Served from: www.lochuuho.com @ 2010-07-31 21:54:01 -->