Breakout session Sharepoint Pros and Cons #intra10

Breakout session by Toby Ward (and blog).

Gives a general overview of Sharepoint old and new versions. "Sharepoint does a lot of things, but does very few things very well." (CMSWatch) Search is ok, not perfect. Content management is basic, simple, but some need heavier stuff. Some clients have site sprawl. Although not many in the room seem to have this problem. Good integration with Microsoft tools, although sometimes work is needed. Sharepoint can be extensive.

The above-mentioned remarks relate mostly to Sharepoint 2007.

Not many using Sharepoint to power to the corporate intranet. More on department and workgroup level.

Now over to Sharepoint 2010. Release date is May 12. (A guy in the room won the Canada cap for getting that right.)

Toby says: don't migrate right away. Wait for the first service pack to be released.

Parts of Sharepoint 2010:

  • sites
  • composites (mashups)
  • insights
  • search
  • content
  • communities

Biggest improvements: the publishing platform (wiki - which is much better than in 2007, Toby says). Web content management, taxonomy and meta data, social media (FAST), digital assess management and records management too. When upgrading things to 2010 things should still work coming from 2007. Sharepoint online will also be improved. Features of 2010 will be release for SP online at the end of 2010.

Toby goes into these items one by one. Interesting: create flows in Visio and import them to Sharepoint. Microsoft guy in room says: It's not that sexy yet in vs 1.0.

Governance still needs to be done; it's not Sharepoint's responsibility anyway.

Pricing for Sharepoint 2010 is not clear yet.

You need a heavy infrastructure and computer to run Sharepoint.

Advice:

  • stick with 2007 until mid 2011. But then move over if you use MS stuff.

Links to his slides will be on Communexions.com.

Popular posts

Keep the Intranet Small

Image
This tweet by Jonathan Phillips ( @digitaljonathan ) triggered to finalize this post, that's been burning in my draft box. I've always been intrigued by how unsuccessful many intranets are. And there are all kinds of good reasons for intranet failure. One of the things that is hardly ever mentioned is: Shouldn't the intranet be smaller? Usually intranets are huge. Lots and lots of pages with lots and lots of content. With complex navigation. The intranet  evaluation surveys almost always show employees only use the news page and people finder. But still we build and maintain nice big intranets. Not only stats point to smaller intranets. There are others reasons as well. I came up with a few. If you have more, just leave a comment. Here's my list: -            user requirements: users don't require large intranet -            search/navigation: searching and navigating a small intranet is easier than in a large intranet -            mobile: the content of the
Read more

Enterprise 2.0 Research

Image
There's not too much fundamental research on Enterprise 2.0. Deloitte recently published interesting research done on enterprise 2.0 implementations and their return-on-investment. In the EU research has also done as well. Study is being done for the European Commission and it was carried out by Tech4i2, IDC and Headshift. What was the goal of the study? Goals of the study To provide a clear definition of Enterprise 2.0 is, describe the market and the positioning of EU industry, also in comparison with US and Asia; To analyze the take-up of Enterprise 2.0, the organizational requirements, and the role on the transition to a knowledge based low-carbon economy; To collect evidence on its macro-economic impact, as a market opportunity for the European Software industry and as a productivity tool for European business; To identify and analyse both the direct and contextual challenges, including the need for Next Generation Access and the legal barriers; To analyse an
Read more

Innovation in Turbulent Times

Image
I love reading articles about innovation. And every now and then you read one that is very interesting. "Innovation in Turbulent Times" by Rigby, Gruver, Allen (in HBR, June 2009) is one of them. This article takes fashion companies as an example for continuous, year-by-year innovation. And how successful fashion companies are usually led by two people: a left-brainer and a right-brainer. "If you don't have highly creative people in positions of real authority, you won't get innovation. Most companies in other industries ignore this lesson." They extend this to show that successful non-fashion companies have the same kind of leadership. And this kind of leadership is usually also characterized by a long-term relationship. I think this concept can also be extended to teams and projects as well. More often than not, people are good at one or the other: thinking up great concepts or ideas, or, making them. In teams and projects we can learn from this as
Read more