<?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>Pearl Tech &#187; StaceyC</title>
	<atom:link href="http://blog.pearltechnology.com/author/staceyc/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pearltechnology.com</link>
	<description></description>
	<lastBuildDate>Fri, 17 Feb 2012 17:35:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Project Info &#8211; What&#8217;s needed and What&#8217;s not?</title>
		<link>http://blog.pearltechnology.com/project-info-whats-needed-and-whats-not/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.pearltechnology.com/project-info-whats-needed-and-whats-not/#comments</comments>
		<pubDate>Fri, 22 Apr 2011 18:20:43 +0000</pubDate>
		<dc:creator>StaceyC</dc:creator>
				<category><![CDATA[Miscellaneous]]></category>

		<guid isPermaLink="false">http://blog.pearltechnology.com/?p=1208</guid>
		<description><![CDATA[ As the saying goes, you get what you ask for, and deciding what information is important to get from the team is one of the most important and challenging things for a Project Manager.  Most of the time team members are going to give you no more information than exactly what you are asking them [...]]]></description>
			<content:encoded><![CDATA[<p> As the saying goes, you get what you ask for, and deciding what information is important to get from the team is one of the most important and challenging things for a Project Manager.  Most of the time team members are going to give you no more information than exactly what you are asking them for.  One very important factor is determining what information you really want, and then phrasing the questions so that you will actually get useful information.  For example, if you ask a team member working on a task “How is it going? How are you doing on this task?” – you will most likely get a response like this “I am about 60% done with that or I <em>should </em>be done with that by next Friday”.  What is this information actually telling you?  In my opinion, a whole lot of nothing.  When did they start the task?  What was the original duration on the task?  Are they working full time on this task and this task only?  Maybe a better way to phrase the question to the team member would be…  “When do you expect to be done with the task, on what day?”  The point here is to actually get a date from the team member that they are committing to. </p>
<p>This now leads to inputting this information into the software that you are using to manage your project.  How important is it to understand the software application that you are using to manage your projects?  Not understanding what the software does or how it works can result in giving false information and dates to Sponsors, Stakeholders, and Team Members.  Most software applications have many advanced settings that people do not even know exist.  It is extremely important to figure out how you want to track information in the schedule and set it up correctly before beginning the project.  If you are going to be tracking duration then make sure that the settings are set on fixed duration, or if you are going to be tracking effort worked of the resource then make sure that the settings are set on fixed work, etc.  Trouble will definitely start to arise if these settings are not being used appropriately since this is how the dates are calculated in the software.  This now leads to a lot of other very important questions: 1) Are the calendars in your project set up correctly with all of the holidays and time off?  2) What type of constraints will be used in the plan?  3) Do you understand how these constraints are affecting your project and critical path?  4) How will you be defining critical activities and using critical paths in the plan?  5) Are you using a baseline to be able to show variance and slippage on tasks in the plan?  6) Do you have multiple views set up to fit the needs of the different audiences that will be viewing the plan?  7)  How often will you be updating status on the plan?  <img src='http://blog.pearltechnology.com/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /> How often will you be changing the Data Date in the plan?</p>
<p>As a Project Manager you are managing time, cost, and scope/quality.  Managing any of these without an accurate schedule is very difficult and probably inaccurate.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.pearltechnology.com/project-info-whats-needed-and-whats-not/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Are you afraid of PM?</title>
		<link>http://blog.pearltechnology.com/are-you-afraid-of-pm/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.pearltechnology.com/are-you-afraid-of-pm/#comments</comments>
		<pubDate>Thu, 24 Feb 2011 17:29:55 +0000</pubDate>
		<dc:creator>StaceyC</dc:creator>
				<category><![CDATA[Miscellaneous]]></category>

		<guid isPermaLink="false">http://blog.pearltechnology.com/?p=969</guid>
		<description><![CDATA[Most people literally cringe at the thought or even the sound of the words project management.  The reason for this, in my experience, has been a sense of losing control, the fear of someone else taking over your job, and the thought of someone else holding you accountable.  Project managers are not intended to take [...]]]></description>
			<content:encoded><![CDATA[<p>Most people literally cringe at the thought or even the sound of the words project management.  The reason for this, in my experience, has been a sense of losing control, the fear of someone else taking over your job, and the thought of someone else holding you accountable.  Project managers are not intended to take over another person’s job on the team.  The main goal for the project manager is to get the entire team communicating, find out what is required to complete the project and then constantly monitoring to see if things are actually getting done.  The best project managers will want to understand what work will need to be performed to get the project done and achieve this by asking a lot of questions.  Sometimes this means sitting with a team member to understand what their job is and documenting processes to understand what the workflow is.  Most team members are also just as terrified to hear the words schedule and documentation.  Schedule means that the project manager will want to know what work needs to occur and when it’s going to get done.  Documentation means that processes and work flows will be written down to help determine tasks needed for the schedule, to see where hand-offs should occur, and to view a resource’s workload.  The documentation and schedule can all be updated as things change – none of this is written in stone!  So are there any PM’s that have had similar experiences with teams that don’t want to let you into their project world?  How did you make the team comfortable with letting you in?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.pearltechnology.com/are-you-afraid-of-pm/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

