<?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-15466608.post6572833068051719808..comments</id><updated>2008-05-01T21:22:44.090+10:00</updated><title type='text'>Comments on Better Projects: Requirements Management - the Six C's explained</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.betterprojects.net/feeds/6572833068051719808/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/6572833068051719808/comments/default'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/04/requirements-management-six-cs_25.html'/><author><name>Craig Brown</name><uri>http://www.blogger.com/profile/01210437173582289473</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>3</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-15466608.post-2915912162115228511</id><published>2008-05-01T21:22:44.090+10:00</published><updated>2008-05-01T21:22:44.090+10:00</updated><title type='text'>And Stephen at Requirements Network Group has sugg...</title><content type='html'>And Stephen at Requirements Network Group has suggested we add CAUSE as a precendent to the other 6Cs.&lt;BR/&gt;&lt;BR/&gt;Great idea.  We now have 7 Cs.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/6572833068051719808/comments/default/2915912162115228511'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/6572833068051719808/comments/default/2915912162115228511'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/04/requirements-management-six-cs_25.html?showComment=1209640964090#c2915912162115228511' title=''/><author><name>Craig Brown</name><uri>http://www.blogger.com/profile/01210437173582289473</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='03178891453306926128'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.betterprojects.net/2008/04/requirements-management-six-cs_25.html' ref='tag:blogger.com,1999:blog-15466608.post-6572833068051719808' source='http://www.blogger.com/feeds/15466608/posts/default/6572833068051719808' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-15466608.post-2224233002928818810</id><published>2008-04-28T21:58:11.660+10:00</published><updated>2008-04-28T21:58:11.660+10:00</updated><title type='text'>Thanks for the feedback Glen.  It's always a pleas...</title><content type='html'>Thanks for the feedback Glen.  &lt;BR/&gt;&lt;BR/&gt;It's always a pleasure to have &lt;A HERF="http://herdingcats.typepad.com/"&gt;respected peers&lt;/A&gt; give positive feedback.&lt;BR/&gt;&lt;BR/&gt;We are in agreement about frameworks coming together.  &lt;BR/&gt;&lt;BR/&gt;I saw a good post on this topic at &lt;A HREF="http://www.pmhut.com/sdlc-vs-project-execution-process" REL="nofollow"&gt;PM HUT&lt;/A&gt; recently.  It was a reminder that the software developmet process is a subset of most prohjects, and while this work stream may be run to a poject framework is often a sub component or a broader project.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/6572833068051719808/comments/default/2224233002928818810'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/6572833068051719808/comments/default/2224233002928818810'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/04/requirements-management-six-cs_25.html?showComment=1209383891660#c2224233002928818810' title=''/><author><name>Craig Brown</name><uri>http://www.blogger.com/profile/01210437173582289473</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='03178891453306926128'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.betterprojects.net/2008/04/requirements-management-six-cs_25.html' ref='tag:blogger.com,1999:blog-15466608.post-6572833068051719808' source='http://www.blogger.com/feeds/15466608/posts/default/6572833068051719808' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-15466608.post-2972938655551785100</id><published>2008-04-27T01:37:46.043+10:00</published><updated>2008-04-27T01:37:46.043+10:00</updated><title type='text'>Craig,Good comparison. I've started using the term...</title><content type='html'>Craig,&lt;BR/&gt;Good comparison. I've started using the term "conventional" when comparing processes. "Waterfall" implies the circa 1970's TRW Development Lifecycle and all its attendent issues. But even if it is not used, the "conventional" approaches to PM still have the echo of those bad olde days.&lt;BR/&gt;If I go down the list (a good list btw) - it seems to me the differences between conventional and agile are in the granularity of the information, and the degree of formality. Alistair Cocokburn has an article in the current issue of CrossTalk (a defense sw journal) about iterative and incremental that clarifies some misconceptions. Even in large defense development programs, requirements emerge as the maturity of the program moves from left to right. At each "assessment point" details become clearer, and even the top level requirements change. "We were going to the moon with Orion, now we're not, we're going to Space Station." That's a big change.&lt;BR/&gt;Your matrix is a great starting point that can reveal the similarities between conventional and agile.&lt;BR/&gt;Brookhaven National labs uses a "graded" project management method similar to this. Maybe the vocabularity is becoming normalized to "just good project management"</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/6572833068051719808/comments/default/2972938655551785100'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/6572833068051719808/comments/default/2972938655551785100'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/04/requirements-management-six-cs_25.html?showComment=1209224266043#c2972938655551785100' title=''/><author><name>Glen B. Alleman</name><uri>www.niwotridge.com</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.betterprojects.net/2008/04/requirements-management-six-cs_25.html' ref='tag:blogger.com,1999:blog-15466608.post-6572833068051719808' source='http://www.blogger.com/feeds/15466608/posts/default/6572833068051719808' type='text/html'/></entry></feed>