<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
>

<channel>
	<title>the pm411.org project management podcast &#187; Accountability</title>
	<atom:link href="http://pm411.org/tag/accountability/feed/" rel="self" type="application/rss+xml" />
	<link>http://pm411.org</link>
	<description>project management internet radio show, templates, and webtools</description>
	<lastBuildDate>Mon, 02 Jan 2012 21:37:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
<!-- podcast_generator="Blubrry PowerPress/2.0.4" -->
	<itunes:summary>The pm411.org Project Management Podcast is dedicated to help you at your job as a Project Manager or Program Manager, regardless if you have years of experience, or if you are just starting on your journey in Project Management.  pm411.org is a place where you can come to find the latest in PM tools, PM Templates, PM tips, and PMI (PMBOK) methodologies that have been found to help others.  It is a place where discussions can be had with project managers from around the globe and in every industry where project management permeates in our Project Management discussion forums.  It is a place where you can find the best Project Management links to other sites dedicated to our wonderful profession.</itunes:summary>
	<itunes:author>Ron Holohan, MBA PMP</itunes:author>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://pm411.org/wp-content/uploads/pm411logo_itunes.jpg" />
	<itunes:owner>
		<itunes:name>Ron Holohan, MBA PMP</itunes:name>
		<itunes:email>show@pm411.org</itunes:email>
	</itunes:owner>
	<managingEditor>show@pm411.org (Ron Holohan, MBA PMP)</managingEditor>
	<copyright>2007-2012 Ron Holohan</copyright>
	<itunes:subtitle>Project management internet radio show, discussion forum, methodology, templates, and webtools</itunes:subtitle>
	<itunes:keywords>project, management, pm, prepcast, management, manager, pmi, pmp, team, management, schedule, budget</itunes:keywords>
	<image>
		<title>the pm411.org project management podcast &#187; Accountability</title>
		<url>http://pm411.org/wp-content/uploads/pm411logo_itunes.jpg</url>
		<link>http://pm411.org</link>
	</image>
	<itunes:category text="Business">
		<itunes:category text="Careers" />
		<itunes:category text="Management &amp; Marketing" />
	</itunes:category>
		<item>
		<title>What we can learn from &#8220;Undercover Boss&#8221;</title>
		<link>http://pm411.org/2010/02/09/what-we-can-learn-from-undercover-boss/</link>
		<comments>http://pm411.org/2010/02/09/what-we-can-learn-from-undercover-boss/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 04:39:23 +0000</pubDate>
		<dc:creator>Ron Holohan, MBA PMP</dc:creator>
				<category><![CDATA[Accountability]]></category>
		<category><![CDATA[Career]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[Leading]]></category>
		<category><![CDATA[Lessons Learned]]></category>
		<category><![CDATA[Meetings]]></category>
		<category><![CDATA[PM Reviews]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[cbs]]></category>
		<category><![CDATA[jobs]]></category>
		<category><![CDATA[Larry O'Donnell]]></category>
		<category><![CDATA[morale]]></category>
		<category><![CDATA[superbowl]]></category>
		<category><![CDATA[The apprentice]]></category>
		<category><![CDATA[undercover boss]]></category>
		<category><![CDATA[waste management]]></category>

		<guid isPermaLink="false">http://pm411.org/?p=941</guid>
		<description><![CDATA[Okay, so I just got around to watching the debut of the new CBS reality show, Undercover Boss, which I recorded after the Superbowl on Sunday evening. I am really not a fan of reality shows, although I did watch the first season of The Apprentice back in 2004 since it had project managers competing to secure a single lucrative position of overseeing the building of Trump International Hotel and Tower in Chicago, Illinois. After watching the first few episodes of The Apprentice, I actually felt anxious.  I think that The Donald’s continual criticizing, interrupting, and “you’re fired” climaxes of each board room episode of The Apprentice struck a little too close to reality for me.  I have never been fired, but I have been in my share of meetings and board rooms where politics are at play, people’s defenses are bristling, and at times career paths are changed.  I have found that these corporate situations often have an appearance more like a scene from William Golding’s Lord of the Flies, than that of a group of people with a common corporate goal.  And at times it has been me who has put the boar’s head on the stake! However, [...]]]></description>
		<wfw:commentRss>http://pm411.org/2010/02/09/what-we-can-learn-from-undercover-boss/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Podcast episode 052:  it&#8217;s okay to be RACI!</title>
		<link>http://pm411.org/2010/01/16/podcast-episode-052-its-okay-to-be-raci/</link>
		<comments>http://pm411.org/2010/01/16/podcast-episode-052-its-okay-to-be-raci/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 06:19:18 +0000</pubDate>
		<dc:creator>Ron Holohan, MBA PMP</dc:creator>
				<category><![CDATA[Accountability]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[PM Podcasts]]></category>
		<category><![CDATA[PM Tools]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[consulted.ram.responsibility assignment matrix]]></category>
		<category><![CDATA[raci]]></category>
		<category><![CDATA[responsibilities]]></category>
		<category><![CDATA[responsibility]]></category>
		<category><![CDATA[roles]]></category>
		<category><![CDATA[team]]></category>

		<guid isPermaLink="false">http://pm411.org/?p=870</guid>
		<description><![CDATA[If you like us, give us a 5 star review in iTunes! In Episode 004 and Episode 051 we discussed the Work Breakdown Structure and how it can help you as a team to clearly document your project’s deliverables.  But once you have completed your WBS, what’s next? Well the next step is to develop a Responsibility Assignment Matrix, or RAM, using the RACI process.  I think you are going to find this to be a valuable tool to help clarify ownership to various parts of your project.  Soon your entire team will be RACI! Define Activities Process After you identify your deliverables in your Work Breakdown Structure, you will need to define those actions and activities that need to be done to produce the lowest level deliverables.  This is the first process in the PMBOK Time Management Knowledge Area and is known as the Define Activities Process. In Episode 004 on Work Breakdown Structures we provided an example of a project of doing laundry.  A lower deliverable could be “clean dark clothes”.  Decomposing the activities under this deliverable could be “sort laundry by color,”, “select cold setting,” measure laundry detergent, add detergent to washer, add dark clothes to washer, check [...]]]></description>
		<wfw:commentRss>http://pm411.org/2010/01/16/podcast-episode-052-its-okay-to-be-raci/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		<enclosure url="http://www.pm411.org/wp-content/uploads/podcasts/pm411_052_2010-01-18.mp3" length="9827742" type="audio/mpeg" />
		<itunes:keywords>Accountability,consulted.ram.responsibility assignment matrix,raci,responsibilities,responsibility,roles,team</itunes:keywords>
		<itunes:subtitle>If you like us, give us a 5 star reviewÂ in iTunes! - In Episode 004 and Episode 051 we discussed the Work Breakdown Structure and how it can help you as a team to clearly document your projectâs deliverables.Â  But once you have completed your WBS,</itunes:subtitle>
		<itunes:summary>If you like us, give us a 5 star reviewÂ in iTunes!

In Episode 004 and Episode 051 we discussed the Work Breakdown Structure and how it can help you as a team to clearly document your projectâs deliverables.Â  But once you have completed your WBS, whatâs next?

Well the next step is to develop a Responsibility Assignment Matrix, or RAM, using the RACI process.Â  I think you are going to find this to be a valuable tool to help clarify ownership to various parts of your project.Â  Soon your entire team will be RACI!
Define Activities Process
After you identify your deliverables in your Work Breakdown Structure, you will need to define those actions and activities that need to be done to produce the lowest level deliverables.Â  This is the first process in the PMBOK Time Management Knowledge Area and is known as the Define Activities Process.

In Episode 004 on Work Breakdown Structures we provided an example of a project of doing laundry.Â  A lower deliverable could be âclean dark clothesâ.Â  Decomposing the activities under this deliverable could be âsort laundry by color,â, âselect cold setting,â measure laundry detergent, add detergent to washer, add dark clothes to washer, check clothes once the cycle completes, unload washer, add washed clothes to dryer, select regular drying setting, check clothes once dryer timer goes off, fill laundry basket, sort laundry to iron, Iron laundry, Fold laundry, and Put laundry away.

Note that the order of the activities doesnât need to necessarily be in order at this point, and additional activities can be added such as âadd dryer sheet to dryer.âÂ  However, once you have your list of activities for each deliverable, you are ready to use the RACI process to assign them to folks associated with the project.

Basically, RACI is a method to assign activities to resources by name or by function.
RACI is an acronym that stands for four types of task assignments:

	Responsible
	Accountable
	Consulted
	Informed

So, letâs talk about the four types of assignments.
Responsible [R]
The first type of assignment is âRâ that stands for âResponsible.âÂ  The person assigned as âresponsibleâ for a task is the person, or role, that is responsible for actually performing the work for the task. A few guidelines to keep in mindâ¦Â  When no one is assigned as responsible for the task, chances are that it wonât get done. Also, when many people are assigned to completing the work, it requires a lot of coordination and usually means further decomposition is required to make sure everyone is clear about what specifically they need to work on.Â  Finally, if a specific person is assigned as the âRâ to multiple tasks they may become overloaded.Â  In this case, you may want to see if someone else can fill in as the âRâ on some of the tasks.
Accountable [A]
The second type of assignment is âAâ that stands for âAccountable.âÂ  This is the person who is held accountable for the task getting completed. Â One guideline to keep in mind for the person assigned as âAccountable,â insure only one person is assigned as accountable for each task being performed. Â If you end up trying to assign multiple people to a particular task you will end up with a lot of finger pointing and confusion when issues occur.
Consulted [C]
The next type is Consulted â the âCâs.âÂ  These are the people involved and consulted prior to a task being performed. Essentially, their input is sought after and factored in prior to action taking place. As the number of people consulted increases, the speed with which action can be taken decreases. Conversely, too few and improper decisions and actions may be made without those whose buy-in is required being assigned as a âCâ.
Informed [I]
Finally are the âIâsâ who are those that need to be Informed on the status and completion of a task. If necessary parties arenât informed,</itunes:summary>
		<itunes:author>Ron Holohan, MBA PMP</itunes:author>
		<itunes:explicit>no</itunes:explicit>
	</item>
		<item>
		<title>Be accountable</title>
		<link>http://pm411.org/2008/03/25/be-accountable/</link>
		<comments>http://pm411.org/2008/03/25/be-accountable/#comments</comments>
		<pubDate>Tue, 25 Mar 2008 23:57:59 +0000</pubDate>
		<dc:creator>Ron Holohan, MBA PMP</dc:creator>
				<category><![CDATA[Accountability]]></category>
		<category><![CDATA[PM Links]]></category>
		<category><![CDATA[lap31]]></category>
		<category><![CDATA[lap31.com]]></category>
		<category><![CDATA[mistakes]]></category>
		<category><![CDATA[project management]]></category>

		<guid isPermaLink="false">http://pm411.org/2008/03/25/be-accountable/</guid>
		<description><![CDATA[Lazymale is our first guest blogger on pm411.org.  But don&#8217;t let his name fool you &#8211; he keeps busy as a Program Manager at a software services firm where he manages a team of 50 people both offshore and in the United States.  Yet he still has time to keep up his own blog at www.lap31.com!  Lazymale describes his lap31.com blog as being about &#8221;laps in this race of a lifetime&#8230; of the laps we covered and the laps that remain&#8230; of struggles, commitment and leadership&#8230; of teamwork and trust&#8230; of learning from mistakes to creating success stories and winning&#8230; Are we prepared for what&#8217;s ahead?  Are we ready to lead?&#8221;  You can reach Lazymale at lazymale@lap31.com. I&#8217;d like to think that I am a very good driver, if not an expert. Even then once in a while, I miss a red light, I over speed and sometimes even make a wrong turn. Does that mean I should quit driving altogether? I don&#8217;t think so. I need to be aware of these errors and be careful. Similarly, it is not unusual to miss a project deadline. No matter how good we plan, we may still miss a deadline somewhere; someday. Should we be afraid to [...]]]></description>
		<wfw:commentRss>http://pm411.org/2008/03/25/be-accountable/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

