<?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:atom="http://www.w3.org/2005/Atom"
				  >
<channel>
<atom:link href="http://marro.ws/profiles/idriscin/rss" rel="self" type="application/rss+xml" />
<title>Marrows - idriscin</title>
<link>http://marro.ws/profiles/idriscin/rss</link>
<description><![CDATA[idriscin's Marked Items]]></description>
<pubDate>Sat, 13 Mar 2010 22:42:18 +0000</pubDate>
<item>
<title>project_life_cycle</title>
<link>http://marro.ws/project_life_cycle</link>
<pubDate>Tue, 20 Oct 2009 18:50:00 +0000</pubDate>
<description><![CDATA[<p><strong>Create your own Project Life Cycle...</strong></p>
<p>A Project Life Cycle is a series of steps that you take to complete a project from start to finish. Of course, it implies that you can complete the same steps for every project - so should you?</p>
<p>In principle, yes. Every project will have an Initiation phase, a Planning phase, an Execution phase and a Closure phase. However within these phases, the steps you take may vary slightly between projects.</p>
<p>The trick is to create a Life Cycle that is generic enough to use for all of your projects, while still being specific enough to add value and save you time on delivery. Here's how to do it...</p>
<p><strong>Map it out</strong></p>
<p>Every project is delivered in some form of Life Cycle. You probably usually define your project upfront, then you'll hire your team, you'll plan and complete a set of tasks to create some deliverables and then get your customer to sign it off as complete. This sequence of steps are what is called a "Life Cycle" and chances are that you're using the same generic Life Cycle every time you deliver a project!</p>
<p>So start by mapping out your current project Life Cycle on a blank sheet of paper and identify the elements that you know work well, and those that don't.</p>
<p><strong>And improve it</strong></p>
<p>Then try and improve your Life Cycle by analyzing why certain steps don't work well currently. Analyze the root cause and identify which steps you could take instead, to improve your chance of success. For instance, maybe "scope creep" is an issue for you, so by putting in place better steps for managing changes to scope, it would help.</p>
<p>Once you have identified the sequence of steps that you know will deliver your projects successfully from start to finish, the next thing you need to do is to "get detailed".</p>
<p><strong>Get detailed</strong></p>
<p>With a clearly defined series of steps, you now need to define the tasks and activities that are needed to perform each step efficiently. For instance, if your first step was to get funding for your project, then do you need to create a Business Case or Financial Plan to do it? What type of person will authorize the funding and what information will they need to do it?</p>
<p>For every step, describe how you intend to do it, the tasks and activities to be taken and who is responsible for them.</p>
<p><strong>Tool up</strong></p>
<p>Great, so you have mapped out your life cycle for delivering projects. Now you need to use a tool that allows you to link all of the steps together into a methodology, so that you can follow it for every project you undertake.</p>]]></description>
<author>idriscinn@gmail.com (idriscin)</author>
<guid isPermaLink="true" >http://marro.ws/project_life_cycle</guid>
</item>
</channel>
</rss>