<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Project Kaizen Day Two</title>
	<link>http://www.reformingprojectmanagement.com/2005/12/06/570/</link>
	<description>The magazine for the project age</description>
	<pubDate>Thu, 07 Aug 2008 22:42:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: David Whelbourn</title>
		<link>http://www.reformingprojectmanagement.com/2005/12/06/570/#comment-2113</link>
		<pubDate>Mon, 19 Dec 2005 16:22:58 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2005/12/06/570/#comment-2113</guid>
					<description>I am often asked 

Where do we begin when improving our project management processes?

Similar to your project kaizen outline.

I work with PRINCE2 as a project methodology and one of its initial points is control.

1. Controlled Start
2. Controlled Progress and 
3. Controlled Close

Many a successful project has been built on solid foundations, so I would push people in the direction of improving their project initiation and business case (that will be used throughout the project to guide decisions on change). If you already have solid initiation processes that produce good artifacts / products then move down the line and look at the controls around work authorisation and quality, finally end with the controlled close aspects.

Just my thoughts to help people think about Kaizen within their project environments</description>
		<content:encoded><![CDATA[<p>I am often asked </p>
<p>Where do we begin when improving our project management processes?</p>
<p>Similar to your project <acronym title="Japanese term for continuous improvement">kaizen</acronym> outline.</p>
<p>I work with PRINCE2 as a project methodology and one of its initial points is control.</p>
<p>1. Controlled Start<br />
2. Controlled Progress and<br />
3. Controlled Close</p>
<p>Many a successful project has been built on solid foundations, so I would push people in the direction of improving their project initiation and business case (that will be used throughout the project to guide decisions on change). If you already have solid initiation processes that produce good artifacts / products then move down the line and look at the controls around work authorisation and quality, finally end with the controlled close aspects.</p>
<p>Just my thoughts to help people think about <acronym title="Japanese term for continuous improvement">kaizen</acronym> within their project environments
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
