<?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>getzcope.com &#187; Manifesto</title>
	<atom:link href="http://www.getzcope.com/blog/tag/manifesto/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.getzcope.com/blog</link>
	<description>ZCOPE - Projektmanagement macht Spass!</description>
	<lastBuildDate>Fri, 20 May 2011 16:41:31 +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>Core Agile Values</title>
		<link>http://www.getzcope.com/blog/2009/10/28/core-agile-values/</link>
		<comments>http://www.getzcope.com/blog/2009/10/28/core-agile-values/#comments</comments>
		<pubDate>Wed, 28 Oct 2009 15:52:22 +0000</pubDate>
		<dc:creator>Oliver Pretz</dc:creator>
				<category><![CDATA[blog-de]]></category>
		<category><![CDATA[blog-en]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Manifesto]]></category>
		<category><![CDATA[Project management]]></category>
		<category><![CDATA[Values]]></category>

		<guid isPermaLink="false">http://www.getzcope.com/blog/?p=739</guid>
		<description><![CDATA[Thanks to the authors of the Manifesto for agile software development the term agility has become increasingly popular in the last 5 years. The Manifesto states explicitly what they believed, their core values and enduring purpose. It pushed the agile software development movement. The Manifest established a set of 4 simple rules or core values [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-750" src="http://www.getzcope.com/blog/wp-content/uploads/2009/10/Core-Values2.png" alt="Core Values" width="320" height="259" /></p>
<p>Thanks to the authors of the Manifesto for agile software development the term agility has become increasingly popular in the last 5 years. The Manifesto states explicitly what they believed, their core values and enduring purpose. It pushed the agile software development movement. The Manifest established a set of 4 simple rules or core values for developing complex innovative systems. Following the co-author Jim Highsmith with his book “Agile Project Management” we can easily apply these core value statements to Agile Project Management:</p>
<p><strong>Responding to change: Don’t plan. Explore.</strong><br />
Reflects the agile viewpoint to focus on envision-explore not on plan-do and on adaption rather than anticipation. Innovative projects are characterized by envisioning and exploring rather than detailed planning and task executing. Thus the team has to see changes as a friend not as an enemy of the project.</p>
<p><strong>Working products: Documents don&#8217;t work. Products do.</strong><br />
Describes the idea of delivering iterative versions of the real product according to the motto: “Documents don&#8217;t work. Products do.” With the side effect of lowering the cost of change or failure following the theory of early failure detection: “the earlier the cheaper”. In the field of Software Engineering the advantages are common known: Requirements are changing and large design and concept phases leading to massive failures, because then the linear implementation of the requirements without feedback and reliable tests often ends up in a disaster.</p>
<p><strong>Customer Collaboration: Confidence over Contract Negotiations.</strong><br />
This value describes the importance of a close partnership to the customer in which each person has a specific role and responsibility. To prioritize the human aspects of a partnership more than it&#8217;s contracts means to find a collaborative relationship to the customer marked by confidence not driven by contract disputes. Because the goal is to deliver value to the customers, the customer defines the requirements that provide value and the business objectives quantifying it.</p>
<p><strong>Individuals and Interaction: Making Participatory Decisions.</strong><br />
This value focuses on the importance of skilled peoples within agile projects. Without the right people all processes and tolls won&#8217;t produce results. Tools are very useful for speeding up efficiency but rely on knowledge and capabilities of the team. “A fool with a tool is still a fool!” The agile movement supports the individuals with the concept of self-organization, self-discipline and respect for the individual. Attaining this value is one of the most difficult in practice. The team has the autonomy to organize itself to fulfill the requirements in a best possible way. That is not common! At the end it&#8217;s a part of a new project culture, a new type of leadership that has to be implemented with lots of experience, discipline and social competence.</p>
<p>So let’s go for it ;-)<br />
Yours,<br />
Oliver Pretz</p>
]]></content:encoded>
			<wfw:commentRss>http://www.getzcope.com/blog/2009/10/28/core-agile-values/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
