<?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>A PM&#039;s workshop &#187; Management</title>
	<atom:link href="http://www.magnone.eu/archives/tag/management/feed" rel="self" type="application/rss+xml" />
	<link>http://www.magnone.eu</link>
	<description>Information is for projects like water for life. The success lies in a careful management of needs.</description>
	<lastBuildDate>Wed, 24 Feb 2010 13:06:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Micro management &#8211; Configuration Strategy Management 1.0.0te</title>
		<link>http://www.magnone.eu/archives/2920</link>
		<comments>http://www.magnone.eu/archives/2920#comments</comments>
		<pubDate>Wed, 11 Nov 2009 15:48:26 +0000</pubDate>
		<dc:creator>Eugenio</dc:creator>
				<category><![CDATA[Prince2]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[templates]]></category>

		<guid isPermaLink="false">http://www.magnone.eu/?p=2920</guid>
		<description><![CDATA[Working on templates requires a certain dose of system-centric attitude. However, tools are built for being used by colleagues. This means that every instrument (with its set of rules) fits with the others, this to form an elastic structure that allows any user (producer or consumer) to find his/her hand with the [...]]]></description>
			<content:encoded><![CDATA[<h2>Available template: <a href="http://www.magnone.eu/prince2-templates-2/configuration-management-strategy-1-0-0" target="_blank">Configuration Strategy Management 1.0.0</a></h2>
<p>This document offers the global approach to one of the most important tool/system for managing any project that involves more than one developer (however, it is extremely useful in that case too). The concept evolves from the distribution of the correct (updated) information to the management of each produced item. In this way, any asset is ranked on the basis of its readiness (quality) and made available in a way that any action on this piece of work can be collected to be analysed either for auditing or  evaluation purposes.</p>
<p>The template has been built on the Prince2 indications. A lot of care has been dedicated to the Quality section, where are listed some very important topics.</p>
<address>Note: in the new Prince2 edition, Configuration and Change Management are set in the same process. In order to proactively fulfils this requirement, some improvements are left for the next edition.</address>
<h2>Topic of the day: micro-management</h2>
<p>Working on templates requires a certain dose of system-centric attitude. However, tools are built for being used by colleagues. This means that every instrument (with its set of rules) fits with the others, this to form an elastic structure that allows any user (producer or consumer) to find his/her hand with the tool.</p>
<h2>Rules and management</h2>
<p>There is an interesting <a href="http://www.infoq.com/news/2009/11/agile-micromanagement">post</a> about Agile and micro-management. As usual, there is the spook of a manager who needs to interfere with developers decisions. Especially when these decisions are taken by the group that works as a <a href="http://en.wikipedia.org/wiki/Posse_comitatus_%28common_law%29" target="_blank">posse comitatus</a> .  If anybody needs to impose any decision onto the colleagues, just for the sake of his/her own position, the person – from any viewpoint – is a danger for the company.  Being accountable of the results could imply some judgment that shall be asserted. This is a process that involves the whole group. Each person should find comfortable enough for completing the task he/she has accepted within a reasonable grade of freedom.  Any scenario where the “boss” – having lost the confrontation either with his/her peer or boss (customer) wants to take a revenge on the team, the problem lies within each person forming the aggregation of people who were not able to form a team.  Literature, from Greek Tragedy to the modern psychoanalysis is bountiful of examples about these sort of conflicts. A project is not an arena or a stage where personal issues can be brought in for the sake of our self-complacency.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.magnone.eu/archives/2920/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

