<?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>Heymans.org &#187; WBS</title>
	<atom:link href="http://heymans.org/tag/wbs/feed/" rel="self" type="application/rss+xml" />
	<link>http://heymans.org</link>
	<description>I&#039;m Bert Heymans, a project manager, moonlighting hobby photographer and an all-round tech adventurer.</description>
	<lastBuildDate>Mon, 30 Jan 2012 15:55:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>3 Tools to Make Work Breakdown Structure</title>
		<link>http://heymans.org/2009/02/3-tools-to-make-work-breakdown-structure/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=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>
	</channel>
</rss>

