<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-5210159427493949178.post4141921214842384040..comments</id><updated>2009-10-26T20:03:20.215Z</updated><title type='text'>Comments on Agile Development Made Easy!: The Problem With Planning</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.agile-software-development.com/feeds/4141921214842384040/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default'/><link rel='alternate' type='text/html' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html'/><author><name>Kelly Waters</name><uri>http://www.blogger.com/profile/17507745125859750885</uri><email>allaboutagile@gmail.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-5210159427493949178.post-7960509571293753932</id><published>2009-10-26T19:35:44.334Z</published><updated>2009-10-26T19:35:44.334Z</updated><title type='text'>I think I know what you mean. The problem with pla...</title><content type='html'>I think I know what you mean. The problem with planning is that it relies on &amp;quot;knowns&amp;quot; and stability of circumstances over time, when more often the back-drop is unknowns (or even unknowables) and dynamic circumstances. So I&amp;#39;d agree that being able to adapt is often more important. I think I blogged on a similar theme a while ago myself&lt;br /&gt;&lt;br /&gt;http://blog.capablepeople.co.uk/2008/08/is-long-term-goal-driven-planning-a-waste-of-time/</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default/7960509571293753932'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default/7960509571293753932'/><link rel='alternate' type='text/html' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html?showComment=1256585744334#c7960509571293753932' title=''/><author><name>shaun sayers</name><uri>http://www.capablepeople.co.uk</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html' ref='tag:blogger.com,1999:blog-5210159427493949178.post-4141921214842384040' source='http://www.blogger.com/feeds/5210159427493949178/posts/default/4141921214842384040' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-5210159427493949178.post-4871438472494684758</id><published>2009-10-25T14:04:00.103Z</published><updated>2009-10-25T14:04:00.103Z</updated><title type='text'>The only thing we have to fear is...change itself....</title><content type='html'>The only thing we have to fear is...change itself.  This is what most planning is about.  Protecting against change.  At least a perception that we can avoid change.  Wikipedia.org states that agility means the capability of rapidly and cost efficiently adapting to changes.  Let&amp;#39;s face it...software development is all about evolving a software product to deliver business value over time.  Evolution is not a planned event, it is a guided event.  The most important thing you need is an initial vision of the product, a definition of what constitutes business value, an open minded team/organization that can adapt to changes for the sake of TRUE business value, and a culture and processes that expect and embrace change.&lt;br /&gt;&lt;br /&gt;Peter DeYoe&lt;br /&gt;www.peterdeyoe.wordpress.com</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default/4871438472494684758'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default/4871438472494684758'/><link rel='alternate' type='text/html' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html?showComment=1256479440103#c4871438472494684758' title=''/><author><name>Peter DeYoe</name><uri>http://www.peterdeyoe.wordpress.com</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html' ref='tag:blogger.com,1999:blog-5210159427493949178.post-4141921214842384040' source='http://www.blogger.com/feeds/5210159427493949178/posts/default/4141921214842384040' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-5210159427493949178.post-6119158143032640720</id><published>2009-10-19T11:04:44.781Z</published><updated>2009-10-19T11:04:44.781Z</updated><title type='text'>Fear seems to be a factor. Fixed cost is seen as a...</title><content type='html'>Fear seems to be a factor. Fixed cost is seen as a safety net, so people prefer to have everything planned and costed up front, rather than releasing funding in smaller chunks to allow for the inevitable change in direction and scope.&lt;br /&gt;I often have conversations beginning with &amp;quot;... but Agile can&amp;#39;t work with fixed cost projects?&amp;quot;. I try to counter that with, &amp;quot;Do you think it is more acceptable to agree a cost, knowing full well that the project will run over budget?&amp;quot;, but still they cling... Perhaps we need to convince the accountants?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default/6119158143032640720'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default/6119158143032640720'/><link rel='alternate' type='text/html' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html?showComment=1255950284781#c6119158143032640720' title=''/><author><name>The Agile Surfer</name><uri>http://www.blogger.com/profile/05398595946595061274</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html' ref='tag:blogger.com,1999:blog-5210159427493949178.post-4141921214842384040' source='http://www.blogger.com/feeds/5210159427493949178/posts/default/4141921214842384040' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-5210159427493949178.post-6054041530483018660</id><published>2009-10-05T19:21:32.442Z</published><updated>2009-10-05T19:21:32.442Z</updated><title type='text'>Couldn't agree more. Detailed, up-front planning i...</title><content type='html'>Couldn&amp;#39;t agree more. Detailed, up-front planning is usually a waste of time considering that once we start to get feedback the direction can change considerably. What we think the market or our users want isn&amp;#39;t always, or usually, the case. As you say, it&amp;#39;s necessary to have goals and a vision, but for some reason, most people see a project plan as set in stone. Working against goals rather than milestones can retain the flexibility we need to remain truly agile.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default/6054041530483018660'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5210159427493949178/4141921214842384040/comments/default/6054041530483018660'/><link rel='alternate' type='text/html' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html?showComment=1254770492442#c6054041530483018660' title=''/><author><name>Robert Dempsey</name><uri>http://www.adsdevshop.com</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.agile-software-development.com/2009/10/problem-with-planning.html' ref='tag:blogger.com,1999:blog-5210159427493949178.post-4141921214842384040' source='http://www.blogger.com/feeds/5210159427493949178/posts/default/4141921214842384040' type='text/html'/></entry></feed>