<?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>Journeyman Project Manager &#187; Project Management</title>
	<atom:link href="http://heymans.org/category/project-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://heymans.org</link>
	<description>Hi, I'm Bert Heymans and I'm a journeyman project manager.</description>
	<lastBuildDate>Thu, 10 Jun 2010 07:18:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Sound advice from Wim Lockefeer</title>
		<link>http://heymans.org/2009/09/sound-advice-from-wim-lockefeer/</link>
		<comments>http://heymans.org/2009/09/sound-advice-from-wim-lockefeer/#comments</comments>
		<pubDate>Mon, 14 Sep 2009 20:29:57 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Interviews]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[interview advice commitment duty responsibility ethics]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=373</guid>
		<description><![CDATA[I interviewed Wim Lockefeer, a senior project manager at Nascom. Wim has over 15 years of experience in project management and he&#8217;s fun to have on the team so I wanted to pick his brain. As usual this post is a summary of what I learned from the interview and my own interpretation. Here&#8217;s my [...]]]></description>
			<content:encoded><![CDATA[<p>I interviewed <a href="http://www.google.com/search?client=safari&amp;rls=en&amp;q=wim+lockefeer&amp;ie=UTF-8&amp;oe=UTF-8">Wim Lockefeer</a>, a senior project manager at <a href="http://nascom.be">Nascom</a>. Wim has over 15 years of experience in project management and he&#8217;s fun to have on the team so I wanted to pick his brain. </p>
<div id="attachment_374" class="wp-caption aligncenter" style="width: 510px"><a href="http://www.flickr.com/photos/heymans/3515141889/"><img src="http://heymans.org/wp-content/uploads/2009/09/3515141889_b50833b620.jpg" alt="Wim Lockefeer" title="Wim Lockefeer" width="500" height="333" class="size-full wp-image-374" /></a><p class="wp-caption-text">Wim Lockefeer</p></div>
<p>As usual this post is a summary of what I learned from the interview and my own interpretation. Here&#8217;s my last question to start with, answered with a fairly epic quote in my opinion:</p>
<p><strong>What does a good project manager do?</strong></p>
<blockquote>
<p>A good project manager makes sure the promises that other people make come true.</p>
</blockquote>
<p><strong>How can a project manager have the biggest impact on a company&#8217;s baseline?</strong></p>
<p>You can look at this from several perspectives, a project manager has a role facing clients and a role in the middle management layer of a company.</p>
<p>Anyhow a PM is responsible for the profitability of a company and is morally bound to wear both hats.</p>
<p>Facing the client a project manager helps to realise quality pitches and has a kind of sales evangelist role.</p>
<p>As a middle manager a project manager is in a position where he has to maintain contact with more people in the company than any other function. That position gives a project manager the best information to work on company efficiency, there&#8217;s a lot of impact there as well.</p>
<p>Project managers aren&#8217;t line managers, they should think in more than one dimension.</p>
<p><strong>How do you keep a clear overview of things?</strong></p>
<p>For yourself, probably the best thing that works is keeping a daily list of things to do and writing them down in such a way that they are feasible.</p>
<p>In the wider project context, good overview comes with:</p>
<ul>
<li>creating a fairly detailed <a href="http://heymans.org/2009/02/3-tools-to-make-work-breakdown-structure/">WBS</a></li>
<li>keeping clear <strong>expectancies</strong> from clients and the people working on the project</li>
<li>making sure people <strong>report accurately</strong></li>
<li>pointing people to their <strong>duties</strong></li>
<li>creating situations that are <strong>self-motivating</strong> for people</li>
<li>being <strong>honest</strong></li>
</ul>
<p>Having someone responsible for a skill group &#8211; a team leader &#8211; puts him in a good position for keeping quality and good time reporting in check. A project manager isn&#8217;t supposed to come across as a controller, he should dispense the correct responsibilities. Overview is a result, it comes with the deal.</p>
<p><strong>What is quality management?</strong></p>
<p>It&#8217;s what a good producer is for a movie. A managers creates premises just like the producer does. He makes sure the conditions are met for people to put their skills to work.</p>
<p>Hence the classic expression <strong>1+1=3</strong>.</p>
<p>You have to be hard on yourself as a manager to make this synergy happen, no matter how much experience you have.</p>
<p><strong>What do you do to get a higher quality management?</strong></p>
<p>Having more emphasis on overview and a bit less on insight. Find the perspective that allows you to work proactively. </p>
<p>Take a step back and let people come to you so they can explain what they need to get their jobs done. Experienced people like working like this, they know what they need to get their job done and come to you for those things.</p>
<p>It&#8217;s a bit like Lego, if you look at the Lego boxes from the old days they where full of pieces and you just had to make stuff. Today boxes are smaller and have a detailed manual. </p>
<p>Some people need manuals, some won&#8217;t, but work that&#8217;s boxed correctly  results in better quality and gets good results faster.</p>
<p><strong>How do you know that what you are doing works?</strong></p>
<p>It&#8217;s a continuous process.</p>
<p>Having a good running company comes down to making sure people are doing what they are supposed to do during their working hours. The hours in a day are limited and can only be spent once, time spent is irreplaceable.</p>
<p><strong>Conclusion</strong></p>
<p>Something that keeps coming back in Wim&#8217;s answers is proper commitment from people and conveying a correct sense of duties. It reminds me of the <a href="http://heymans.org/2009/03/the-one-minute-manager/">One Minute Manager</a> book. For you as a manager it all comes down to creating the environments for others to apply their skills in the most efficient way. Again, just like we noticed in the <a href="http://heymans.org/2009/09/what-i-learned-from-jan-de-schepper/">interview with Jan De Schepper</a> you need good soft-skills to make it happen.</p>
<p><a href="http://twitter.com/Sparehed">Follow Wim on Twitter</a> and check out his neat blog on the fine art of comics <a href="http://www.sparehed.com/">The Ephemerist</a>. He&#8217;s also a respected writer for the Flemish comic magazine <a href="http://www.stripturnhout.be">Stripgids</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/09/sound-advice-from-wim-lockefeer/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What I learned from Jan De Schepper</title>
		<link>http://heymans.org/2009/09/what-i-learned-from-jan-de-schepper/</link>
		<comments>http://heymans.org/2009/09/what-i-learned-from-jan-de-schepper/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 19:27:28 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Interviews]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Project Management]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=365</guid>
		<description><![CDATA[A (long) while ago I had a talk about project management with Jan De Schepper. He is the former Telindus Chief executive and Executive Chairman of the Board of Directors at Nascom and runs the Business Solutions Unit. We get to see a lot more of him on the floor at Nascom HQ these days [...]]]></description>
			<content:encoded><![CDATA[<p>A (long) while ago I had a talk about project management with <a href="http://www.google.com/search?client=safari&amp;rls=en&amp;q=jan++de+schepper&amp;ie=UTF-8&amp;oe=UTF-8">Jan De Schepper</a>. He is the former <a href="http://www.telindus.com/">Telindus</a> Chief executive and Executive Chairman of the Board of Directors at <a href="http://nascom.be">Nascom</a> and runs the Business Solutions Unit. We get to see a lot more of him on the floor at <a href="http://nascom.be">Nascom</a> HQ these days and I figured that would be the perfect opportunity to learn from someone with loads of experience and ask him a few questions. </p>
<div id="attachment_366" class="wp-caption aligncenter" style="width: 510px"><img src="http://heymans.org/wp-content/uploads/2009/09/jan.jpg" alt="Jan De Schepper" title="jan" width="500" height="333" class="size-full wp-image-366" /><p class="wp-caption-text">Jan De Schepper</p></div>
<p>This wasn&#8217;t a classic kind of interview. No tape-recorder, just pen, paper and a talk. And these are the lessons I learned.</p>
<p><strong>Have you ever had the project manager job title?</strong></p>
<p>No, but I&#8217;ve always worked in project mode. Starting <a href="http://www.telindus.com/">Telindus</a> for instance was a project.</p>
<p><strong>You are and have been responsible for so many people and so many things, how do you monitor and control so much stuff?</strong></p>
<p>Good memory, and the the capacity to anticipate. What I do can be summed up in 5 points of control:</p>
<ol>
<li>feedback control, asking the right questions and doing it a lot</li>
<li>building memory and anticipating</li>
<li>looking at the results</li>
<li>looking at how the results came to be</li>
<li>working with people, having a good working culture</li>
</ol>
<p><strong>How do you know what works?</strong></p>
<p>By looking rationally and instinctively at things. Rationally by looking at the numbers, instinctively by building on previous experiences. </p>
<blockquote>
<p>There&#8217;s a difference between looking and seeing, hearing and listening, touching and feeling, &#8230; that&#8217;s instinct.</p>
<p>Experience is what you get after you needed it.</p>
</blockquote>
<p>My experiences for instance tell me about todays crisis, you have to show what works to companies and how a service will provide that ROI they need today. You have to reassure this, be credible, agile and provide quality at a good price.</p>
<p><strong>Facing a client, which role is the most efficient for a project manager?</strong></p>
<p>A good manager is what I like to call a <em>3D manager</em>. The formost important thing you need to do is communicate. That is listening to what is going on as well as the interpretation of the things you hear. A PM has to do this facing all directions.</p>
<ol>
<li>A project manager should translate what is told before making an action plan.</li>
<li>Think in parallel, be multidisciplinary.</li>
<li>You have to be an excellent time manager, for yourself and for others.</li>
<li>And you have to be able to use the tools, like PMI, Prince2, etc. whatever methodology you need.</li>
<li>A <em>3D manager</em> is a good leader.</li>
<li>There has to be integrity in all you do.</li>
</ol>
<p><strong>How can you be a good leader?</strong></p>
<p>Well, quality of the people we work with is very important. When there is good talent, a good leader can stimulate talent and keep it. 40% of the talent that is in most people is latent, a coach can help people discover and make use of it. People have to be able to learn form a leader.</p>
<p><strong>Thanks for the advice Jan!</strong></p>
<p><strong>Conclusion</strong></p>
<p>What we notice from the interview with Jan is that there&#8217;s a constant emphasis on soft skills (listening, talking, interpreting, building knowledge, leadership, etc.). For us PMs the methodology is a basis, you&#8217;ll only start to make a real difference by working on soft skills and emotional intelligence.</p>
<p>This is a conclusion my Program Manager Taki Tsaklanos came up with when he proofread this post, and I couldn&#8217;t agree more. I guess I&#8217;ll interview him sometime soon <img src='http://heymans.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Next up is someone else though, so keep a look out, a new interview will be online soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/09/what-i-learned-from-jan-de-schepper/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t Compromise on the Good Part</title>
		<link>http://heymans.org/2009/05/dont-compromise-on-the-good-part/</link>
		<comments>http://heymans.org/2009/05/dont-compromise-on-the-good-part/#comments</comments>
		<pubDate>Sat, 09 May 2009 19:46:07 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Inspiration]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[quote]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=348</guid>
		<description><![CDATA[There are 3 parameters everybody wants in any project. The project has to be: Cheap Fast Good The golden rule is you can only have 2. A fast &#038; cheap project is rarely gonna be good. A fast &#038; good project isn’t cheap. And a cheap good project won’t be fast. So please choose whether [...]]]></description>
			<content:encoded><![CDATA[<p>There are <strong>3 parameters everybody wants</strong> in any project.<br />
The project has to be:
<ul>
<li>Cheap</li>
<li>Fast</li>
<li>Good</li>
</ul>
<p>The golden rule is <strong>you can only have 2</strong>.</p>
<ul>
<li>A fast &#038; cheap project is rarely gonna be good.</li>
<li>A fast &#038; good project isn’t cheap.</li>
<li>And a cheap good project won’t be fast.</li>
</ul>
<p>So please choose whether you want it cheap, or fast.<br />
<strong>Don’t compromise on the good part.</strong></p>
<p>a <a href="http://hossgifford.com/">Hoss Gifford</a> quote &#8211; via <a href="http://blog.soulcreation.com/">Claudio Capodifoglia</a></p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/05/dont-compromise-on-the-good-part/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Creative Industry Project Management</title>
		<link>http://heymans.org/2009/05/creative-industry-project-management/</link>
		<comments>http://heymans.org/2009/05/creative-industry-project-management/#comments</comments>
		<pubDate>Fri, 01 May 2009 21:51:25 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[change management]]></category>
		<category><![CDATA[creative industry]]></category>
		<category><![CDATA[creativity]]></category>
		<category><![CDATA[quality assurance]]></category>
		<category><![CDATA[risk management]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=343</guid>
		<description><![CDATA[Creativity in art and advertising requires a certain amount of chaos, after all creating ideas is an organic process. These are some actions I noticed that can make the difference under such conditions. Keeping a good risk log, thinking up correct mitigations. Having a stakeholder list and a communication plan. Practicing disciplined asset management. Putting [...]]]></description>
			<content:encoded><![CDATA[<p>Creativity in art and advertising requires a certain amount of chaos, after all creating ideas is an organic process. </p>
<p>These are some actions I noticed that can make the difference under such conditions.</p>
<ul>
<li>Keeping a good risk log, thinking up correct mitigations.</li>
<li>Having a stakeholder list and a communication plan.</li>
<li>Practicing disciplined asset management.</li>
<li>Putting exceptional effort in illustrating the technical and time-based constraints, so everyone has the correct expectations.</li>
<li>Practicing active quality assurance, involving creative direction from start to finish.</li>
<li>Having people challenge each other with great mutual thrust.</li>
<li>Creating opportunities for people with all kinds of skills to communicate naturally. (the <a href="http://www.duvalguillaume.com/news/about">brand team</a> philosophy)</li>
</ul>
<p>The advertising industry is creativity driven. The message of a campaign needs to get across in all it&#8217;s aspects.</p>
<p>I look at it as very harsh quality assurance. Sometimes that means making an unplanned iteration, or starting over in the middle of a project.</p>
<p>And <strong>that unpredictability factor is where I think the greatest challenge lies</strong>, to be able to still deliver within budget and on time. This is hard and requires good strategy and business insight.</p>
<p><a href="http://www.flickr.com/photos/heymans/3455301538/" title="What the office looks like by Bert Heymans, on Flickr"><img src="http://farm4.static.flickr.com/3379/3455301538_0c5188474c.jpg" width="333" height="500" alt="What the office looks like" /></a></p>
<p>Last month I started to work as a project manager for <a href="http://www.duvalguillaume.com/">Duval Guillaume</a>, a big advertising agency based in Belgium. The core business of <a href="http://www.duvalguillaume.com/">Duval Guillaume</a> is creating strong brands using an idea-centric approach. </p>
<p>Just so you know, my professional headquarters remains at <a href="http://www.nascom.be">Nascom</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/05/creative-industry-project-management/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Key Method to Prioritizing Efficiently</title>
		<link>http://heymans.org/2009/03/key-method-to-prioritizing-efficiently/</link>
		<comments>http://heymans.org/2009/03/key-method-to-prioritizing-efficiently/#comments</comments>
		<pubDate>Wed, 11 Mar 2009 23:52:05 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Time Management]]></category>
		<category><![CDATA[coaching]]></category>
		<category><![CDATA[habits]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[priority]]></category>
		<category><![CDATA[productivity]]></category>
		<category><![CDATA[psychology]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=285</guid>
		<description><![CDATA[Chances are high that you and your team have a lot of things to do at the moment and a long list of tasks is currently on your plates. There&#8217;s a cool way to find out what&#8217;s the smartest thing to do first by putting each task in one of 4 group in terms of [...]]]></description>
			<content:encoded><![CDATA[<p>Chances are high that you and your team have a lot of things to do at the moment and a long list of tasks is currently on your plates.<br />
There&#8217;s a cool way to find out what&#8217;s the smartest thing to do first by putting each task in one of 4 group in terms of saving time.</p>
<p>Have a look at my sketch drawing in the picture &#8230;<br />
<a href="http://www.flickr.com/photos/heymans/3330447934/"><img src="http://heymans.org/wp-content/uploads/2009/03/3330447934_45267d15ac.jpg" alt="setting priorities" title="setting priorities" width="500" height="333" class="aligncenter size-full wp-image-286" /></a></p>
<ol>
<li>important things that are urgent</li>
<li>important things that are less urgent, but not less important</li>
<li>not so very important things that are urgent</li>
<li>unimportant things that aren&#8217;t urgent</li>
</ol>
<p>You can put everything you have to do in one of those 4 groups. Groups 1 and 4 are the obvious ones, do stuff in 1 now, never do anything that gets into 4, easy. But the things in groups 2 and 3 could trick you in wasting your time if you don&#8217;t pay attention. </p>
<p>This isn&#8217;t rocket science, you already know this but I think it&#8217;s a good way to visualize the choices you have to make.</p>
<p>It takes <strong>discipline</strong> and <strong>courage</strong> at times to focus on the tasks you put in group 2, but often they are the ones that help you grow out of hard situations. Stuff that goes into <strong>group 2 for a PM</strong> for instance could be making a <strong>detailed planning</strong> or a <strong>strong risk log</strong>, or <strong>something strategical</strong> like writing out a new process and presenting it to your own project office or to your executives.</p>
<p>Have a good <strong>look at what your project teams are doing</strong>, it&#8217;s the job of a PM to indicate the urgency and the importance of different things for them but also to <strong>help them make the correct assessment</strong> and maybe the drawing can help you with that when things get fuzzy (like they do).</p>
<p>I got a lot of things like this explained to me in far greater detail by Inge De Bruyn from <a href="http://www.degroeipraktijk.be/">De Groeipraktijk</a> and use the advice quite a lot, they do training workshops and seminars on all kind of soft skills. This post isn&#8217;t endorse by them but I&#8217;d recommend them to you if you&#8217;d ask me.</p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/03/key-method-to-prioritizing-efficiently/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>3 Tools to Make Work Breakdown Structure</title>
		<link>http://heymans.org/2009/02/3-tools-to-make-work-breakdown-structure/</link>
		<comments>http://heymans.org/2009/02/3-tools-to-make-work-breakdown-structure/#comments</comments>
		<pubDate>Sun, 22 Feb 2009 20:37:24 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Integration Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[mindmap]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[scope]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[WBS]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=250</guid>
		<description><![CDATA[After making a preliminary scope statement and some high level planning, most contracts can be signed and actual production can start. The direction of the project is clear but more details are needed to efficiently control the work. For this I get the project team together and make a Work Breakdown Structure (WBS), it&#8217;s a [...]]]></description>
			<content:encoded><![CDATA[<p>After making a preliminary scope statement and some high level planning, most contracts can be signed and actual production can start. The direction of the project is clear but more details are needed to efficiently control the work. For this  I get the project team together and make a <a href="http://en.wikipedia.org/wiki/Work_breakdown_structure" target="_blank">Work Breakdown Structure</a> (<a href="http://en.wikipedia.org/wiki/Work_breakdown_structure" target="_blank">WBS</a>), it&#8217;s a <strong>detailed scope description</strong> where you try to put everything into that&#8217;s needed to finish the project. I found a few fun ways to do this: </p>
<ul>
<li><strong>Make a mind map</strong>. You can use a tool like <a href="http://freemind.sourceforge.net/wiki/index.php/Main_Page">Freemind</a> for this. A mind map has a tree structure just like that of a <a href="http://en.wikipedia.org/wiki/Work_breakdown_structure" target="_blank">WBS</a>. Most mind mapping tools are made for brainstorming so they allow you to work fast.</li>
<li><strong>Work with Post-Its.</strong> Sit together at a fairly big clean table or whiteboard and group the elements of work in columns of Post-Its. Use at least <strong>2 colors</strong>, a color to write group names on and a color for work elements. Take a picture of the whole thing after you&#8217;re done.</li>
<li><strong>Use <a href="http://en.wikipedia.org/wiki/Scrum_(development)" target="_blank">SCRUM</a> user stories to find and define the tasks</strong>. SCRUM is a methodology for agile software development, but most of it can be applied to just about any industry. <a href="http://en.wikipedia.org/wiki/Scrum_(development)" target="_blank">SCRUM</a> calls a collection of tasks a project backlog, which are derived from user stories. This video I found at <a href="http://www.agile-software-development.com/2009/01/10-minute-video-introduction-to-scrum.html" target="_blank">Agile Software Development</a> explains everything you need to know in about 8min.</li>
<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/Q5k7a9YEoUI&#038;color1=0xb1b1b1&#038;color2=0xcfcfcf&#038;hl=en&#038;feature=player_embedded&#038;fs=1"></param><param name="allowFullScreen" value="true"></param><embed src="http://www.youtube.com/v/Q5k7a9YEoUI&#038;color1=0xb1b1b1&#038;color2=0xcfcfcf&#038;hl=en&#038;feature=player_embedded&#038;fs=1" type="application/x-shockwave-flash" allowfullscreen="true" width="425" height="344"></embed></object>
</ul>
<p>Most of the projects I manage are a bit too complex to make a <a href="http://en.wikipedia.org/wiki/Work_breakdown_structure" target="_blank">WBS</a> on a presales budget but if it&#8217;s possible for you to do this exercise up front it&#8217;s an <strong>excellent basis for estimates</strong>. You need <strong>the full team</strong> for this unless you&#8217;re a complete domain expert yourself. </p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/02/3-tools-to-make-work-breakdown-structure/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>How does a project get a year late?</title>
		<link>http://heymans.org/2009/02/how-does-a-project-get-a-year-late/</link>
		<comments>http://heymans.org/2009/02/how-does-a-project-get-a-year-late/#comments</comments>
		<pubDate>Tue, 17 Feb 2009 07:41:47 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[pm]]></category>
		<category><![CDATA[proverb]]></category>
		<category><![CDATA[wisdom]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=243</guid>
		<description><![CDATA[One day at a time. This little piece of wisdom is one of my favorite project management proverbs. It&#8217;s number 40 in a long list of PM jokes and proverbs I found the other day. Interesting stuff, but be warned, you&#8217;ll notice about 95% of it is horribly corny.]]></description>
			<content:encoded><![CDATA[<blockquote><p><strong>One day at a time.</strong></p></blockquote>
<p>This little piece of wisdom is one of my favorite project management proverbs. It&#8217;s number 40 in a long list of <a href="http://www.visitor-tracking.com/pm-jokes.php" target="_blank">PM jokes and proverbs</a> I found the other day. Interesting stuff, but be warned, you&#8217;ll notice about 95% of it is horribly corny.</p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/02/how-does-a-project-get-a-year-late/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Planning the Perfect Deadline</title>
		<link>http://heymans.org/2009/02/planning-the-perfect-deadline/</link>
		<comments>http://heymans.org/2009/02/planning-the-perfect-deadline/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 07:00:03 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[checklist]]></category>
		<category><![CDATA[deadline]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[proactive]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=192</guid>
		<description><![CDATA[Here are some important things you can use as a checklist when thinking about deadlines. Check to see if a deadline is on a Friday, this happens all the time and it&#8217;s probably a bad idea because people make plans for the weekend and if something should go wrong you&#8217;re in for a challenge. I [...]]]></description>
			<content:encoded><![CDATA[<p>Here are some important things you can use as a <strong>checklist</strong> when thinking about <strong>deadlines</strong>.</p>
<ul>
<li><strong>Check to see if a deadline is on a Friday</strong>, this happens all the time and it&#8217;s probably a bad idea because people make plans for the weekend and if something should go wrong you&#8217;re in for a challenge. <del datetime="2009-02-07T00:08:26+00:00">I like deadlines on Mondays.</del> As <a href="http://www.derschmale.com/">David</a> points out, midweek is probably a lot better, that lowers the risk of having to work in weekends even more.</li>
<li><strong>Are you responsible for another project that has important events at the same time?</strong> Act proactively and early if this happens, reschedule or ask a colleague to help out. </li>
<li><strong>Take a look at the vacation planner</strong>, just maybe that key stakeholder or that rockstar server administrator the project depends on will be off rock climbing in the Alps that week. Ask HR.
</li>
<li><strong>Is the deadline on an official holiday?</strong> For other countries (when working with offshore companies) you can probably find an official calendar at <a href="http://icalshare.com/">iCalShare</a> (compatible with a lot more than just iCal) </li>
<li><strong>Does the delivery process take a long time?</strong> Think about this, some deployments or integrations take a long time to prepare or execute.
</li>
<li><strong>Make sure you have the correct acceptance criteria in your hands.</strong> Call you client some time up front and tell him what the status of the project will be at the moment of the deadline, even if it&#8217;s already in the project charter. If something is still ambiguous at a late moment it should be defined better, right away. </li>
</ul>
<p><strong>A classic example</strong> of last minute ambiguity is the &#8220;time of day&#8221; discussion, aka &#8220;we meant ready by morning on the day of the deadline, not 6pm because our VP needs to sign off the campaign for the final go live&#8221;.</p>
<p>Remember, you can ask all vital planning information you need from any stakeholder once you own the project. </p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/02/planning-the-perfect-deadline/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>What does a good Project Manager do actually?</title>
		<link>http://heymans.org/2009/01/what-does-a-good-project-manager-do-actually/</link>
		<comments>http://heymans.org/2009/01/what-does-a-good-project-manager-do-actually/#comments</comments>
		<pubDate>Sat, 24 Jan 2009 17:16:01 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[behavior]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[PMI]]></category>
		<category><![CDATA[responsibility]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=170</guid>
		<description><![CDATA[Good question, someone asked me a few days ago and it got me thinking about the essentials. So what does a good PM do actually? Here&#8217;s a list of good PM behaviors that I think are important: communicate with all the people who are influenced by the project monitor and control the scope, budget and [...]]]></description>
			<content:encoded><![CDATA[<p>Good question, someone asked me a few days ago and it got me thinking about the essentials. So what does a good PM do actually?</p>
<p>Here&#8217;s a list of <strong>good PM behaviors</strong> that I think are important:</p>
<ol>
<li><strong>communicate</strong> with all the people who are influenced by the project</li>
<li>monitor and control the <strong>scope</strong>, <strong>budget</strong> and <strong>planning</strong> constrains</li>
<li><strong>understand the content</strong> of the project in enough detail to communicate, monitor and control <strong>efficiently</strong></li>
<li>create situations that allow the team to <strong>focus</strong> on the project goals</li>
<li><strong>help people</strong> to get the feedback they need to <strong>grow</strong> (not the same as coaching)</li>
</ol>
<p>To give you some context on my list, in <a href="http://nascom.be" target="_blank">my company</a> we create teams around a project most of the time, it&#8217;s what the <a href="http://www.amazon.co.uk/gp/product/193069945X?ie=UTF8&#038;tag=blogheymansor-21&#038;linkCode=as2&#038;camp=1634&#038;creative=19450&#038;creativeASIN=193069945X">Project Management Body of Knowledge</a><img src="http://www.assoc-amazon.co.uk/e/ir?t=blogheymansor-21&#038;l=as2&#038;o=2&#038;a=193069945X" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /> would call a <em>projectized organization</em>. </p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/01/what-does-a-good-project-manager-do-actually/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Shorter Project Charters</title>
		<link>http://heymans.org/2009/01/shorter-project-charters/</link>
		<comments>http://heymans.org/2009/01/shorter-project-charters/#comments</comments>
		<pubDate>Mon, 19 Jan 2009 01:17:27 +0000</pubDate>
		<dc:creator>Bert</dc:creator>
				<category><![CDATA[Mindmaps]]></category>
		<category><![CDATA[Project Initiation]]></category>
		<category><![CDATA[assumptions]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[constraints]]></category>
		<category><![CDATA[mindmap]]></category>
		<category><![CDATA[pmbok]]></category>
		<category><![CDATA[PMI]]></category>
		<category><![CDATA[project charter]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://heymans.org/?p=107</guid>
		<description><![CDATA[A project charter is the document that provides ownership (and authority) to the PM for a project, after someone hands that to you or when you write it up yourself and get it signed, you are the owner of the project on behalf of your company. The point is, you start out with it and [...]]]></description>
			<content:encoded><![CDATA[<p>A project charter is the document that provides ownership (and authority) to the PM for a project, after someone hands that to you or when you write it up yourself and get it signed, you are the owner of the project on behalf of your company. </p>
<p>The point is, you start out with it and maintain it during the course of the project. I never get project charters handed to me in my current work situation, I always write them myself. And I like them short.</p>
<p>According to what I understand from the <a href="http://www.amazon.co.uk/gp/product/193069945X?ie=UTF8&#038;tag=blogheymansor-21&#038;linkCode=as2&#038;camp=1634&#038;creative=19450&#038;creativeASIN=193069945X">PMBOK</a><img src="http://www.assoc-amazon.co.uk/e/ir?t=blogheymansor-21&#038;l=as2&#038;o=2&#038;a=193069945X" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /> there are 3 things that are absolutely essential for a good project charter, and those are:</p>
<ul>
<li>a <em>business case</em></li>
<li>the projects <em>constraints</em></li>
<li>the <em>assumptions</em> (or <em>dependencies</em>)</li>
</ul>
<p>Looking at only those 3 things that&#8217;s not much is it? Some of the things I always add are:</p>
<ul>
<li>high level in scope</li>
<li>high level out of scope</li>
<li>communication plan, list of major project stakeholders with their coordinates and roles</li>
<li>general terms and conditions in the mother language of the sponsor, for legal purposes</li>
</ul>
<p>I made a <a href="http://en.wikipedia.org/wiki/Mind_map">mindmap</a> exercise in <a href="http://freemind.sourceforge.net">Freemind</a> a long time ago by looking at some example project charters I got my hands on, the combination I came up with looked a bit like this:</p>
<p><img src="http://heymans.org/wp-content/uploads/2009/01/berts_project_charter.png" alt="berts_project_charter" title="berts_project_charter" width="350" height="387" class="aligncenter size-full wp-image-114" /></p>
<p>But that&#8217;s too long to maintain if you have a <strong>high number</strong> of <strong>relatively short</strong> projects to manage. </p>
<p>Today my actual essentials look more like this:<br />
<img src="http://heymans.org/wp-content/uploads/2009/01/project_charter_mindmap_conclusion.png" alt="project charter mindmap conclusion" title="project charter mindmap conclusion" width="460" height="410" class="aligncenter size-full wp-image-115" /></p>
<p>Here&#8217;s the big mindmap:<br />
<a href="http://heymans.org/wp-content/uploads/2009/01/project_charter_comparison.png"><img src="http://heymans.org/wp-content/uploads/2009/01/project_charter_comparison-300x240.png" alt="project charter comparison" title="project charter comparison" width="300" height="240" class="aligncenter size-medium wp-image-119" /></a></p>
<p><a href='http://heymans.org/wp-content/uploads/2009/01/project_charter_comparison.pdf'>project charter comparison PDF download</a><a href="http://heymans.org/wp-content/uploads/2009/01/project_charter_comparison.pdf"><img src="http://heymans.org/wp-content/uploads/2009/01/pdficon_small.gif" alt="pdficon_small" title="pdficon_small" width="17" height="17" /></a></p>
<p><a href='http://heymans.org/wp-content/uploads/2009/01/project_charter_comparison.mm'>Freemind source file (.mm)</a><a href='http://heymans.org/wp-content/uploads/2009/01/project_charter_comparison.mm'> <img src="http://heymans.org/wp-content/uploads/2009/01/freemind_icon.png" alt="freemind_icon" title="freemind_icon" width="17" height="17" /></a></p>
<p>I want to share the whole exercise with you, so here you go, source and everything in a variety of formats.</p>
]]></content:encoded>
			<wfw:commentRss>http://heymans.org/2009/01/shorter-project-charters/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
