<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' version='2.0'><channel><atom:id>http://www.blogger.com/feeds/6261285/posts/summary</atom:id><lastBuildDate>Wed, 08 Nov 2006 09:49:08 +0000</lastBuildDate><title>Intranet Portal Guide - Intranet Watch</title><description></description><link>http://viney.com/intranet_watch/</link><managingEditor>david@viney.com (David Viney)</managingEditor><generator>Blogger</generator><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>15</openSearch:itemsPerPage><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/112093747459658514</guid><pubDate>Sat, 09 Jul 2005 19:29:00 +0000</pubDate><atom:updated>2005-08-11T20:15:38.786+01:00</atom:updated><title>Intranet Portals - Search and Taxonomies</title><atom:summary type='text'>Knowledge Management for beginners

Knowledge Management (KM) can be defined simply as the process through which organizations generate value from their intellectual and knowledge-based assets. Knowledge assets are often grouped into two categories:

(1) Explicit Knowledge:

Generally, everything and anything that can be documented, archived and codified. Examples include patents, trademarks, </atom:summary><link>http://viney.com/intranet_watch/2005/07/intranet-portals-search-and-taxonomies.html</link><author>david@viney.com (David Viney)</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/111192685878251013</guid><pubDate>Sun, 27 Mar 2005 12:30:00 +0000</pubDate><atom:updated>2005-05-02T22:18:26.116+01:00</atom:updated><title>Intranet Portals - Collaboration through Team Rooms</title><atom:summary type='text'>Knowledge Management for beginners

Knowledge Management (KM) can be defined simply as the process through which organizations generate value from their intellectual and knowledge-based assets. Knowledge assets are often grouped into two categories:

(1) Explicit Knowledge
Generally, everything and anything that can be documented, archived and codified. Examples include patents, trademarks, </atom:summary><link>http://viney.com/intranet_watch/2005/03/intranet-portals-collaboration-through.html</link><author>david@viney.com (David Viney)</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/111506867037834415</guid><pubDate>Mon, 02 May 2005 21:09:00 +0000</pubDate><atom:updated>2005-05-02T22:17:50.386+01:00</atom:updated><title>Intranet Portals - Personalisation and Customisation</title><atom:summary type='text'>The key difference between an (old-fashioned) Intranet and a Portal

What typifies a modern intranet portal is that there is a standardised user interface (“UI”) with a built in system for user authentication. In other words, the user signs in to the portal rather than simply accessing it. This brings us to the key difference; an intranet portal knows who you are, whilst with an old-fashioned </atom:summary><link>http://viney.com/intranet_watch/2005/05/intranet-portals-personalisation-and.html</link><author>david@viney.com (David Viney)</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/111012028882415217</guid><pubDate>Sun, 06 Mar 2005 14:37:00 +0000</pubDate><atom:updated>2005-03-06T14:46:22.740Z</atom:updated><title>Intranet - The Benefits Realisation Plan</title><atom:summary type='text'>The Millennium Experience

A successful project is one that delivers on-spec ('quality'), time and cost. Right? Well consider these two projects…The Millennium Dome was delivered on time for the 31 December 1999 and safely within a budget (fixed in 1998) of £289 million. The Project was also delivered to quality, albeit against a Specification that had been adjusted several times during the </atom:summary><link>http://viney.com/intranet_watch/2005/03/intranet-benefits-realisation-plan.html</link><author>david@viney.com (David Viney)</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/109917371566637326</guid><pubDate>Sat, 30 Oct 2004 22:01:00 +0000</pubDate><atom:updated>2005-03-05T19:51:10.306Z</atom:updated><title>Intranet Project Names - some ideas</title><atom:summary type='text'>"What's in a name? That which we call a rose
By any other word would smell as sweet."

In this famous quote from Act II of Romeo and Juliet, Juliet tells Romeo that a name is an artificial and meaningless convention, and the fact he is a Montague and she a Capulet (warring families) means nothing to their love.

However, there is some strong evidence from the UK's Cranfield University - and </atom:summary><link>http://viney.com/intranet_watch/2004/10/intranet-project-names-some-ideas.html</link><author>david@viney.com (David Viney)</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/110251036542228443</guid><pubDate>Wed, 08 Dec 2004 13:48:00 +0000</pubDate><atom:updated>2005-03-05T19:49:05.266Z</atom:updated><title>Intranet Portal - Business Case ROI</title><atom:summary type='text'>The days of easy money are over

In these post-dot-com days of the 21st Century, the hype attached to IT is well and truly over. The modern Board is deeply suspicious of large IT projects with questionable benefits and a long-term payback period.

The good news is that a world-class portal implementation has the power to completely transform your organisation and touch everyone, from the office </atom:summary><link>http://viney.com/intranet_watch/2004/12/intranet-portal-business-case-roi.html</link><author>david@viney.com (David Viney)</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/109917246927510699</guid><pubDate>Sat, 30 Oct 2004 21:39:00 +0000</pubDate><atom:updated>2005-03-05T13:41:48.436Z</atom:updated><title>Intranet Portal Project - RAD or Waterfall?</title><atom:summary type='text'>In this short article, David Viney examines whether Rapid Application Development (RAD) or Waterfall development methodologies should be used during Intranet Portal projects.

Building bridges

I have often used the analogy of building a bridge to explain to business colleagues the difference between RAD and Waterfall.

Let’s say that we are in the middle ages and the Mayor of </atom:summary><link>http://viney.com/intranet_watch/2004/10/intranet-portal-project-rad-or.html</link><author>david@viney.com (David Viney)</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/110336528984826511</guid><pubDate>Sat, 18 Dec 2004 10:16:00 +0000</pubDate><atom:updated>2005-03-05T13:36:54.533Z</atom:updated><title>Stakeholder Analysis and Stakeholder Management</title><atom:summary type='text'>What is a Stakeholder?

Try “define: Stakeholder” in Google and you will be surprised by the huge differences in the way this simple word is defined. It perhaps proves - in a way - just how confused people get about Stakeholder Management and how inconsistent the different approaches to it can be!

My simple definition is “anyone affected by a decision and interested in its outcome”. This can </atom:summary><link>http://viney.com/intranet_watch/2004/12/stakeholder-analysis-and-stakeholder.html</link><author>david@viney.com (David Viney)</author></item><item><guid isPermaLink='false'>http://www.blogger.com/feeds/6261285/posts/summary/110676956703170787</guid><pubDate>Wed, 26 Jan 2005 19:40:00 +0000</pubDate><atom:updated>2005-03-05T11:00:57.386Z</atom:updated><title>Managing Project Risks and Issues</title><atom:summary type='text'>Inherent (or Business) Risk

Inherent Risk is the risk that exists in the environment around your portal project. It will tend to be unique to your organisation; it's culture and politics. For example, if you have a fragmented business (either geographical or functional), then this will create a higher inherent risk of poor communication.

Project (Specific) Risk

Project Risk is the risk </atom:summary><link>http://viney.com/intranet_watch/2005/01/managing-project-risks-and-issues.html</link><author>david@viney.com (David Viney)</author></item></channel></rss>