<?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>13apples on Leadership &#187; PMP</title>
	<atom:link href="http://leadership.13apples.com/tag/pmp/feed/" rel="self" type="application/rss+xml" />
	<link>http://leadership.13apples.com</link>
	<description>where leaders collaborate</description>
	<lastBuildDate>Wed, 28 Dec 2011 03:56:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Managers or Companies? There is a choice.</title>
		<link>http://leadership.13apples.com/managers-or-companies/</link>
		<comments>http://leadership.13apples.com/managers-or-companies/#comments</comments>
		<pubDate>Mon, 07 Mar 2011 06:34:42 +0000</pubDate>
		<dc:creator>Raj Menon</dc:creator>
				<category><![CDATA[Leadership Mindset]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[PMP]]></category>
		<category><![CDATA[program management]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[trust]]></category>

		<guid isPermaLink="false">http://leadership.13apples.com/?p=2636</guid>
		<description><![CDATA[According to an article by Business News Daily, a 2010 survey conducted by a career-management agency called Right Management revealed that "84% of workers want to quit jobs, find new gigs in 2011". If we look beyond the obvious reasons for why that is so, we start to see the trail that leads to a much bigger issue.]]></description>
			<content:encoded><![CDATA[<style type="text/css">
#leftcontainerBox {
float:left;
position: fixed;
top: 60%;
left: 70px;
}

#leftcontainerBox .buttons {
float:left;
clear:both;
margin:4px 4px 4px 4px;

padding-bottom:2px;
}


#bottomcontainerBox {
height: 30px;
width:50%;
padding-top:1px;
}

#bottomcontainerBox .buttons {
float:left;
height: 30px;
margin:4px 4px 4px 4px;
}

</style>
<p style="text-align: justify;"><strong><span style="text-decoration: underline;">People leave Managers, not companies.</span></strong></p>
<p style="text-align: justify;">The effectiveness and success to managing people lies in the leadership skills, sense and style of the Managers. When done right, people stay motivated and bend over backwards without complain or regret. The Manager and the Team Member builds a relationship fueled by trust.</p>
<p style="text-align: justify;">According to an article by Business News Daily, a 2010 survey conducted by a career-management agency called Right Management revealed that &#8220;<a href="http://www.businessnewsdaily.com/84-percent-employees-seek-new-jobs-2011-0858/" target="_blank">84% of workers want to quit jobs, find new gigs in 2011</a>&#8220;. The article also quoted the company&#8217;s President who said that &#8220;Employees’ trust has been seriously shaken and there is a general lack of confidence in leaders.” Almost all the top reasons for why employees leave seem to point towards ineffective Managers and broken trust. If we look beyond the obvious reasons for why that is so, we start to see the trail that leads to a much bigger issue.</p>
<p style="text-align: justify;"><strong><span style="text-decoration: underline;">A Manager who is mis-managed is almost always likely to mis-manage his team.</span></strong></p>
<p style="text-align: justify;">Leadership is infectious. Good leadership has a positive impact on the team whereas bad leadership impacts negatively. Whatever the effects of leadership, it surely trickles down from the top honcho to many levels down.</p>
<p style="text-align: justify;">A friend recently told me about his Manager who had begun to show signs of maturity causing a positive change in his leadership ways. Such incidents give me hope that a transition from bad to good leadership is not an impossibility. When experience teaches us how to adopt as well as adapt to changing times and situations, it is not uncommon to see such drastic changes in leadership styles. Most leaders I know strive for that continuous improvement. However, in my friend&#8217;s situation, there was one compelling factor that could not be dismissed. The change that he noticed occurred only after a leadership change at a level above his i.e. his Manager&#8217;s Manager had changed. So if we were to believe that this is not a lone one-off incident, that mis-management is also infectious, then what next?</p>
<p style="text-align: justify;"><strong><span style="text-decoration: underline;">We have the power to choose.</span></strong></p>
<p style="text-align: justify;">Change happes when we are dissatisfied with the status quo. But choosing to change is not the only choice we have. We have the power to choose who we work for. So let&#8217;s circle back to the beginning. People leave Managers, not companies. In other words, we change Managers, not companies. And there lies the choice, a rather difficult one because unlike companies the value and worth of a Manager cannot be googled.</p>
<p style="text-align: justify;">But there is an easier choice available to us now, every minute of every day, a choice to strengthen our relationship as a Manager with our Team, and vice versa.  Let&#8217;s choose to prepare ourselves for the time when we become ready to leave a company to work for a Manager.</p>
<p style="text-align: justify;">&nbsp;</p>
<p style="text-align: justify;">&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://leadership.13apples.com/managers-or-companies/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Critical Chain Project Management</title>
		<link>http://leadership.13apples.com/ccpm-p1/</link>
		<comments>http://leadership.13apples.com/ccpm-p1/#comments</comments>
		<pubDate>Mon, 25 May 2009 20:34:15 +0000</pubDate>
		<dc:creator>Raj Menon</dc:creator>
				<category><![CDATA[Leadership Mindset]]></category>
		<category><![CDATA[PMP]]></category>
		<category><![CDATA[productivity]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[success]]></category>

		<guid isPermaLink="false">http://lap31.com/flyer/?p=894</guid>
		<description><![CDATA[...an effective scheduling technique that enables project managers to truly plan a project instead of merely stringing tasks together to an end date. True planning calls fot a great deal of thought that should go into executing a project and steer it towards success. But to do that, we need to first understand project failure.]]></description>
			<content:encoded><![CDATA[<style type="text/css">
#leftcontainerBox {
float:left;
position: fixed;
top: 60%;
left: 70px;
}

#leftcontainerBox .buttons {
float:left;
clear:both;
margin:4px 4px 4px 4px;

padding-bottom:2px;
}


#bottomcontainerBox {
height: 30px;
width:50%;
padding-top:1px;
}

#bottomcontainerBox .buttons {
float:left;
height: 30px;
margin:4px 4px 4px 4px;
}

</style>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">CCPM. Have you heard about this project management framework? What about the concept of critical path? If you have ever been exposed to project schedules, the latter would probably ring a bell. Critical path is the shortest distance to project acceptance and completion. If the project has 10 tasks to deliver, and 8 of them are critical for acceptance, the critical path will comprise of those 8 tasks. Makes sense?</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">CCPM is a framework build around the critical path concept. To me it is an effective scheduling technique that enables project managers to truly plan a project instead of merely stringing tasks together to an end date. True planning calls fot a great deal of thought that should go into executing a project and steer it towards success. But to do that, we need to first understand project failure.</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">Why do projects fail? According to Allan Elder&#8217;s whitepaper (link below), most projects fail to meet deadlines on time, on budget, and on scope (OTOBOS) due to the following 5 reasons or diseases of project management:</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">(a) We are victims of &#8220;<strong>Bad Multi-Tasking</strong>&#8220;. In short, we have too many tasks on our plate mainly due to a lack of planning from the task assignor/delegator &#8211; your Manager or &#8216;You, Inc.&#8217; &#8211; thus leading to bad task prioritization to procrastination to burnout.</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">(b) Parkinson&#8217;s Law i.e. <strong>Work expands so as to fill the time available for completion</strong>. The safety we&#8217;ve built into our estimates with an intent to avoid the worst case scenario somehow transforms into being our best case scenario. And we are not incentivized to do otherwise.</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">(c) The &#8216;<strong>Student Syndrome&#8217; </strong>is in us and we cannot escape it. So, lets accept the fact that due to the above 2 reasons we are not going to work on that task until the 11th hour &#8211; the time we need just enough to complete the task and meet the deadline. We dont know how we do it but we do.</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">(d) <strong>Task Dependency</strong> for the wrong reasons. Project completion is dependent on all its tasks being completed on time (task completion date) and on budget (resource availability) but when tasks are integrated, projects get penalized due to time wastage and resources being under-committed.</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">(e) Task Completion <strong>!=</strong> Task Delivery. We tend ignore those sneaky little unplanned and unforeseen events that cause <strong>delays in the delivery of completed tasks</strong>. Project progress is measured based on the tasks completed and not task hand-offs.</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">CCPM is based on the &#8216;Theory Of Constraints&#8217; methodologies and is said to have proven a high rate of project success when implemented right. I have not tried it out yet but am in the process on learning how to. Walk with me on this critical path to success and we&#8217;ll find out how to keep our projects OTOBOS.</p>
<p style="line-height: 14.25pt; font-size: 10pt; color: #000000; font-family: 'Lucida Sans Unicode', sans-serif; text-align: left;">In my follow-up to this post, I will dive more into how CCPM works. Meanwhile, please do read &#8220;<a title="Allan Elder's &quot;The Five Diseases of Project Management&quot;" href="http://www.nolimitsleadership.com/images/The%20Five%20Diseases%20of%20Project%20Management.pdf" target="_blank">The Five Diseases of Project Mangement</a>&#8221; (PDF) to understand the above reasons in detail. This whitepaper is a keeper.</p>
]]></content:encoded>
			<wfw:commentRss>http://leadership.13apples.com/ccpm-p1/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>6 Steps to Successful Schedules</title>
		<link>http://leadership.13apples.com/6-steps-to-successful-schedules/</link>
		<comments>http://leadership.13apples.com/6-steps-to-successful-schedules/#comments</comments>
		<pubDate>Wed, 02 Apr 2008 05:00:13 +0000</pubDate>
		<dc:creator>Raj Menon</dc:creator>
				<category><![CDATA[Words of Wisdom]]></category>
		<category><![CDATA[PMP]]></category>
		<category><![CDATA[program management]]></category>
		<category><![CDATA[project management]]></category>

		<guid isPermaLink="false">http://lap31.com/flyer/?p=63</guid>
		<description><![CDATA[Creating a comprehensive schedule is one of the more difficult activities that Project Managers face. Schedule creation is often considered more art than science - and results often support this. What is often more frustrating is that team members often find themselves on one team with a project manager that creates and manages schedules a particular way and then on another team with a project manager with a different approach.]]></description>
			<content:encoded><![CDATA[<style type="text/css">
#leftcontainerBox {
float:left;
position: fixed;
top: 60%;
left: 70px;
}

#leftcontainerBox .buttons {
float:left;
clear:both;
margin:4px 4px 4px 4px;

padding-bottom:2px;
}


#bottomcontainerBox {
height: 30px;
width:50%;
padding-top:1px;
}

#bottomcontainerBox .buttons {
float:left;
height: 30px;
margin:4px 4px 4px 4px;
}

</style>
<div class="entry-body">
<div>
<div class="item-body">
<div>
<p><em>It is my honor to introduce <strong>Ron Holohan</strong> as lap31&#8242;s first guest blogger. Ron is the founder of <a href="http://www.pm411.org/" target="_blank">pm411.org</a>, a site which is dedicated to help Project Managers find the latest in tools, tips, and methodologies. Ron has 14 years of experience in this field, PMP certified and is now a Director of Program Management for a major company in the Chicago. You can reach Ron at <a href="mailto:show@pm411.org" target="_blank">show@pm411.org</a>.</em></p>
<hr />Creating a comprehensive schedule is one of the more difficult activities that Project Managers face. Schedule creation is often considered more art than science &#8211; and results often support this. What is often more frustrating is that team members often find themselves on one team with a project manager that creates and manages schedules a particular way and then on another team with a project manager with a different approach.</div>
<p>I often hear from people on teams, “why can’t all project managers do things the same way?”</p>
<p>If you have heard this on your team, perhaps it is time that you take a look at the way you and your team create your team schedules. Perhaps you are not taking the consistent steps in developing team schedules that have been shown to work time and time again.</p>
<p>There are lots of resources out there that claim the perfect answer to your scheduling problems. But, I believe that you can improve your chances for success just by following six simple steps.</p>
<p><strong>Step 1: Define the schedule activities</strong></p>
<p>Take your WBS work packages and decompose them further into schedule activities. If you haven’t created a WBS yet for your project, you will want to listen to the pm411.org podcast <a href="http://pm411.org/2007/05/06/podcast-episode-004-work-breakdown-structures/" target="_blank">Episode 4 on Work Breakdown Structures</a>.</p>
<p>Take each WBS work package, and decide what activities are required to create that package. For example, if your work package is “Configure New Computer Hardware,” your schedule activities might include “set up network configuration,” “install the video card,” “install applications,” and then “set up mail client.”</p>
<p><strong>Step 2: Sequence the activities</strong></p>
<p>Remember back in grade school where you were given a bunch of pictures and you had to figure out their order. You had to decide which picture represented the 1st activity, the 2nd activity and so on? Well, that is exactly what the second step is all about. In step two we sequence the schedule activities by simply placing them in the order in which they need to happen. For example, perhaps we need to install the video card first, then set up the network configuration, install application and then finally set up the mail client. In some cases two or more activities can be done simultaneously. Perhaps we can set up the mail client while other applications are being installed. This step is where we look at the different types of schedule dependencies such as finish-to-start, start-to-start, finish-to-finish, and start-to-finish to figure out how each of these activities relate to each other.<br />
&lt;!&#8211;break&#8211;&gt;<br />
<strong>Step 3: Estimate the resources needed for the activity</strong></p>
<p>The third step involves estimating what resources will be required to accomplish each activity. This includes estimating needed team resources, financial resources, and equipment. These resource needs should be selected for each activity prior to estimating the duration of each activity which is the next step.</p>
<p><strong>Step 4: Estimating the duration of each of the activities</strong></p>
<p>This step requires you and your team to analyze how long it will take to accomplish each of the activities. These estimates can be quantified through the following tools:</p>
<ul>
<li>Expert Judgement &#8211; by conferring with someone who is familiar or experienced in what it takes to accomplish a particular activity.</li>
<li>Analogous Estimating &#8211; a top-down estimation approach is taken by looking at similar projects within your organization for estimates on how long a particular activity should take.</li>
<li>Parametric Estimating – Basically this is scaling an estimate. For example, perhaps you know it takes on average 10 minutes to install a software application. If the “install applications” activity includes the installation of 6 applications, you can use parametric estimation to estimate that it will take approximately 6 times 10 minutes, or 60 minutes to install all the applications.</li>
<li>Three point estimation &#8211; Sometimes referred to as PERT analysis, is a great tool for estimating activity durations. We posted about 3 point estimating back in <a href="http://pm411.org/2007/03/11/27/" target="_blank">March of 2007</a>. You basically take a weighted average of a pessimistic, expected, and optimistic estimate for the activity duration. This estimate is in the form of, (Pessimistic + 4x(Expected) + Optimistic) / 6</li>
</ul>
<p><strong>Step 5: Schedule Development</strong></p>
<p>This step is the process where the sequence of activities, resources needed for the activities, and the duration of each activity is used to optimize the overall project schedule. Tools used in this process include <a href="http://en.wikipedia.org/wiki/Critical_path_method" target="_blank">Critical Path Method</a>, schedule compression, what-if scenario analysis, <a href="http://en.wikipedia.org/wiki/Resource_Leveling" target="_blank">resource leveling</a>, and <a href="http://pm411.org/2007/08/05/podcast-episode-011-critical-chain-project-management/" target="_blank">critical chain</a> methods. Each of these topics could have one or more episodes dedicated to it, so we will not go into detail of each.</p>
<p>Once the schedule is developed, it should be baselined to provide a snapshot of the original schedule plan of the plan.</p>
<p><strong>Step 6: Monitoring and controlling the schedule</strong></p>
<p>The final step is monitoring and controlling the schedule. This step is performed throughout the life of the project and ensures that the work results lines up with the schedule plan. Schedule control requires the use of progress reporting, schedule change control systems, such as the use of Project Change Requests, performance management, and variance analysis to determine if additional action is required to get the schedule back in line with the plan.</p>
<p>So, there you have it &#8211; 6 steps you need to know to create a successful project schedule!</p></div>
</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://leadership.13apples.com/6-steps-to-successful-schedules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Think SMARTer!</title>
		<link>http://leadership.13apples.com/think-smarter/</link>
		<comments>http://leadership.13apples.com/think-smarter/#comments</comments>
		<pubDate>Sun, 03 Feb 2008 05:00:55 +0000</pubDate>
		<dc:creator>Raj Menon</dc:creator>
				<category><![CDATA[Leadership Mindset]]></category>
		<category><![CDATA[PMP]]></category>
		<category><![CDATA[success]]></category>

		<guid isPermaLink="false">http://lap31.com/flyer/?p=81</guid>
		<description><![CDATA[<style type="text/css">
#leftcontainerBox {
float:left;
position: fixed;
top: 60%;
left: 70px;
}

#leftcontainerBox .buttons {
float:left;
clear:both;
margin:4px 4px 4px 4px;

padding-bottom:2px;
}


#bottomcontainerBox {
height: 30px;
width:50%;
padding-top:1px;
}

#bottomcontainerBox .buttons {
float:left;
height: 30px;
margin:4px 4px 4px 4px;
}

</style>
It’s the 1st quarter of the New Year and time for us to set our goals for 2008. For most of us its just another one of those documents we need to fill up. We do it because we are asked to; because everyone else is doing it. It’s not that we don’t see the &#8230;]]></description>
			<content:encoded><![CDATA[<style type="text/css">
#leftcontainerBox {
float:left;
position: fixed;
top: 60%;
left: 70px;
}

#leftcontainerBox .buttons {
float:left;
clear:both;
margin:4px 4px 4px 4px;

padding-bottom:2px;
}


#bottomcontainerBox {
height: 30px;
width:50%;
padding-top:1px;
}

#bottomcontainerBox .buttons {
float:left;
height: 30px;
margin:4px 4px 4px 4px;
}

</style>
<p>It’s the 1st quarter of the New Year and time for us to set our goals for 2008. For most of us its just another one of those documents we need to fill up. We do it because we are asked to; because everyone else is doing it. It’s not that we don’t see the value in it. We don’t care enough about it. I hated goal setting too. I hated it because it made me think about my wishes and wants that I haven’t yet fulfilled, those that I fear to pursue. As we climb that ladder of growth in our organization, setting goals become an integral part of our everyday professional life with a direct impact on our personal life. In others words, our lives have to become goal-oriented. We cannot afford to not care. We must care enough to set Specific, Measurable, Accountable, Result-oriented and Time-based goals – SMART goals.</p>
<p>One of my goals for 2008 is to become PMP certified. It is a SMART goal because I know &#8220;specifically&#8221; what I want to do. I want to enroll, learn and get certified. I will take mock tests that will help me &#8220;measure&#8221; my progress towards my final test, which will measure my success. The fact that I am setting it as my annual goal, sharing it with my family and with you, shows &#8220;accountability&#8221;. It is &#8220;result-oriented&#8221; not because I will be certified, but because the certification will help me be better at what I do &#8211; project management. It is &#8220;time-based&#8221; because it has a deadline &#8211; August &#8217;08.</p>
<p>I&#8217;ve always believed that if I wish for something and want it badly enough, then someday that wish will come true. We don’t always get what we wished for simply because our &#8216;wishes&#8217; don’t turn into &#8216;wants&#8217;. The first step is to convert those wishes into wants because when we really want something, we set our mind to it and when our mind is focused on something, we are thinking goals. So don’t delay. Set some goals. Remember, it’s a simple as making a wish.</p>
]]></content:encoded>
			<wfw:commentRss>http://leadership.13apples.com/think-smarter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

