<?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-8662858581791799812.post9074358046518652063..comments</id><updated>2007-11-28T23:06:30.180+01:00</updated><category term='mobile'/><category term='Innovation'/><category term='Information Management'/><category term='social software'/><category term='ECM'/><category term='E20'/><category term='Ambient awareness'/><category term='E-Learning'/><category term='Change'/><category term='Integration'/><category term='Master Data Management'/><category term='SOA'/><category term='Enterprise Architecture'/><category term='E20 SocBiz'/><category term='green'/><category term='RSS'/><category term='SaaS'/><category term='Portals'/><category term='Leadership'/><category term='Content Architecture'/><category term='Social media'/><category term='apps'/><category term='Wikis'/><category term='Blogs'/><category term='Information overload'/><category term='Findability'/><category term='Green IT'/><category term='Micro-blogging'/><category term='Information Architecture'/><category term='Project Management'/><category term='Governance'/><category term='Intranets'/><category term='Cloud Computing'/><category term='Mobility'/><category term='Culture'/><category term='Visualizations'/><category term='BPM'/><category term='Social Networks'/><category term='Strategy'/><category term='Search'/><category term='Web 2.0'/><category term='Requirements'/><category term='Knowledge Management'/><category term='Virtual teams'/><category term='Social CRM'/><category term='User Experience'/><category term='Mashups'/><category term='BI'/><category term='Collaboration'/><category term='Enterprise 2.0'/><category term='SocBiz'/><title type='text'>Comments on The Content Economy: Using a Wiki For Requirements Management</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.thecontenteconomy.com/feeds/9074358046518652063/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default'/><link rel='alternate' type='text/html' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html'/><author><name>Oscar Berg</name><uri>https://profiles.google.com/109479022314471643787</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh6.googleusercontent.com/-y-9XOIriOSg/AAAAAAAAAAI/AAAAAAAACz8/y8IeZ7GbvNw/s512-c/photo.jpg'/></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-8662858581791799812.post-987949975017632877</id><published>2007-11-28T23:06:00.000+01:00</published><updated>2007-11-28T23:06:00.000+01:00</updated><title type='text'>Thanks for pointing me to this valuable resource.&lt;...</title><content type='html'>Thanks for pointing me to this valuable resource.&lt;BR/&gt;&lt;BR/&gt;/Oscar.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default/987949975017632877'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default/987949975017632877'/><link rel='alternate' type='text/html' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html?showComment=1196287560000#c987949975017632877' title=''/><author><name>Oscar Berg</name><uri>http://www.blogger.com/profile/13364324951599654650</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.oscarberg.se/images/ob.jpg'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html' ref='tag:blogger.com,1999:blog-8662858581791799812.post-9074358046518652063' source='http://www.blogger.com/feeds/8662858581791799812/posts/default/9074358046518652063' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1090671562'/></entry><entry><id>tag:blogger.com,1999:blog-8662858581791799812.post-1290556963507118171</id><published>2007-11-28T22:23:00.000+01:00</published><updated>2007-11-28T22:23:00.000+01:00</updated><title type='text'>Stakeholder participation will be stimulated by em...</title><content type='html'>Stakeholder participation will be stimulated by empowering these stakeholders. And a wiki is a very good technology to support empowerment.&lt;BR/&gt;The site wikipatterns.com&lt;BR/&gt;http://www.wikipatterns.com/display/wikipatterns/Wikipatterns&lt;BR/&gt;Has several patterns that are useful to support empowerment&lt;BR/&gt;E.G. "Seed it with content", "Barnraising" will be useful to get the masses going.&lt;BR/&gt;&lt;BR/&gt;But something extra is required to maintain the speed of quality growth</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default/1290556963507118171'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default/1290556963507118171'/><link rel='alternate' type='text/html' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html?showComment=1196284980000#c1290556963507118171' title=''/><author><name>Henk Daalder</name><uri>http://www.guldenlijn.nl/windparken/mwiki/index.php/See_English_summary</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img1.blogblog.com/img/blank.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html' ref='tag:blogger.com,1999:blog-8662858581791799812.post-9074358046518652063' source='http://www.blogger.com/feeds/8662858581791799812/posts/default/9074358046518652063' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-251184556'/></entry><entry><id>tag:blogger.com,1999:blog-8662858581791799812.post-1494887183317512392</id><published>2007-09-27T18:30:00.000+01:00</published><updated>2007-09-27T18:30:00.000+01:00</updated><title type='text'>Hello Oskar,&lt;br&gt;&lt;br&gt;I fully agree with your idea t...</title><content type='html'>Hello Oskar,&lt;BR/&gt;&lt;BR/&gt;I fully agree with your idea to use a wiki for distributed teams or an easy communication with stakeholder.&lt;BR/&gt;There is a project running in Germany. Only a few papers are available in the web(German only). try to search for "DisIRE".&lt;BR/&gt;Pls, let me know if you find something more.&lt;BR/&gt;&lt;BR/&gt;Q-wing@web.de</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default/1494887183317512392'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default/1494887183317512392'/><link rel='alternate' type='text/html' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html?showComment=1190914200000#c1494887183317512392' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img1.blogblog.com/img/blank.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html' ref='tag:blogger.com,1999:blog-8662858581791799812.post-9074358046518652063' source='http://www.blogger.com/feeds/8662858581791799812/posts/default/9074358046518652063' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-334770229'/></entry><entry><id>tag:blogger.com,1999:blog-8662858581791799812.post-8654129644632709458</id><published>2007-08-14T03:31:00.000+01:00</published><updated>2007-08-14T03:31:00.000+01:00</updated><title type='text'>http://www.computer.org/portal/cms_docs_software/s...</title><content type='html'>http://www.computer.org/portal/cms_docs_software/software/content/promo/s2028_07.pdf</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default/8654129644632709458'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8662858581791799812/9074358046518652063/comments/default/8654129644632709458'/><link rel='alternate' type='text/html' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html?showComment=1187058660000#c8654129644632709458' title=''/><author><name>Grasshopper</name><uri>http://www.blogger.com/profile/02558920592141195354</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.thecontenteconomy.com/2007/08/using-wiki-for-requirements-management_03.html' ref='tag:blogger.com,1999:blog-8662858581791799812.post-9074358046518652063' source='http://www.blogger.com/feeds/8662858581791799812/posts/default/9074358046518652063' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1684566114'/></entry></feed>
