<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Software Development and Project Management</title>
	<atom:link href="http://blog.brodzinski.com/2007/08/software-development-and-project.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.brodzinski.com/2007/08/software-development-and-project.html</link>
	<description>Dealing with software projects in real life</description>
	<lastBuildDate>Fri, 10 Feb 2012 19:07:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2007/08/software-development-and-project.html#comment-1890</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Mon, 06 Aug 2007 16:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/08/software-development-and-project-management.html#comment-1890</guid>
		<description>Yes, when you develop software using agile methods it definitely has impact on a way you manage projects. And yes, that part of project management which covers software development must be adjusted to suit agile model (managing iterations as you point). However, the whole rest of project doesn&#039;t change much. It depends on project how big is the software development part within the project.&lt;br/&gt;&lt;br/&gt;Generalizing a bit - project management always has to deal with different processes which are parts of the bigger whole (no matter if it is software development, hardware delivery or acceptance tests) and project manager has always adjust the his practices to to achieve a success. It really doesn&#039;t matter if you talk about agile or any other kind of practices.</description>
		<content:encoded><![CDATA[<p>Yes, when you develop software using agile methods it definitely has impact on a way you manage projects. And yes, that part of project management which covers software development must be adjusted to suit agile model (managing iterations as you point). However, the whole rest of project doesn&#8217;t change much. It depends on project how big is the software development part within the project.</p>
<p>Generalizing a bit &#8211; project management always has to deal with different processes which are parts of the bigger whole (no matter if it is software development, hardware delivery or acceptance tests) and project manager has always adjust the his practices to to achieve a success. It really doesn&#8217;t matter if you talk about agile or any other kind of practices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajeev Singh</title>
		<link>http://blog.brodzinski.com/2007/08/software-development-and-project.html#comment-1889</link>
		<dc:creator>Rajeev Singh</dc:creator>
		<pubDate>Thu, 02 Aug 2007 20:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/08/software-development-and-project-management.html#comment-1889</guid>
		<description>I agree, that project management already exists regardless of the methodology.&lt;br/&gt;&lt;br/&gt;Agile practices, however, introduce the need of managing these short cycles of development called iterations - Iteration Management. &lt;br/&gt;&lt;br/&gt;On smaller projects, often a Project Manager is an Iteration Manager as well. Even on the outward looking side (towards the client) where a PM concentrates her/his attention to, the frequency at which the iterations play themselves may change a few practices around communication and the payload of the communication. Progress of the team is reflected using a bit more sophisticated yet meaningful concepts like velocity, load factor, etc.&lt;br/&gt;&lt;br/&gt;So, I guess, what I am trying to say is that Agile requires to manage iterations and forces a PM to change their pace and nature of communication in a certain fashion. That&#039;s all there&#039;s to Agile Project Management.</description>
		<content:encoded><![CDATA[<p>I agree, that project management already exists regardless of the methodology.</p>
<p>Agile practices, however, introduce the need of managing these short cycles of development called iterations &#8211; Iteration Management. </p>
<p>On smaller projects, often a Project Manager is an Iteration Manager as well. Even on the outward looking side (towards the client) where a PM concentrates her/his attention to, the frequency at which the iterations play themselves may change a few practices around communication and the payload of the communication. Progress of the team is reflected using a bit more sophisticated yet meaningful concepts like velocity, load factor, etc.</p>
<p>So, I guess, what I am trying to say is that Agile requires to manage iterations and forces a PM to change their pace and nature of communication in a certain fashion. That&#8217;s all there&#8217;s to Agile Project Management.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

